**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Comments
Coldsnap at beginning of fight hits for 420 per tick.
When Ice Phoenix does s1, and hits me, only deals 265 per tick.
Is this working as intended?
You lost half your health without Voodoo's regen. That node has heal block.
Shouldn't Iceman be immune to coldsnap? I was surprised it wasn't...
Difficult ties in w skill level....whereas unavoidable damage is just a matter of Kabam’s favorite “insert coin to play” mentality. And we can all agree that that can be insanely unnerving....
Can't speak for exact numbers, but in general icebros coldsnap from l1 is weaker than the one from his sig.
I hate to tell you this but the node still does a lot more damage. I had a 5/50 drax with 11k hp and I went in the fight, I did not even take a blocked hit from Ice Phoenix and she still knocked me out just with the cold snap damage. Her sig ability says she can only do 4.5k damage over 12 seconds but my drax just lost over 11k hp from cold snap.
I'm pretty sure no one was arguing that there were no champions with counters to cold snap. The question is whether it is reasonable for that champion to have so few specific champion counters.
Also, scaling up the damage you are seeing with Rogue, even with her 70% shake off the original version of Ice Phoenix would have dealt about 5500 damage to Rogue, about half her health, with cold snap alone. That means even if it was possible for Rogue to kill Ice Phoenix as fast as Seatin did with Star Lord (which is impossible) and even if it was possible to do so with as few blocked hits as Seatin's Star Lord (again, impossible because of the huge difference in damage) you'd still have taken at least 2324 damage on top of cold snap. With heal block in effect, I don't think many players could one-shot Phoenix with 4* Rogue without lots of practice tries.
Even scaling Rogue up to 5*, I think it is unlikely someone using 5* Rogue could have finished the fight taking less than 10k damage from Ice Phoenix, half of that from Cold Snap alone, and even with Rogue's immense 70% reduction in Cold Snap duration. And outside of Agent Venom and Mephisto, that's the best case scenario.
It isn't a question of whether it is doable at all, but whether it is reasonable for the difficulty level. And even the highest difficulty level content has a reasonable ceiling on difficulty.
By my calculations, Cold snap should deal about 10750 damage from Cold snap assuming no class advantages/disadvantages. Her sig ability sheet doesn't factor in the fact that she is sitting on a +150% damage node. That's not enough to defeat an 11k health champion, but I suspect you're exaggerating when you say you didn't take a single blocked hit. It would literally take only one blocked hit to turn 10750 to 11k.
My only point is that people went out of their way to unit or item their way through the fight without any need for it. This fight is doable with a 3 star Mephisto just like the 6 star boss rush Mephisto could be solo'd with a 3 star Mephisto.
Instead of just powering through content there is usually a better, smarter way of getting it done. That's all I was saying. It won't stop anyone from complaining about a challenge in the game though.
I wish I had a video proof for this, but you’re free to assume. I’m stating the fact, I only intercepted. No hits blocked.
I just tried fighting against her and my character does no matter what in about 10 seconds, no hits, just that Ice death...even if it’s a robot like Ultron or Vision, doesn’t matter, just dies.
I though you guys fixed this? I can’t see under any circumstance how this can be considered fair and/or competitive in any way.
Fair enough. However, the calculated difference between what the adjusted cold snap is going to deal and your stated health of your attacker is, without any documentation to the contrary, sufficiently within the margin of error to be consistent with the ~40% reduction in damage the devs altered Cold snap to do.
I should reiterate that there was no bug that Cold snap was doing more damage than the character sheet shows. That's not a bug and that's not what the devs changed. Cold snap does more damage than the character sheet shows because Ice Phoenix is on a +150% buff node which the character sheet does not account for. The devs reduced the damage of Cold snap because it was doing more damage than intended or desired, not more damage than the character sheet claimed.
Do it and post a video
Coldsnap takes your entire energy before the nerf. Her attack was 10k, so if you block, you absorb the impact which further depletes your energy.
[Edited by Moderation]
It should be extremely difficult to get this rewards, but it should be about skill, not spending ridiculous amounts of resources.
That way you can 'avoid' public critisms saying that you don't test your product before letting the public use them. LOL
They did not change her rank. They changed the signature level of her signature ability which is to start the fight with cold snap. I believe it was sig 100 originally and it was reduced to sig 10. It originally did 7078.28 damage over 12 seconds (unbuffed) and it was lowered to deal 4375.56 damage over 12 seconds. Ice Phoenix sits on a +150% damage node, so the real damage of cold snap was originally about 17695.7 (7078.28 x 2.5) and was lowered to about 10938.9 (4375.56 x 2.5). Those numbers are approximate because I don't know how the game rounds off damage numbers when it delivers damage over time. In terms of visible damage it appears to be 24 ticks of 448 damage which would add up to 10752 damage.
Encountered many intended mistakes? Lol.
I believe you have something backward there. The natural conclusion when a company states that all of their errors are unintended is that they were not properly tested. In the software world the joke is that if you don't want to admit something was an unintended error, the bug is called a questionable feature.