Sheesh 3.5 was a lot longer than even Bb and storm, and apologies you are correct 2.4 which means he should still be able to do two combos. And chain several stuns if you wait till he's near l2 before pulling l1, but yeah he could definitely do with a buff now to balance him, stun was his thing, and now that the stun is in line with other characters he doesn't have much going for him
@GroundedWisdom it's 1.6 seconds, 2 seconds would still make him useable and inline with other champs as you could start a second combo, but yes he needed fixing, noones saying leave him as he was, and your point about him being novelty is correct....now especially.
And your idea that they did the best thing they could is absurd. several suggestions have been made here that would make more sense than what they did, we are suggesting a better and less lazy address to the issue, if they can so quickly change his stun time, why not just his Stun percentage, why not give him a slight buff so people actually do care about getting him. More thought and more balance was all we were campaigning for
As much as I disagree with @GroundedWisdom on many occasions and I don't need to address it here, I'm sure most know why. He might be on to something. Firstly let me state that this is conjecture and not fact.
Some of the attributes of champs i.e. attack/defense/crit rates and ability modifiers such as stun durations, DoT rates may be configurable as live updates from the server. It pulls these values as it loads each screen, so that Kabam can tweak them whenever required. Synergies require changes in the client build... the app that we download each month. To avoid them having to do a new build and getting us to download it for this fix, they did the server updates.
You have to realise that a new update isn't just the single fix, it might have a lot of other changes in there as well that haven't been tested yet. It's almost impossible to roll out a single fix in isolation on the client. Then there is also the marketplace approval. The Android and iOS builds then need to be submitted to the respective marketplaces for approval before publishing.
This would explain why the fix was so fast and was an extremely efficient method for them to tie off the possible exploit. Having said that, I hope that Kabam reads this and doesn't take it as their final solution, just an interim one. There is no reason why they couldn't address the synergy in the next build and roll back the champ update.
For that matter, they would be Champ-specific, so if he was changed that significantly, the Tickets would only be given to those who have him, and only be usable on him. He wasn't changed that significantly either way.
For that matter, they would be Champ-specific, so if he was changed that significantly, the Tickets would only be given to those who have him, and only be usable on him. He wasn't changed that significantly either way.
So far I've only read complaints from people that have him and have ranked him up. So champ specific RDTs would suffice.
Not changed significantly? Kabam called it a game-breaking issue, that sounds significant. So it's either game-breaking and significant or it's not and don't change the champ.
The change to him was not significant. The effects of having a Champ that can lock and opponent into Stun indefinitely are.
Ok, you're mincing words. It equates to the same thing. The change allows him to be capable of stun lock or not be capable of stun lock, you can't separate the change from its effect. If you could, they wouldn't have changed him would they?
No, I'm not mincing words. It was a minimal change to prevent a much larger exploit. It does not equate to the same thing. The effect of not changing it is not equal to the means at which they prevented it. It was a small alteration that stopped a larger problem from developing. Reducing his Stun by a second is not a large change. Certainly not a nerf that constitutes Tickets. We haven't seen changes like that in almost a year. They aren't going to come out of any and all necessary changes to Champs, especially when said changes are crucial to preventing an exploit.
You have a small leak in your basement. If you leave it, it will eventually erode and flood the entire basement, causing mold and mildew, ruining your home and everything in it. You can apply a small patch to stop the leak. The patch is quite small compared to the damage the leak will do. Only in this case, erosion happens at the speed of light.
It's a stretched analogy, but the bottom line is just because they made a change to prevent a serious problem doesn't mean the change is equally as serious.
The pun is intentional, your analogy does not hold water.
1) The small patch that you applied to the leak does not functionally change the basement. It would be more accurate to say, to patch the leak in your basement, I'm going to fill a third of it with concrete.
2) They've already indicated that the leak is causing severe damage because it is game-breaking should it be exploited. In other words, it's a massive hole that is waiting for a heavy downpour.
You seem to be the one arguing semantics, and you claim I'm mincing words. Here is a more direct approach.
The change doesn't warrant Tickets because it wasn't a major change. They're not for any and all changes to Champs. Although they come up anytime something is fixed.
For some reason, your claim is because an exploit is major, the response to prevent it is just as major. Not the case. Small changes can prevent larger issues.
TL:DR - It wasn't a major change. Not the kind that would warrant Tickets. This was not a planned change to the function of the Champ as well. It was necessary to prevent an exploit.
I would argue an extra combo per l1 is a major change, there are so few in circulation I would
Have no qualms about champ
Specific rdts myself; but I don't like rdts as a rule, I honestly think
Kabam should just throw him a bone here and give him a buff, he is rare and has been a sought after champ, 3.5 second stun was a big deal, 2.5 worse than storm and bb. With 3.0 you can get in: mllll heavy mlllm, now he can't even get the heavy in like they can
People saying it's not a significant change have never used Kang. He was a good champ - not just a novelty. With his unique long stun on L1 if you managed your power bar carefully you could use it to finish a difficult fight but it wasn't permastunning - it was a risky way to not get L3'd. It was one of the things that made him fun to play and could be kind of a rush if you played it perfectly - but one slip up and you're dead. That was without any synergy. I have never used him with power gain synergy because I never sought to exploit the game and I certainly would never use his pillow hands to "perma stun" for 700+ hits and go bored out of my mind.
I see that no one has responded to my reasonable suggestions on how to fix this issue without nerfing the character and I see that Kabam has issued stripped down ("nerfed") RDTs to everyone. But I'm not even going to use them. Frankly that doesn't cut it because of the other resources invested - not mention the units involved in people even chasing this rare champ to begin with.
It doesn't matter though. I've already moved on. I've been stonewalled by customer service and warned by the mods for speaking truth so that's all the answer I need to know that this is not a company I wish to support any longer. You get robbed and then you get told to suck it and get back in line. Who subjects themselves to this? This is not entertainment. Good luck folks. It's been fun. Well... in the beginning maybe... but now not really. I'm out.
Comments
As much as I disagree with @GroundedWisdom on many occasions and I don't need to address it here, I'm sure most know why. He might be on to something. Firstly let me state that this is conjecture and not fact.
Some of the attributes of champs i.e. attack/defense/crit rates and ability modifiers such as stun durations, DoT rates may be configurable as live updates from the server. It pulls these values as it loads each screen, so that Kabam can tweak them whenever required. Synergies require changes in the client build... the app that we download each month. To avoid them having to do a new build and getting us to download it for this fix, they did the server updates.
You have to realise that a new update isn't just the single fix, it might have a lot of other changes in there as well that haven't been tested yet. It's almost impossible to roll out a single fix in isolation on the client. Then there is also the marketplace approval. The Android and iOS builds then need to be submitted to the respective marketplaces for approval before publishing.
This would explain why the fix was so fast and was an extremely efficient method for them to tie off the possible exploit. Having said that, I hope that Kabam reads this and doesn't take it as their final solution, just an interim one. There is no reason why they couldn't address the synergy in the next build and roll back the champ update.
I am sure i will get a warning for this, but if you take away his orginal ability rank down should be issued.
So far I've only read complaints from people that have him and have ranked him up. So champ specific RDTs would suffice.
Not changed significantly? Kabam called it a game-breaking issue, that sounds significant. So it's either game-breaking and significant or it's not and don't change the champ.
Ok, you're mincing words. It equates to the same thing. The change allows him to be capable of stun lock or not be capable of stun lock, you can't separate the change from its effect. If you could, they wouldn't have changed him would they?
It's a stretched analogy, but the bottom line is just because they made a change to prevent a serious problem doesn't mean the change is equally as serious.
1) The small patch that you applied to the leak does not functionally change the basement. It would be more accurate to say, to patch the leak in your basement, I'm going to fill a third of it with concrete.
2) They've already indicated that the leak is causing severe damage because it is game-breaking should it be exploited. In other words, it's a massive hole that is waiting for a heavy downpour.
You want to try again?
The change doesn't warrant Tickets because it wasn't a major change. They're not for any and all changes to Champs. Although they come up anytime something is fixed.
For some reason, your claim is because an exploit is major, the response to prevent it is just as major. Not the case. Small changes can prevent larger issues.
TL:DR - It wasn't a major change. Not the kind that would warrant Tickets. This was not a planned change to the function of the Champ as well. It was necessary to prevent an exploit.
Have no qualms about champ
Specific rdts myself; but I don't like rdts as a rule, I honestly think
Kabam should just throw him a bone here and give him a buff, he is rare and has been a sought after champ, 3.5 second stun was a big deal, 2.5 worse than storm and bb. With 3.0 you can get in: mllll heavy mlllm, now he can't even get the heavy in like they can
I see that no one has responded to my reasonable suggestions on how to fix this issue without nerfing the character and I see that Kabam has issued stripped down ("nerfed") RDTs to everyone. But I'm not even going to use them. Frankly that doesn't cut it because of the other resources invested - not mention the units involved in people even chasing this rare champ to begin with.
It doesn't matter though. I've already moved on. I've been stonewalled by customer service and warned by the mods for speaking truth so that's all the answer I need to know that this is not a company I wish to support any longer. You get robbed and then you get told to suck it and get back in line. Who subjects themselves to this? This is not entertainment. Good luck folks. It's been fun. Well... in the beginning maybe... but now not really. I'm out.