Best Of

kinda owe the players a reasonable time frame to fix something, 2 years is unacceptable, kabam are not a small company

Fear me for my name is ONSLAUGHT

DTHANOS: LOL

yeah, just when I start to get gloomy about the nerf and all the other unintended interactions that will eventually ruin my favorite champs, I just toggle over to my statcast roster… and all the rain clouds go away.

Well to be fair to Kabam we did:-

1. Asked for new stats for our Statcast relic....oh wait
2. Kabam did informed the players well in advance of Hulkling and Valkyrie issue before players start to ranked those two champions up for the then upcoming BG meta.…oh wait
3. Kabam did manage to "fix" Hulkling and Valkyrie in time for players to use in those BG weeks...oh wait
4. Kabam did work really hard to fix Hulkling and Valkyrie properly so it didn't have any impact to the rest of the game, it not like they took the easiest option...oh wait
5. Kabam informed the players well in advance that they were planning to work on Protection "fix" and how it would affected Daunted…oh wait
6. Well at least no Kabam Champion design stated in their deep dive that Daunted does work against Protection...oh wait
7. Well at least Kabam managed to fix 2 champions without nerf another 5...oh wait
8. Well at least Kabam is an competent company and care about its players...oh wait
9. Well at least it not all about money…🤣🤣🤣

Respectfully, this was not a bug or unintended feature. As some one explained above, protections and resistances have always been additive. That is why a champion with 100% bleed resistance can still take bleed damage if the potency exceeds 100%. Why give resistance instead of immunity if there was not an intended way to still cause damage?

That said, Kabam can of course change the game how they see fit for its health. A point you have raised on numerous occasions so I won’t belabor it. The issue, once again, is that they did it without any communication or player input. Clearly, they knew of this change (ie, that they were going to eventually change how protection works) before the update went live. Unlike the weeks it took for Mike ans Kabam to investigate what was going on with hulkling, he immediately had a well detailed update on the situation yesterday (only after players realized the change). That should have been communicated immediately to the players once known. That’s the scummy behavior players are really mad about.

What a brain dead and tone deaf thing to say. 2 years since a champs release + not mentioned in the spotlight, and yet somehow your smooth brain actually typed this out.

As soon as Kabam make the decision there is a problem that needs to fixed it should go on the Trello board. That’s what it’s for. They didn’t add it. They once again go for the route of keeping us all in the dark and then try and convince us Kabam are communicating with us. Kabam deserve all the backlash they get.

I mean to follow up on my previous comment. When it was brought to their attention of hulkling and Valkyrie. Only a couple of business days later, Mike responded with:

"Hey folks, we're continuing to investigate this one -

In the meantime, I can confirm 

there have been no intentional changes to Hulkling or Valkyrie's damage output for this release.

If we determine something did change somewhere in the underlying damage calculation, we will either revert that change or update Hulking and Valkyrie's kit to bring their damage output as close as possible to parity with their historical performance, as you would expect from them."

Implying that he hasn't looked into it yet. But interesting enough, 2 weeks later.. It was exactly that. It "wasn't intentional" and "we will try to have them as close to before as POSSIBLE" but ya know, due to the game and how things interact

I don't know if that's the common response to a bugged champ but it seems very interesting that the inevitable and not common outcome was suggested in the initial response. When the typical outcome is, we will look into it or we will ensure that these Champions meet their earlier output.

DLL explains the daunted and protection interaction at around 4:20 timestamp.