Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.Yup. Here’s the explanation for that one. I’ll add hap crappens, (this means noone’s perfect even if you believe they are.)“Hey Everybody,I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can.This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower.With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority.We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.” And its not like the bad information was a rogue moderator. The issue was reported in the bug thread, a moderator said it would be looked into, and the thread was labelled "under investigation." Then the moderator came back and announced that it was not a bug, and closed the thread labeling it "not a bug." Presumably the moderator was reporting the findings of the game team, so it was more than just "a moderator gave you incorrect information."I don’t think you remember the originating thread about AA’s stun. Let’s review it. BRB.Ok back. Nope not what you remember. The moderator just responded without marking it under investigation nor coming back. It was an off the hip response.Check for yourself. https://forums.playcontestofchampions.com/en/discussion/comment/252890#Comment_252890Check yourself.*wrong link Fair enough. Scratch that part of the narrative. Doesn't change the point though. Was the point that asking offers no assurances? Yeah it doesn’t 100% however it’s the best you’re going to get. Here’s the question now. And this isn’t a slight it’s being used for comparative purpose. You’ve admittedly been incorrect in your assertions, should people treat you as they do Kabam and trust anything you ever say?
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.Yup. Here’s the explanation for that one. I’ll add hap crappens, (this means noone’s perfect even if you believe they are.)“Hey Everybody,I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can.This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower.With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority.We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.” And its not like the bad information was a rogue moderator. The issue was reported in the bug thread, a moderator said it would be looked into, and the thread was labelled "under investigation." Then the moderator came back and announced that it was not a bug, and closed the thread labeling it "not a bug." Presumably the moderator was reporting the findings of the game team, so it was more than just "a moderator gave you incorrect information."I don’t think you remember the originating thread about AA’s stun. Let’s review it. BRB.Ok back. Nope not what you remember. The moderator just responded without marking it under investigation nor coming back. It was an off the hip response.Check for yourself. https://forums.playcontestofchampions.com/en/discussion/comment/252890#Comment_252890Check yourself.*wrong link Fair enough. Scratch that part of the narrative. Doesn't change the point though.
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.Yup. Here’s the explanation for that one. I’ll add hap crappens, (this means noone’s perfect even if you believe they are.)“Hey Everybody,I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can.This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower.With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority.We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.” And its not like the bad information was a rogue moderator. The issue was reported in the bug thread, a moderator said it would be looked into, and the thread was labelled "under investigation." Then the moderator came back and announced that it was not a bug, and closed the thread labeling it "not a bug." Presumably the moderator was reporting the findings of the game team, so it was more than just "a moderator gave you incorrect information."I don’t think you remember the originating thread about AA’s stun. Let’s review it. BRB.Ok back. Nope not what you remember. The moderator just responded without marking it under investigation nor coming back. It was an off the hip response.Check for yourself. https://forums.playcontestofchampions.com/en/discussion/comment/252890#Comment_252890Check yourself.*wrong link
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.Yup. Here’s the explanation for that one. I’ll add hap crappens, (this means noone’s perfect even if you believe they are.)“Hey Everybody,I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can.This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower.With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority.We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.” And its not like the bad information was a rogue moderator. The issue was reported in the bug thread, a moderator said it would be looked into, and the thread was labelled "under investigation." Then the moderator came back and announced that it was not a bug, and closed the thread labeling it "not a bug." Presumably the moderator was reporting the findings of the game team, so it was more than just "a moderator gave you incorrect information."
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.Yup. Here’s the explanation for that one. I’ll add hap crappens, (this means noone’s perfect even if you believe they are.)“Hey Everybody,I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can.This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower.With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority.We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.”
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended.
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?
This was not a mechanic of this Champion, and was not mentioned as one. All Champions have the same speed and cadence to their Attacks, and no Champion should be able to combo into a Heavy attack with 100% reliability.
Last point, and one that troubles me: it feels deeply out of touch for the team to drop this into the changelog unceremoniously and without any dialogue or explanation. I don’t ascribe that to sneakiness; I just don’t get it.
Tell me, Kabam: How in the world am I supposed to know if a champion works as intended or not?You can ask them, if you’re afraid to ask them that’s a good indicator it is unintended. Nope. Asking them won't do it. People asked about AA and were told specifically that it wasn't a bug...until it was.Yup. Here’s the explanation for that one. I’ll add hap crappens, (this means noone’s perfect even if you believe they are.)“Hey Everybody,I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can.This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower.With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority.We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.” And its not like the bad information was a rogue moderator. The issue was reported in the bug thread, a moderator said it would be looked into, and the thread was labelled "under investigation." Then the moderator came back and announced that it was not a bug, and closed the thread labeling it "not a bug." Presumably the moderator was reporting the findings of the game team, so it was more than just "a moderator gave you incorrect information."I don’t think you remember the originating thread about AA’s stun. Let’s review it. BRB.Ok back. Nope not what you remember. The moderator just responded without marking it under investigation nor coming back. It was an off the hip response.Check for yourself. https://forums.playcontestofchampions.com/en/discussion/comment/252890#Comment_252890Check yourself.*wrong link Fair enough. Scratch that part of the narrative. Doesn't change the point though. Was the point that asking offers no assurances? Yeah it doesn’t 100% however it’s the best you’re going to get. Here’s the question now. And this isn’t a slight it’s being used for comparative purpose. You’ve admittedly been incorrect in your assertions, should people treat you as they do Kabam and trust anything you ever say? If my assertions are to my customers and they cause people to buy things from me based on the misinformation, after which I admit my error but say I won't offer compensation since it was an honest mistake, then yes. They probably shouldn't trust me after that.
Just saw quake's description as well ,it doesnt say anywhere she can hold Heavy or charge heavy for any extended duration. like hela or kamala she should also throw heavy automaticaly after charging for few seconds??? redskull's ability clearly states he can hold heavy for extended duration
Just saw quake's description as well ,it doesnt say anywhere she can hold Heavy or charge heavy for any extended duration. like hela or kamala she should also throw heavy automaticaly after charging for few seconds??? redskull's ability clearly states he can hold heavy for extended duration It says she evades basic attacks when concussion is placed. Guess what places concussion
Last point, and one that troubles me: it feels deeply out of touch for the team to drop this into the changelog unceremoniously and without any dialogue or explanation. I don’t ascribe that to sneakiness; I just don’t get it. That's easy: tunnel vision. It seemed like a minor change to the person making it, and they were just wrong, and no one else critically reviewed it. It happens. Remember a team didn't do this, a person did. And if it wasn't reviewed as thoroughly as it should have been, again it was a person that failed to do that. And individuals make mistakes that we often assume a team shouldn't make collectively.The larger issue is that the changelog should be the last in a long line of bug management processes. It is asking too much for the changelog to fully document everything about the lifecycle of a bug's discovery, analysis, discussion, and remediation. If the changelog was part of a larger better process, then the changelog itself wouldn't be necessarily problematic.One more thing: I don't know the ins and outs of Kabam's development process specifically, but in my experience different parts of a game like this are often worked on by different people and there's a glitch I've seen affect more than one dev team. Things like animations are often worked on by different people than things like mechanical content - what we'd call things like abilities and effects. That makes sense because the work and the skills required are often radically different. But there's a tendency to think of the abilities and effects as being one thing that determines what "happens" in the game, and the animations and sequences as being a different more superficial kind of thing. That's *usually* true, but there's often an overlap where how an entity moves can critically affect what they can do, and this game is no exception. If there's a "cultural instinct" to assume that animations are cosmetic and abilities are consequential, a bug fix in the animation section of the game might not get the critical review attention it deserves. I've seen this mistake happen on a scale that would make the She-Hulk change look miniscule by comparison.
This was not a mechanic of this Champion, and was not mentioned as one. All Champions have the same speed and cadence to their Attacks, and no Champion should be able to combo into a Heavy attack with 100% reliability. Over time players become aware that different champions have different frames and speeds of animations to their attacks. When you use Quake you have to adjust how quick you alternate between using evade/dexterity and charging heavy attacks depending on who you are fighting. Against MODOK, you alternate these two things faster because MODOK’s light attacks animations are faster than most champions. Against Spider-Man Classic, you alternate evade/dexterity and charging heavy attacks slower because Spidey’s basic strikes animations are slower than average. The above example also applies to other champions like Proxima Midnight and Doctor Voodoo. Intercepting strategies get tweaked against different champions because certain champions’ medium attacks have faster animations than other champions. Additionally, certain champions’ medium attacks make contact earlier than other champions’ medium attacks. Venom, Thanos, and Unstoppable Colossus are champions’ whose medium attack animations are faster than average. Corvus Glaive, Warlock, and Sentinel are champions whose medium attack animations make contact later than average.DickSlug - one of the most knowledgeable members of the MCOC community - has previously explained these things as products of MCOC’s unity engine game mechanics (see below). His explanation of MCOC hitboxes is invaluable when learning how to take your MCOC skills to higher levels. My bad in advance if my interpretation of Miike’s and DickSlug’s writings are off:https://www.reddit.com/r/ContestOfChampions/comments/5lnvcj/hit_detection_explained/?utm_source=share&utm_medium=ios_apphttps://www.reddit.com/r/ContestOfChampions/comments/5lj2l1/whiffing_explained_with_pictures/?utm_source=share&utm_medium=ios_app
But I find your first paragraph implausible. Why? Because there’s almost certainly a process for triaging bug fixes, which is what we’ve been told, more or less, in these forums. It seems odd to think that coders just take a look at the list of known and unknown issues and pick a random bug to fix without someone deciding the ones that take priority over others. And if chaining heavies at the end of a combo was a big game issue, this would likely have been a global fix, not a champ-specific one.
You stated a timetable for this change - not sticking to the timeline further illustrates how poor your communication is.This suggests that your data noticed a rush of players going 6.2.6 champion using her style. Adjusting her kit is up to you, but readjusting your timeline for the adjustment clearly shows that you are targeting players progression with the rationale of the change. Players ranked this champion specifically for this encounter and should have at least be granted a week to work on it, as was communicated. All we ask for from you is better communication.
DickSlug - one of the most knowledgeable members of the MCOC community - has previously explained these things as products of MCOC’s unity engine game mechanics (see below). His explanation of MCOC hitboxes is invaluable when learning how to take your MCOC skills to higher levels. My bad in advance if my interpretation of Miike’s and DickSlug’s writings are off:https://www.reddit.com/r/ContestOfChampions/comments/5lnvcj/hit_detection_explained/?utm_source=share&utm_medium=ios_apphttps://www.reddit.com/r/ContestOfChampions/comments/5lj2l1/whiffing_explained_with_pictures/?utm_source=share&utm_medium=ios_app