Forum Discussion

4 years ago

Solved

TU24 Kam Mission Bug - Stand Your Ground Doesnt Recover Protection

Product: Star Wars: Galaxy of Heroes Platform:Apple iPhone What type of device are you experiencing the issue with? iPhone XS OS Version 14.6 Ally Code: (Find it here: http://bit.ly/AllyCode ) 16...

bug

EA_UltraSlide
4 years ago
Hi guys and thanks for the report.

"Stand your Ground" was never supposed to restore any Protection, it is only supposed to remove the decrease to max Protection when "Trampled" is removed. This appears to be WAI.

The description reads "Dispel all stacks of Trampled from target ally.".

Update:

This has now been flagged to the team for further investigation. Please see the following forum post: Known Issues with Today's Title Update (06/16/2021)

IcarusSunwalker

New Adventurer

4 years ago

@EA_UltraSlideWait a second, are you saying that it's the developers intention to have our protection reduced by 50% even before we get our 1st turn? Even more since Trampled can't be evaded?

When someone steals you $50 and you "recover" those $50 back you don't get $50 back? Your profit is 0, I get that, but you have "recovered" your $50.

Please rethink what you are saying because it does not make any sense. The protection that was removed should be reinstated.

aFuriousPorpoise

Seasoned Hotshot

4 years ago

Think of "max protection" more like your wallet and "proctection" as the $50. SYG means you recover the wallet but the $50 is gone.

IcarusSunwalker
New Adventurer
4 years ago
@aFuriousPorpoise Still, that was not how the ability used to work since the TB was released.
If that is the intention then they should allow for the ability to be evaded or they might as well say, "at the start of battle you will lose all your protection", because you will need at least 2 stacks to kill Jango.

Ultimately, they should have announced in the Bug Fixes that Crumb posts that this has never WAI and they fixed it in this TU.
- aFuriousPorpoise
  Seasoned Hotshot
  4 years ago
  @IcarusSunwalker I don't disagree with you - if you intentionally fix/change something it should absolutely be in the release notes, which implies they didn't know a change they made had this effect (maybe some refactoring had unintended consequences and the test coverage is poor) and decided after the fact that it was WAI and have now changed their mind about what was intended.
  
  It probably wasn't really the best idea to do a TU in the middle of a TB and Conquest.