Hi guys,
in the
latest update thread, there is a bugfix mentioned:
Fixed an issue that allowed Nightsister's (excluding Zombie) to be Revived by Mother Talzin’s “The Great Mother” if they were defeated with Deathmark active
Can somebody clarify how this mechanic was working and how it is supposed to work after fix?
I thought zombie revives (can't be prevented) all the time and has to be the last man standing before finally dying out.
Thanks!
1
Replies
This.
They were all reviving but now only zombie will.
If it is the debuff preventing the revive then the in game description should be updated to reflect this: "targets defeated by terminate can't be revived" to "targets defeated with death mark can't be revived"
Death mark does not block revive, terminate does.
So now nightsisters are nerfed(even though they've heavily fallen out of favor, aside from p4 sith)?
I've got an update: Deathmark's ability description is a bit incomplete compared to how it was described originally in raids. We need to update the ability description to show it prevents revives as seen below. The patch fixed the Nightsisters (besides Zombie) being able to revive even if deathmarked.
correct. because the debuff is implied.
Are you talking about the Forest Moon event? I thought I saw this too when I killed Ewok Elder and up popped Logray. Problem was, I couldn't confirm if Logray was killed with it applied because they were cleansing it occasionally.
Did you just seriously link that commie site? There’s only 1 real repository!
Only reason why I asked because the original post which I've read was edited; it said:
original in web-cache
Maybe he couldn't find it on Reddit?
https://swgoh.gg/characters/death-trooper/ability/terminate
There are 2 distinct revive immunity parts to the code. One is linked to the base ability "Terminate":
Apply Effect
Context #2
specialability_deathtrooper02_kill_trigger_BASE
To Self who is Alive
Apply child effect(s) based on condition triggers
Effect expires on:Perform Move
Child effect is applied on:Kill
Context Returned: Target(s) and if effect succeeded in applying
Immunity
Context #0
generic_revive_immunity_target
For Current Target from Enemy Side who is Alive or Dead
Applies an Immunity effect to the target(s)
Effect is unresistable
Descriptive revive_immunity
Effected revive
Context Returned: Target(s) and if effect succeeded in applying
Basically if the move causes a kill, the target can't be revived.
But also there is a revive immunity linked to Deathmark:
Apply Effect
Context #5
specialability_deathtrooper02_deathmark_part3of3
To Current Target from Enemy Side who is Alive
This effect will EXECUTE if the previous query returned CONTEXT_VALUE > 0
Apply child effect(s) based on condition triggers
Effect is unresistable
Descriptiveclearable_debuff
Effect expires on:2xFull Turn Complete,Encounter End,Persistent Effect Add Instancestealth_buff,Revive,Remove Persistent Effectdeathmark_debuff
Child effects are applied on:Receive Damage
Context Returned: Target(s) and if effect succeeded in applying
Immunity
Context #0
generic_revive_immunity_self_deathmark
For Self who is Alive
Where an active effect doesn't have tag revive_immunity
Applies an Immunity effect to the target(s)
Effect is unresistable
Descriptive revive_immunity deathmark_revive_immunity
Effected revive
Context Returned: Target(s) and if effect succeeded in applying
So basically revive immunity is a hidden tag that accompanies the Deathmark debuf, expiring when the debuf expires.
So both Terminate and Deathmark cause revive immunity.
Then you read the dev's answer incorrectly. Both terminate and deathmark prevent revives. DT's ability description doesn't currently say that, which is what Crumb was saying needs to be fixed. It DOES prevent revives, but the description is wrong.
Really??? Are you sure?
(and if you see either on your shard congrats)
As you marked it, SB_Crumb was making a comparison to raids (using it as analogy). So it would make absolutely no sense if he was talking about raids in the first place.