AQ Thanos Heal Prevention - Whats this garbage?

Bryan_85

Today, I took block damage with 10% life left. LMD was immediately destroyed, and I began to degen for two seconds from the 10% mark, until I had zero health left.

There is NO REGEN here for the node to prevent. There is no healing factor here. Why is this node affecting this? He shouldn’t get 1% health left and not degen. He should act normally with this node.

DalBot

Literally nothing in his champion profile or in game profile mention anything about regeneration. There is absolutely zero logic to this interaction. The proposed solutions are just terrible.

BigPoppaCBONE

Why the push for heal prevention? It seems to have caused more issues than it’s worth. How did the team decide that leaving Fury at 1% is the correct move vs just leaving the heal block alone? Why so determined to shoehorn that heal prevention in despite the problems it creates @Kabam Zibiit ?

Worknprogress

BigPoppaCBONE said:

Why the push for heal prevention? It seems to have caused more issues than it’s worth. How did the team decide that leaving Fury at 1% is the correct move vs just leaving the heal block alone? Why so determined to shoehorn that heal prevention in despite the problems it creates @Kabam Zibiit ?

Bc Fury absolutely rinses map 7 Thanos if I had to guess

Mauled

SummonerNR said:

(just remembered this...) What is the exact wording for Nick Fury ability of his taking over the fight once his Double is dead ?? Something about his health climbing up to 100 over several seconds ? Does that start from 0 or from 30% ?

That 2nd video that shows him coming in at only 30% (and then degening quickly to 0) is maybe what his real-self starts at right away and then climbs to 100% over several seconds. So might be the “climbing from whatever up to 100%” that is now being Prevented with the new Thanos buff wording. Since it is not an instantaneous stepping in at 100% right away.

Still should NOT be degening during that last 30%, but at least that might explain some of the issue ??

I went in with NF yesterday as I always do, yellow bar, not having touched him for the whole map - just because he’s fun to use on Thanos. Let Thanos smack me for the real NF and I just straight up died. This effect basically is a hard counter to activating his ability mid fight.

Worknprogress

Mauled said:

SummonerNR said:

(just remembered this...) What is the exact wording for Nick Fury ability of his taking over the fight once his Double is dead ?? Something about his health climbing up to 100 over several seconds ? Does that start from 0 or from 30% ?

That 2nd video that shows him coming in at only 30% (and then degening quickly to 0) is maybe what his real-self starts at right away and then climbs to 100% over several seconds. So might be the “climbing from whatever up to 100%” that is now being Prevented with the new Thanos buff wording. Since it is not an instantaneous stepping in at 100% right away.

Still should NOT be degening during that last 30%, but at least that might explain some of the issue ??

I went in with NF yesterday as I always do, yellow bar, not having touched him for the whole map - just because he’s fun to use on Thanos. Let Thanos smack me for the real NF and I just straight up died. This effect basically is a hard counter to activating his ability mid fight.

You have to kill the decoy off before going into the fight. That doesnt seem like something they plan on changing either

DalBot

I honestly don't comprehend how they're trying to justify this, let's call it what it is, nerf of a character by shutting down an ability that shouldn't be present in the first place.

Worknprogress

zeezee57 said:

Genuine question here, does the change from heal block to heal prevention impact anyone else or was this a specific change just to stop Fury? I honestly can't think of anyone else who's healing wasn't already stopped before. As has been said a dozen times already Fury doesn't regen, show me where in his description it says regeneration.

Possibly Blade stopping heal block from procing. I don't use him at all but that's all I could really think of

SiriusBreak

I have to agree that this makes 0 sense. Granted, we SEE Fury gain health after the LMD has been destroyed, but is not technically Nick healing. Just Nick taking over for his LMD (or so we're made to believe as per sig ability wording). This is the real dilemma I see here. The effect is coming from the node, yes? However, the last line of Nick's signature ability explicitly states 'The destruction of Nick's decoy Removes all effects and isn't affected by ability accuracy reduction.' So, placing a Petrify, Heal Block (passive or otherwise) wouldn't work as it would immediately be removed.

Now, because the effect is coming from the node, Nick's ability apparently cannot remove it, though the effect is on him at all times, yet... not. Rewind back to when the node stated 'Heal Block' you can plainly see a 'Heal Block' Icon on Fury (1st video posted by @DalBot ). Despite the fact the Heal Block was permanent, it is technically an effect on Fury, and in turn was removed by his sig ability. Apparently, somehow changing the word from 'Block' to 'Prevention' circumvents 'Removes All effects.'

I did notice in the 2nd video of the current situation, there was no icon representing 'Heal Prevention' on Nick Fury. Is this why Nick's sig ability is now irrelevant? Because 'Heal Prevention' supersedes all abilities and is something more than an effect? I'm genuinely interested in this being stated as such because it would be prudent to know this for future encounters with 'Heal Prevention' and Nick Fury as I have a 5* R4. It is seemingly contradictory with his signature ability's phrasing though.

Madcat

Blade
Nick Fury
Crossbones
Agent Venom
King Groot
Kingpin

All are affected now by not being able to remove or reduce the chance to be affected by a heal block node.

Not sure if Domino or Black Widow could avoid triggering the heal block from a node.

Not that anyone but mods can see this critical information that was requested.

BigPoppaCBONE

Worknprogress said:

BigPoppaCBONE said:

Why the push for heal prevention? It seems to have caused more issues than it’s worth. How did the team decide that leaving Fury at 1% is the correct move vs just leaving the heal block alone? Why so determined to shoehorn that heal prevention in despite the problems it creates @Kabam Zibiit ?

Bc Fury absolutely rinses map 7 Thanos if I had to guess

So what? It isn’t an instant kill and even if it was, so what? What’s the real difference between an instant kill, a one-shot or a two-shot? The alliance still had to go through the fights to get there. They can’t knock out the map in an hour and free their champs, so nothing changes competition-wise. It’s like Kabam got this idea in their heads that they think is really good and they’re willing to tear down whatever they have to and break all kinds of other interactions to put in their pet idea.

DalBot

So are we still going to get zero explanation on why Fury is being nerfed at all when nothing in his profile mentions anything about regenerating?

World Eater

When people talk about stealth nerfs and sneaky, unannounced changes, this is exactly what they mean..

DalBot

MikeHock said:

When people talk about stealth nerfs and sneaky, unannounced changes, this is exactly what they mean..

Yep, the fact that this change clearly targets one specific champ (that I know of at this time)and was completely unannounced is what makes it extra infuriating.

buffajr

I was under the impression upon NFs release that there should be no way to stop the real NF from activating and putting him at 100%. Having the node keep him at 1% upon signature ability seems like horse puckey. Why not change the interaction of the signature ability to interact similar to Kang in V3?

DalBot

Also love that his ability "is not effected by ability accuracy reduction", yet you can conspicuously node block his ability that shouldn't even have to exist. 🤷🏻‍♂️

Worknprogress

buffajr said:

I was under the impression upon NFs release that there should be no way to stop the real NF from activating and putting him at 100%. Having the node keep him at 1% upon signature ability seems like horse puckey. Why not change the interaction of the signature ability to interact similar to Kang in V3?

There's no way for US to stop it.

buffajr

Whatever the reason for this interaction, I believe the main concern here is lack of communication. I may be wrong, but I do not believe they advised at the time or ahead of time that this node was going to be adjusted/changed.

The response was that the original heal block was not interacting as intended in some cases, but did not offer any further explanation of what these instances were so we are still left to question “why the change?”. With little to no explanation on the reason for the change the community will immediately jump to “nerf” as it appears to only affect the users attack champs.

Also, the note that “ The Heal Prevention should be preventing the healing from Nick's signature ability“ is also concerning as it was previously noted several times that there was no way to prevent this from activating. With no further explanation for the change and with one champion being singled out it’s clear there is more at play here.

The options are simple; do nothing and continue to not fully address this node change and explain as to why a seemingly faulty node is still in play further cementing the community’s cry for lack of communication, explain the need for the changing of the node and the instances where it was not working to help us understand the changes to one of the games most played modes.

Either way anything short of a larger response on this is saddening. My biggest concern would be changes like this in other current/future content that can eliminate a certain champs utility at the drop of dime with no explanation. Resources to rank up champs for end game content are too time consuming and difficult to acquire for this to be taken lightly.

DalBot

Fredhorst23 said:

I just noticed that the bleed lane has heal prevention also, so I'm guessing poison path does too. I wouldn't be surprised if the nick fury situation had nothing to do with thanos and was built in to make it impossible for him to purify the node debuffs.

It's only certain nodes in AQ. I use New Cap Marvel for poison lane and usually fight Vulture in Phase 2 while he's thorns noded and he also has the heal prevention on him.

DalBot

Fredhorst23 said:

Yeah, that's what I'm seeing. Any of the lanes that have debuffs from the start seem to have the prevention.

And yet here we are, at the end of another AQ, without any explanation of why this change was made, if it was meant to target a certain champ, and no explanation of why this champs interaction with the node defies all logic based on how the champ is supposed to act.

It’s unacceptable and is ABSOLUTELY a nerf

DalBot

Yeah it's frustrating that the player base is being completely ignored on this nerf that completely and totally lacks justification or logic.

Bidzy7

So much for being open, transparent and honest with the community.

The fact this change was not communicated is ridiculous especially since the whole intention of the change was because the node was not interacting how the designers intended and champs were bypassing it through ability accuracy reduction, purifying etc
That whole reason for the change was that players were using champs to circumvent the heal block, so changing it to stop this would obviously be noticed by said players. Yet no announcement or information prior to entering AQ.

Nick Fury sig ability is not described as a heal. The intention of the sig ability from all sources given to us players is that you are fighting with a weaker decoy version of Nick fury and when you die you fight with the real one with the handicap of only being able to stay at 30% health max and healing above that will degen you back down to 30%.
Of course the way this was programmed is rather then having the health just go straight to 100, the mechanic "heals "back up to 100% and then degens to 30%. Hence why MODOK can interact with the sig ability too.

You tend to have a habit of changing the narrative so we can't even take descriptions at face value, because if you don't like how we are benefiting from it then you simply "nerf" it and then say its meant to work like this.


Nick fury should be allowed access to his sig ability and the Real Nick Fury on these nodes and and it shouldn't be seen as healing.

DalBot

Bidzy7 said:

So much for being open, transparent and honest with the community.

The fact this change was not communicated is ridiculous especially since the whole intention of the change was because the node was not interacting how the designers intended and champs were bypassing it through ability accuracy reduction, purifying etc
That whole reason for the change was that players were using champs to circumvent the heal block, so changing it to stop this would obviously be noticed by said players. Yet no announcement or information prior to entering AQ.

Nick Fury sig ability is not described as a heal. The intention of the sig ability from all sources given to us players is that you are fighting with a weaker decoy version of Nick fury and when you die you fight with the real one with the handicap of only being able to stay at 30% health max and healing above that will degen you back down to 30%.
Of course the way this was programmed is rather then having the health just go straight to 100, the mechanic "heals "back up to 100% and then degens to 30%. Hence why MODOK can interact with the sig ability too.

You tend to have a habit of changing the narrative so we can't even take descriptions at face value, because if you don't like how we are benefiting from it then you simply "nerf" it and then say its meant to work like this.


Nick fury should be allowed access to his sig ability and the Real Nick Fury on these nodes and and it shouldn't be seen as healing.

And yet here we are with the company simply running away from the issue rather than doing the right thing

DalBot

Used him this morning and he went back to 1% and the degen was still there and he died immediately.

This is gross.