Territory Battle and War - Guild Leader and Officer Tools Update [MEGA]

"CG_Kozispoon;c-1327981" wrote:
Morning and happy Monday folks!

Thank you for all your helpful replies, feedback, and discussion regarding what we have in store for Territory Wars going forward. Noting feedback of time commitments, we wanted to expand on a couple points:

• There is no value in continuing activity after your Guild is at three stars in a territory, thus the contribution lock when maxed.
  
• Even though a territory can be locked, Platoon Missions and Special Missions will still be available to Guild members.
  
• Locking a territory at 3 stars provides guilds a clearer picture of effective contributions vs general engagement. It does so by limiting a player’s ability to climb stat leaderboards after a territory is already completed.
  
• We made the call not to let officers lock at one, two stars. We feel the coordination to lock/unlock Territories at specific times drives Guild Officers time commitment up significantly.
  
• Dedicating Guild member deployments solely to officers would again drive up time commitment of officers exponentially. Territory battles is intended to reward the efforts of all Guild members and we’ll continue looking for ways to reward and enhance guild wide efforts.
  
• The Focus and Prohibit tools will also work on Deployment
  

.

@CG_Kozispoon:

The contribution lock is actually a huge detriment. As guild officers, we are attempting to assess participation and CM completion rates, so even if it means sacrificing potentially a * for rewards, we'd rather that players seek to complete 114 CM's irrespective so that we have **valid** management data to assess participation level and performance. The rest of the changes, are somewhat welcome, in the sense that they will help with the overall picture (contribution per phase leaderboards) but this particular one actually makes that picture considerably less accurate. I, and many others responding to this thread, are asking you guys **not** to lock CM's. Locking deployments if fine, and beneficial, but CM locking very much is not beneficial.