Boba execute messing up everything
So boba executed 86 and rey killed 88. I tried to revive 88 with je on the next turn but he didn't come back. My best guess is rng chose 86 for the revive and bobas block made it not work. Any...
Forum Discussion
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.
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
