Chasm not healing

ThaRoadWarrior

I also described the problem of Chasm's revive-stun overriding Thano5's Court Death stun, and my fix of "attacker gets priority" would be fine if it worked in that context also where you have two characters with competing "on death" stun events. The stun component on 5* Court Death was supposed to make it so that it guaranteed the damage hit, so that behavior is a nerf for sure.

The way Chasm's power is worded is: At the start of the match and whenever Chasm revives, stun the enemy team for 1 turn. If Chasm is downed and there are N or more Abyss tiles on the board, Chasm is revived with XX% health etc. So the stun happens on the Revive, not the Down based on this wording.

Court Death says: When you down an enemy, stun all characters except Thanos for 2-turns, then deal 15123 damage toall enemies and 3751 damage to Thanos' allies.

So the way I would expect it to work is:
1) Chasm (or iHulk) is downed
2) Court Death Stun is triggered, then the damage
3) Subsequent Revive events trigger

It seems like the way it WAS working is that the revive events on iHulk and Chasm happened simultaneously to the Down event, which is what allowed Court Death to trigger after Hulk came back. That one seems to have been "fixed," but Chasm's is still happening as a simultaneous event which gives his stun the priority over Court Death.

entrailbucket

Part of the problem here is in the descriptions, too. We've noticed this with a few other characters (Wong is one) where the description doesn't 100% describe exactly what the ability actually does (and, to be fair, if you wanted to completely lay out exactly what some of these abilities do, it'd be a massive wall of text). The other problem is that most of these little details are irrelevant to 99% of players -- there's only a few of us who even noticed the big order of operations change they just put in.

KGB

@ThaRoadWarrior said:
I also described the problem of Chasm's revive-stun overriding Thano5's Court Death stun, and my fix of "attacker gets priority" would be fine if it worked in that context also where you have two characters with competing "on death" stun events. The stun component on 5* Court Death was supposed to make it so that it guaranteed the damage hit, so that behavior is a nerf for sure.

The way Chasm's power is worded is: At the start of the match and whenever Chasm revives, stun the enemy team for 1 turn. If Chasm is downed and there are N or more Abyss tiles on the board, Chasm is revived with XX% health etc. So the stun happens on the Revive, not the Down based on this wording.

Court Death says: When you down an enemy, stun all characters except Thanos for 2-turns, then deal 15123 damage toall enemies and 3751 damage to Thanos' allies.

So the way I would expect it to work is:
1) Chasm (or iHulk) is downed
2) Court Death Stun is triggered, then the damage
3) Subsequent Revive events trigger

It seems like the way it WAS working is that the revive events on iHulk and Chasm happened simultaneously to the Down event, which is what allowed Court Death to trigger after Hulk came back. That one seems to have been "fixed," but Chasm's is still happening as a simultaneous event which gives his stun the priority over Court Death.

Ah, so they split iHulks passive into 2 parts but not Chasms. So you would expect in step 3 that Chasm would revive and stun your team for 1 turn since a revive would clear the stun leaving Chasm as the only unstunned character on either team.

So here is a question. Lets say you down iHulk and Chasm is still alive but after your court death damage he would be dead. Would you expect:

1) iHulk down - he gets set to revive since Chasm still alive
Court Death fires downing Chasm
Match over since all enemies down

2) iHulk down - he gets set to revive since Chasm still alive
Court Death fires downing Chasm. There are no other alive team mates so he is not set to revive
iHulk revives since he was set to revive

There's ambiguity there about what could reasonably expect to happen based on wording of the powers.

Anyone tested whether iHulk revives if he was stunned when he was downed? He used to revive but I wonder now that they split the revive into 2 parts whether he lost that ability and now he won't revive if downed while stunned (Phoenix doesn't for example).

KGB

entrailbucket

Phoenix does revive when she's stunned -- the ability always specifically stated that, and as far as I know it's always worked correctly.

ThaRoadWarrior

if Court Death resolves on iHulk dying, and doing so kills Chasm, and they were the final 2, you should win, because that's how AOE attacks funcion and that's all Court Death is in the end, just with a conditional trigger.

KGB

@ThaRoadWarrior said:
if Court Death resolves on iHulk dying, and doing so kills Chasm, and they were the final 2, you should win, because that's how AOE attacks funcion and that's all Court Death is in the end, just with a conditional trigger.

But the AOE didn't actually down iHulk. In my example he was downed by something else prior (damage/another power). It's no different than if a cascade happened that first downs iHulk, then Chasm.

There is more than one way it could resolve and still meet the letter of the power.

KGB

WilliamK1983

Used him a bunch last night in the lighting rounds and to run through welcome to shield. He healed every web tile match if he was under 10k health. Anytime above 10k, nothing. I thought he might have healed twice above 10k, but it was M'baku healing, the slow character rotation made it seem like Chasm.

tonypq

It's crazy over a week now and no comments from BC on the healing issues or anything they may or may not be aware of that's broken with Chasm. I'm not a Chasm worshipper heh, but he's a useful character in quite a few scenarios, would be nice if he worked. When I'd seen there were no posts on the issue I created a thread in the bug forum and no responses yet. I linked this thread in that bug forum post also.

Still seems very weird he might be healing like normal for some, but at the same time is a hot broken mess for myself and some others that have posted here.

ThaRoadWarrior

@KGB said:

@ThaRoadWarrior said:
if Court Death resolves on iHulk dying, and doing so kills Chasm, and they were the final 2, you should win, because that's how AOE attacks funcion and that's all Court Death is in the end, just with a conditional trigger.

But the AOE didn't actually down iHulk. In my example he was downed by something else prior (damage/another power). It's no different than if a cascade happened that first downs iHulk, then Chasm.

There is more than one way it could resolve and still meet the letter of the power.

KGB

If court death triggers on the "down," the AOE should emit damage when Hulk is "downed" but before the revive, and if it downs Chasm, it should end the match before any revives trigger. What actually happens will depend on where the "do I have active allies?" check is performed though. Again, there is what is happening, and what is intended to happen, and only the design team knows which is which.

Captain_Trips88

I seem to be in the very random moments of healing category. also used chasm in welcome to shield to try and blitz through and the Thing node wiped me out. I don't ever use chasm so I just thought it was a misunderstanding of his powers when it came to healing but having read this I believe its just whatever this change is.
Incidentally, ended up using Arcade, he racks up quite a lot of big quick damage with Okoye and has an element of puzzle play with matching traps that appeals to someone who thoroughly enjoys the Shang-Chi approach of having to actually think during matches.

tonypq

I'm still having issues with Chasm not healing correctly. Very strange some say he's healing for them but others have experienced the same issues I have.

Nothing more annoying than matching webs for a few turns in a row just to see no healing. To see his health just dwindle down, until the only way he actually heals sometimes is if he revives heh.

When I pulled Chasm in the LL store back then, his healing worked as it normally should, so something is going on these days. When I first started using him, his healing at the time was his main draw. Reminded me a bit years ago in 3* tier, when I'd use Patch Wolverine simply because you could count on his healing which made things easier.

When I first started using Chasm it was primarily for his healing for some tougher PVE SCL 10 nodes once a while. To let Chasm take a beating and preserve the health of my other 5*s. When when I read how much of a pain in PVP he was I started using him there also and he healed as his description states.

MrDupaTM

I wish he could also stop auto-stealing, auto-stunning and auto-sucking.

Just nerf him.

tonypq

Thought his healing got fixed. Used him one match and literally every web tile caused him to heal. Then next two matches his healing appeared to be broken again.