TW droid unstable batteries messed up our strategy

DarthMyself
106 posts Member
edited April 2019
By now we know that there was some sort of error in the text describing the current TW droid buff. The original forum post as well as the in game details stated clearly:" Whenever a droid is Defeated (i.e. defeated by unstable batteries or killed by attack) he deaks 80% damage and burns all enemies etc...

Our guild drew its strategy based on this clear description, and we decided to use all our droids on Offense under various squads. Because that meant whenever a droid dies he is dealing big damage. So even undergeared droids would be useful.
But as we started our TW, we noticed that none of that was happening. Then we learned about the Mistake in the text.
Now our entire strategy is in shambles. Since we set our Defenses and our Offensive plans revolving around this understanding of the buffs.

Mistakes do happen to all of us. (To some more often than others, but I digress). Therefore I request from the devs to allocate first place rewards to all parties of all TW battles as a compensation for time wasted planning based on wrong information given to us by the game.
I see this as the only fair approach to fix this mistake. Everybody wins. CG will not die if they gave 1 additional zeta and a bunch of extra gear to everyone who took part in TW.

Replies

  • OmegaIV
    105 posts Member
    Your request fell on deaf ears. :(
  • Nikoms565
    14242 posts Member
    Tiy could have left the "our strategy" part out of the thread titke, and it woukd have been just as accurate.
    In game name: Lucas Gregory FORMER PLAYER - - - -"Whale blah grump poooop." - Ouchie

    In game guild: TNR Uprising
    I beat the REAL T7 Yoda (not the nerfed one) and did so before mods were there to help
    *This space left intentionally blank*
  • This issue needs addressed. We also lost our TW match up because of this description error.
  • They didn't fix it. Our guild just tried it in today's TW and nothing happened. Come on CG! This was already reported!
Sign In or Register to comment.