Node 38 + IMIW =bugged A broken champ for a broken node.
Vale84
Member Posts: 308 ★★★
Reporting this cause, honeslty, having to run tests in stead of you guys at kabam ( @Kabam Miike @Kabam Vydious @Kabam Zibiit @Kabam Zibiit ) is something that i don't mind doing, if it wasn't almost half season 2 ongoing.
Apparently there is an unprecedent interaction between Corvus Glaive and the new IMIW on node 38. Parrying Iron Man there activates his ability indeed, and all the stacks of armor are broken. BUT the armors gained through the node aren't removed. You find then yourself fighting with an opponent where 6 stacks of armor breaks and 6 stacks of armor up cohesist same time. Parrying a second time, now that he has 9 stacks, adds 9 more armor breaks, but again, doesn't remove the armor ups.
How does this even happen. Don't let me hear "cause the node's armors are passive", because so are IMIW's own ones. On top, before releasing a champion which will inevitably become the most hated in the whole war scenario, can you at least, please, care about checking its interaction to what was the obvious node he'd be used on BEFORE we have to find out in a master war in the middle of season, going there with a PROPER (even listed) counter just to find out it doesn't work as it should?
Just to make an example, in the last war we faced a LoL Ultron on the same node, and corvus could break EVERY single armor being it Ultron's own, the node stacking one, or the "hit guard" triggered one. So clearly, looks like a bug to me.
Waiting an answer, thanks for your time. And thanks for letting us gift a death or more without reason midseason, i guess. *smh*
Apparently there is an unprecedent interaction between Corvus Glaive and the new IMIW on node 38. Parrying Iron Man there activates his ability indeed, and all the stacks of armor are broken. BUT the armors gained through the node aren't removed. You find then yourself fighting with an opponent where 6 stacks of armor breaks and 6 stacks of armor up cohesist same time. Parrying a second time, now that he has 9 stacks, adds 9 more armor breaks, but again, doesn't remove the armor ups.
How does this even happen. Don't let me hear "cause the node's armors are passive", because so are IMIW's own ones. On top, before releasing a champion which will inevitably become the most hated in the whole war scenario, can you at least, please, care about checking its interaction to what was the obvious node he'd be used on BEFORE we have to find out in a master war in the middle of season, going there with a PROPER (even listed) counter just to find out it doesn't work as it should?
Just to make an example, in the last war we faced a LoL Ultron on the same node, and corvus could break EVERY single armor being it Ultron's own, the node stacking one, or the "hit guard" triggered one. So clearly, looks like a bug to me.
Waiting an answer, thanks for your time. And thanks for letting us gift a death or more without reason midseason, i guess. *smh*
5
Comments
fun times.
The fact it can be soloed doesn't change the evidence the node is bugged if IM is on it. else we would see all other defenders there with the same weird armor-armor breaks ratio.
Armor break is defined as "-xxx armor, removes an existing armor buff"
Where armor break appears there can't be armor ups unless you apply one AB on a stack of more than 1 armor ups. Since corvus converts ALL armor ups in armor breaks, there should be none left.
So props to your guys who had to deal with the bug and managed, but the node itself needs be addressed.
It's NOT a bug.
Never anywhere does Aggression: Armor's node mention the armors can be removed by an Armor Break. I recall fighting the aggression node with an armor breaker (Medusa) and extra armors weren't removed. Armor Break specifically states it removes a stack of the Armor buff, which this isn't. The only way to remove Aggression: Armor is to hit him.
So...yeah.
This is a perfectly functioning broken champ.
Have fun guys!
But IMIW's sheet says autoblock can trigger from 4 stacks of 'any' armor. So again. Not a bug.
When he is under 15% health, his autoblock can trigger from ONE of any armor. So again. U can do nothing with NODE38.
Actually I just pulled him so yup not a bug working as intended great design lol
Please avoid spreading false infos. Any other champ defending that node can be armor broken and the stacks from the node can as well. I mentioned as example LoL ultron but anything goes really.
What you might wanna say is that shatter is ineffective? Alas im bot sure, but armor break works 100% against ANY armor of that node IMIW excluded.
Which EVEN if was true would only need even more of a fix.
PS: and not just that. Node s armor count too towards his critical resistance. With the consequence that people is needing 30 hits plus to remove the last 15% due to doing close to 0 dmg even with little stacks of armor.
There are ways around that even on 38. The problem lies in the fact armors wont go down and will eventually pile up. And since node armors (for no reason) not only count for autoblock but even for critical resistance, the last 15% will take ages since your char wont ever crit, and will deal super low dmg on non crits. We re talking a r5 5* stark spiderman dealing 750 dmg on a heavy with 10 stacks of poise. Which is broken.
Like these buffs can be nullified by mystics
They don't interact with MD
Mephisto 's soul imprisonment doesn't stop it
Magik's l3 doesn't work
So yeah if you're not hitting him, his armors from the aggression node aren't going away.
Also please remember that modok was bugged when he was released and they took their own sweet time fixing it.
Again rather than speaking by theory (im armors are passive too and get removed by AB), you should rather see for yourself.
That ia armor up from the node (every 2 seconds). The whole video has CG break all armors and easily smashing through ultron.
So no, armors from node arent unremovable and
YES, armor break removes them
But not if iron man ia on the node.
Once more, back again with the only advice you ever give anyone. Buy FGMC. Incredible.