Hi Developers,
Along with the list of successful defence and attack banners in TW, please also provide a list of number of Unsuccessful attempts by a guild member.
Currently there is no way in determining whether a guild member have used his full roster or just attempted one This is specially problematic when there are low scores and people say they have attacked but were unsuccessful.
This can be true some time but not most of the time. Hope others also face the same issue in TW.
This will help in removing free loaders from the guild.
0
Replies
I know we need to trust others.. but sometimes others take advantage of it.
This is a way around, so there is a way, but yes we need a better way
Which non—locked zone? Lock all zones. Key word: "all"
For example my guild doesn't have any Traya so if there is a Traya wall and we know that people will end up wasting too many teams to take down one then we block that zone and put focus on manageable zone.
Hope you understand my POV.
Lock all zones. Use guild—chat, banner texts or a third party chat application to inform your guild which zones to attack.
(And try educating your guild to only attack if they have a team with a proper chance of winning or killing at least one enemy.)
Our guild uses discord, and it helps so much on every guild activity, that you should strongly consider it. Instant communication, and the ability to attach screenshots etc......Think about how valuable it is for a member to say "I've got a squad that can take it", or worse "Hey, be careful of that FO squad, I left them with TM loaded".
I really would like more visibility to this, because I can't tell if players with low Attack banners are inactive/waiting, or ineffectively attacking.
Yes, there are things to be done to combat this. But it is janky that we have to use tricks and external apps to get this done. Just track actual attempts, show us the data so we don't have to try to trick the game into giving us the information we want.
What an idea!
Developers should try and provide a way out as this seems to be a common problem across the guilds.