Boba execute messing up everything

"HokieFiend;859055" wrote:
There is a big difference between a raid event and PvP. One situation does not apply to the other.

Instead of people getting upset about a mechanic for a toon that is a specific counterbalance to revive toons you should adjust your strategy.

PvP is a giant game of rock, paper, scissors. Again, asking for paper to beat scissors isn't the answer. You're effectively asking for your toon, which has inherent weakness against another now, to always have its advantage.

"scuba;858878" wrote:


IMO the revive should not pick a character for revive that can't be revived. It is like picking a stunned character to assist.

That said this issue has been going on with ewok elder since pit raid was introduced. Hasn't been fixed, even though it could be because execute tags the character as having revived immunity.

Good news is issue with elder has been flagged for review and hopefully one day a fix will be implemented across the board for all revive characters.

https://forums.galaxy-of-heroes.starwars.ea.com/discussion/comment/704791/#Comment_704791

Ewok Elder will try to revive Devoured or Deathmarked allies: This is confirmed as a bug and flagged as such for our dev team for review

It is the same broke mechanic though no matter what mode of the game it is in so both situations are the exact same.
If 2 characters are killed and one is marked with "revive_immunity" be it by Boba execute, deathmark, devour, and the other is not then a revive should not try to revive the character with "revive_immunty" it should skip them in the selection process when checking for a random ally. Again same as calling stunned ally to assist, the selection processes skips stunned allies since they can not assist because they are stunned.

This is the situation that Op brought up.
One character (86) was executed by Boba the other killed by Rey (88). OP did not expect to revive 86 but should have been able to revive 88 but lost the RNG battle that should not exist.