Boba execute messing up everything

Nice catch! This sounds annoying.

Tell Customer Service and report it in the bugs section.

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

"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.

It's not a broken mechanic when applied to PvP IMO when looking at Boba's execute mechanic and JE patch up. JE is supposed to revive a random droid ally. If that random droid is revive immune so be it. You are asking for JE patch up to always be able to get around a specific counterbalance ability from another toon.

It's a difference in opinion I suppose

"HokieFiend;859071" wrote:
It's not a broken mechanic when applied to PvP IMO when looking at Boba's execute mechanic and JE patch up. JE is supposed to revive a random droid ally. If that random droid is revive immune so be it. You are asking for JE patch up to always be able to get around a specific counterbalance ability from another toon.

It's a difference in opinion I suppose

On that same line of thinking... assists state they will call a random ally to assist so if that random ally is stunned/dazed so be it.

They made a change so that rng in this instance doesn't pick a character that can't assist why should revive rng be different?

Now if you are going to use a revive to try and revive an executed ally than it is your own fault in wasting the ability.

They should also fix the JE AI so he doesn't try to revive after a non-droid dies.

Bobba is OP

They probably made that decision on assists due to a greater overall affect on balancing leaving it that way. Boba' execute is a more specific counterbalance mechanism to revive toons. They may change it but, to me, you can't expect to retain an automatic revive (assuming multiple dead) going against a toon you know is designed to negate that advantage.

"HokieFiend;859117" wrote:
They probably made that decision on assists due to a greater overall affect on balancing leaving it that way. Boba' execute is a more specific counterbalance mechanism to revive toons. They may change it but, to me, you can't expect to retain an automatic revive (assuming multiple dead) going against a toon you know is designed to negate that advantage.

Again with that logic you should not expect to retain an assist because character are stunned.

The calling a stunned ally fix was not for balance it was as ea/CG state silly that the game mechanics were doing that.

Abilities need to be consistent. If one ability is going to skip an ally that can't respond then other abilities should do the same.
Shouldn't be a guessing game as to if an ability is WAD or WAI or broke.