Thrawn event 7*
October 7, 2017 11:29PM
edited October 2017
Whenever a unit is fractured in the thrawn event (7*) and then I have Hera put backup on them and they die the unit does not revive. And yes they still have backup on them when taken out. Is this suppose to happen since fracture says nothing about stopping revives.
0
- 61.2K General Discussion
- 9 Developer Q&A Archive
- 2.6K New Players
- 30.6K Arena and Character Strategy
- 4K Individual Events
- 4.6K Guild Events
- 4.6K PVP and Rivalry
- 50.2K Guild Recruitment
- 732 Art and Media
- 4.1K Off Topic
Howdy, Stranger!
Replies
But see that doesn't make sense since in the backup ability description it says it can't be prevented and it is a locked ability so that should override deathtrooper's ability
How do I do that I do t really post the forum very much
In this event death trooper doesn't have or doesn't use that ability. Unless DT's applied buff immunity works through it which it shouldn't
I think him alone could be my whole Phoenix team at g8 7*
The cant be prevented part in the Back-Up plan means lets say Ezra if he has buff immunity on him and Hera uses back up Ezra will gain Back-Up ignoring buff immunity
But then that makes the ability absolutely useless. That means it is only applied and does nothing.
This is the actually ability description: Target other ally gains Backup Plan buff for 3 turns.
(Backup Plan: Revcover 10% health, Revive with 80% Health and 30% Turn meter when defeated. Can't be dispelled or Prevented.)
This is describing what is being done and the it can't be prevent from being done that is the whole point of a locked ability THAT THE EFFECTS WON'T BE STOPPED by other ability's.
My main grip is that stormtrooper(taunted), thrawn, and deathtrooper start on full turn meter. If stormtrooper wasn't auto taunted I'd happy.
Backup Plan is still useful here, because your characters won't always be killed by specifically Terminate. But be aware that if they are, Backup Plan won't work.
And that's what I meant useless for this event.
See I'm arguing semantics right now. When you say what an ability does then write it can't be dispelled or prevented then that is what it means unless one specifies certain expectations. But then since it is a locked ability which does not go away technically it should be overridden by "lesser" abilities except in raid of course.
See I'm arguing semantics here too when say what an ability does then write next to it that it can't be prevent or dispelled it means just that that those said effects will happen unless specific exceptions are stated. And besides since it is a locked abiloty it is technically an ability of higher order to a "lesser" unlocked ability unless in raids of course.
It doesn't say the effects though. It is referring to the buff.
Yes, a Boba killed by Terminate would not revive. This is a function of the ability independent of deathmark.
There are two type of revives in this game, ones like HK that are not a part of a like ability/ constantly reapplied and ones like Boba/Her a that are "locked" it just honestly is silly to make it "locked" and not removable and then make a toon that can just ignore that completely. It makes the whole idea pointless since a toon will eventually be made that revives that will ignore the terminate abilities a line should be drawn.
You know when protection was introduced it was introduced as a nonrecoverable health bar like that was the terminology used. But then characters where introduced that specifically gave "healed" protection completely counteracting the original point of protection.
Revive is all the same. Boba's Bounty Hunter's Resolve buff is locked--it can't be dispelled. The effects of the buff; in this case, the revive, can be blocked. The first character to block revives was Boba...also the first character with a locked buff. If it was meant to ignore revive immunity, they wouldn't have introduced it with the first character to inflict revive immunity.
Think of the order of operations this way:
1) You put Backup Plan on someone.
2) That person dies.
3) Terminate places a hidden flag on the character saying they cannot be revived.
4) Backup Plan triggers and attempts to revive.
5) Because the character can't be revived, Backup Plan fizzles and they stay dead.
Who knew playing Magic the Gathering a whole bunch in high school would have real world benefits 17 years later?
Not to argue but they are not the same one is a revive chance one is a automatic revive upon death
Terminate says that the character killed by it cannot be Revived.
The BUFF in essence is only the effects upon death so the can't be prevented is a little silly since they affects are techniclly prevented by another ability. The description does not differentiate between applying buff or affects. Lol man I haven't thought about magic the gathering in a long time
Whole point really is that the two abilities in the descriptions kinda butt heads. The Backup plan says it won't be prevented when it describes the effects in the parenthesis. It really should have the prevented part outside of the parenthesis. But anyway you I'm really just annoyed at the 100% TM at the started of the final battle
Well, I think we can all agree the wording sometimes leaves something to be desired. In this case, "Can't be dispelled or prevented" is in the same sentence--how would a revive be dispelled? Therefore, it's safe to assume it is talking about the buff and not the mechanic.