**WINTER OF WOE - BONUS OBJECTIVE POINT**
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
There is currently an issue where some Alliances are are unable to find a match in Alliance Wars, or are receiving Byes without getting the benefits of the Win. We will be adjusting the Season Points of the Alliances that are affected within the coming weeks, and will be working to compensate them for their missed Per War rewards as well.
Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.
Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.
Comments
I don’t get it. I started an initial thread about the changes to AA because I was surprised and wanted to get community thoughts on it. That led to Miike’s original post about AA being “bugged.” And that thread got closed with his comment, which is silly given the predictable fallout from Miike’s declaration.
There were then a couple of additional AA threads that could have easily been merged and managed, but instead continued to meander down slightly different paths. My “What is a Bug?” was one, and I actually learned a few things from the posts in it. It was an interesting follow on to all the talk about what is an “exploit” from a week or so back when 1.1.5 was a thing.
So...polite forums threads are often deleted or closed, derailing and demeaning comments stick around while innocuous ones disappear and official forums pronouncements can be completely disregarded.
Getting back to the point of this thread: the advent of 18.1. This isn’t an auspicious start.
Dr. Zola
The entire skill class is based on champs without powers. Gwenpool's one of the best, no need to change anything.
man this all way. i thought it was me touching my pad somewhere!
Miike, what you are stating here isn't bad per se, as the change in AA isn't that terrible. The point is that once more there is clear indication that not only the ones acting as proxies for Kabam can be not turstwhorty, but also that the controls over them aren't a thing. Whatever a Mod or Admin speaks on forums is and should be considered as Kabam speaking to users. And being so, should be subjected to controls.
Honestly, after reading the Sentry Info fiasco months ago, and numerous other istances in which you went back on your words, this creates a bad precedent. When champion's infos are describing them in a completely different way, or their abilities are, just to be conveniently adjusted whenever needed, then how do you think the community can trust you?
On top, the change wasn't even needed, unless one of the new to be released champions would have had In that specific AA ability a great counter. I hope this is not the case, cause it would cleraly mean you're just taking out pre existing counters to be able to release new ones later and cash more on them.
time will tell.
Meanwhile, RD specific champ tickets are due.
Those that said they didn't know about this feature until now just didn't know how to use him. It was written right on the character description that neurotoxin does not count as a debuff.
It's not a "it's safe to assume" thing... it's written right on his description.
If the stun was not suppose to be "does not count as a debuff".. then it should have been in a separate section. They do this with every other character when they want to separate properties (Medusa, Hela, etc).
The real answer is "we made a mistake in the text. it not actually a bug"... but well, it doesn't matter though. The mods are actively looking at this thread and will continue to not reply.
In an effort to take a few baby steps toward candor here, I’d like to clarify that a stun on CWBP generated by Neurotoxins will not be reflected unless AA is hitting CWBP at the precise moment of the Neurotoxin triggering stun. I ask this because my understanding is that only physical stuns are reflected by CWBP.
Is this correct @Kabamwhoever? And if so, why?
Dr. Zola
@DrZola would it matter if @kabamwhoever does answer your question? As long as they refuse to take responsibility for Mod statements and act as though it matters if said statements have real game consequences the Mod replies have no more weight than any other poster. Less really. Many people in the forum at least understand the game.
I believe the answer to your question is yes, based on other comments made. My reading of Kabam statements about this is that the game has designed BPCW so that when a stun is triggered on him, the game checks to see if his opponent is making contact. If so, the stun is reflected. It is an implementation quirk that the game logic does a check for contact, but doesn't do a check to see if the stun was the result of the same contact. It may be that at the moment the game tech (i.e. the game engine) doesn't have a way to check whether a stun was generated from a specific action that is currently making contact because there is no state variable that tracks that information.
The fact that it is considered a rare event is probably because the timing must be very close, within one or two frames of the moment of contact to be considered simultaneous.
With that said, I think the analysis from @DNA3000 is correct. If so, that’s actually a limitation that doesn’t bother me too much because it seldom happens. Split-second frame timing issue are understandable.
Dr. Zola
Exactly, they only make changes prior to something that may be beneficial to players in upcoming content. Check the history of changes.
Many here have theorized on why this is suddenly happening. Would Kabam be able to provide a definitive answer for us please?
The most popular theory is that because both feet are used in the attack, it causes 2 hits and therefore one of them hits her. It seems to me that this is just a glitch or a change in the reach of that attack. I will explain why by going into detail on the game mechanics:
First let me state that I hope this wasn't a "fix" done by Kabam purposely, because they thought that this was some sort of bug in the game, or a type of character exploit (like the recent changes with AA for example). The 2 hits detail should not matter and wasnt some sort of bug or exploit that she was fully evading both of these hits in the heavy attack. The reason behind her evade of both hits was because both hits happen in such a short time, relatively simultaneously, that when the first hit triggers evade, she is still in the evade process when the second hit comes and therefore it cannot hit her. Simply put, when the 2nd hit of the attack comes it is so similtaneous with the first that her evade buff from the first is still active (as you can clearly see when fully evading this heavy while in the middle of the screen.)
The second reason based on game mechanics, is that the evade puts enough space between them temporarily, that the 2nd hit just misses. The 2nd hit is actually a shorter hit than the first and should not be able to cover the distance between them that the first hit could not. Think if you are walking down a crowded hallway and u lean to the side to avoid bumping shoulders with someone coming towards you, but there is a second person you dont see right behind them. You would lean to the side and avoid bumping into both oncomers, even without seeing the other one coming because you were still leaning away to avoid the first.... Now, picture that same scenario but the second person that you dont see is a couple of seconds pace behind them, u would stand back upright and bump their shoulder.
Quake was always working correctly by avoiding both hits of that attack because she is still leaning backwards when the second hit comes. This game mechanic was never a flaw in the game or something that was a bug with Quake that needed to be fixed. The issue was with the heavy attack itsself, the hits are so close in the timing of when they are supposed to make contact that the 2nd hit still went by. Im not saying this is some sort of bug for that type of heavy attack, it is just how this heavy was designed to work. You can undertand this point better by looking at Quakes reaction while cornered by other different types of multi hit heavy attacks by other champions. Lets take Magik for example. She has more than 2 hits, but the timing of the second hit is so that it will hit you, unless you learn to dex out of it (which takes practice, but it definitely possible). Therefore, logically following game mechanics, if the second hit of the spiderman type heavy attack is able to hit you, then that means the 2nd hit MUST come AFTER Quake has recovered from the evade of the first hit. If that were truly what was happening, then there would be an opening to use dexterity to avoid that 2nd hit, as supposedly she was fully recovered from the evade.
Hopefully this helps to understand that there was no fix to be made. Everything was working according to the proper mechanics of the game. NOTE ALSO: Any evade type champion, Spiderman himself for example, still fully evades this type of heavy attack in the corner WITH A SINGLE EVADE. Quakes evade has always responded in the same exact manner, as it should have. There was no glitch here. an evade is an evade, whether you are Quake or whether you are Spiderman. One of these characters evade responding differently to the same exact attack is the glitch, not the other way around.
I hope that Kabam has taken the time to read this. If they did change this on purpose, I hope that they can now understand that there was nothing that needed to be fixed, everything was working exactly as it should have.
Many here have theorized on why this is suddenly happening. Would Kabam be able to provide a definitive answer for us please?
The most popular theory is that because both feet are used in the attack, it causes 2 hits and therefore one of them hits her. It seems to me that this is just a glitch or a change in the reach of that attack. I will explain why by going into detail on the game mechanics:
First let me state that I hope this wasn't a "fix" done by Kabam purposely, because they thought that this was some sort of bug in the game, or a type of character exploit (like the recent changes with AA for example). The 2 hits detail should not matter and wasnt some sort of bug or exploit that she was fully evading both of these hits in the heavy attack. The reason behind her evade of both hits was because both hits happen in such a short time, relatively simultaneously, that when the first hit triggers evade, she is still in the evade process when the second hit comes and therefore it cannot hit her. Simply put, when the 2nd hit of the attack comes it is so similtaneous with the first that her evade buff from the first is still active (as you can clearly see when fully evading this heavy while in the middle of the screen.)
The second reason based on game mechanics, is that the evade puts enough space between them temporarily, that the 2nd hit just misses. The 2nd hit is actually a shorter hit than the first and should not be able to cover the distance between them that the first hit could not. Think if you are walking down a crowded hallway and u lean to the side to avoid bumping shoulders with someone coming towards you, but there is a second person you dont see right behind them. You would lean to the side and avoid bumping into both oncomers, even without seeing the other one coming because you were still leaning away to avoid the first.... Now, picture that same scenario but the second person that you dont see is a couple of seconds pace behind them, u would stand back upright and bump their shoulder.
Quake was always working correctly by avoiding both hits of that attack because she is still leaning backwards when the second hit comes. This game mechanic was never a flaw in the game or something that was a bug with Quake that needed to be fixed. The issue was with the heavy attack itsself, the hits are so close in the timing of when they are supposed to make contact that the 2nd hit still went by. Im not saying this is some sort of bug for that type of heavy attack, it is just how this heavy was designed to work. You can undertand this point better by looking at Quakes reaction while cornered by other different types of multi hit heavy attacks by other champions. Lets take Magik for example. She has more than 2 hits, but the timing of the second hit is so that it will hit you, unless you learn to dex out of it (which takes practice, but it definitely possible). Therefore, logically following game mechanics, if the second hit of the spiderman type heavy attack is able to hit you, then that means the 2nd hit MUST come AFTER Quake has recovered from the evade of the first hit. If that were truly what was happening, then there would be an opening to use dexterity to avoid that 2nd hit, as supposedly she was fully recovered from the evade.
Hopefully this helps to understand that there was no fix to be made. Everything was working according to the proper mechanics of the game. NOTE ALSO: Any evade type champion, Spiderman himself for example, still fully evades this type of heavy attack in the corner WITH A SINGLE EVADE. Quakes evade has always responded in the same exact manner, as it should have. There was no glitch here. an evade is an evade, whether you are Quake or whether you are Spiderman. One of these characters evade responding differently to the same exact attack is the glitch, not the other way around.
I hope that Kabam has taken the time to read this. If they did change this on purpose, I hope that they can now understand that there was nothing that needed to be fixed, everything was working exactly as it should have.
Thank you for your time and consideration!
@Kabam Zibiit
@Kabam Loto
@Kabam Vydious
@Kabam Miike
@Kabam Rose
This is unacceptable Kabam and the MCoC community will not tolerate it. What's to stop you doing it to our other high level champs like blade and medusa who we've all heavily invested loads of money and time on? This will stop now and I won't be spending a dime on this game until you provide those with AA compensation as suggested by the plethora of players in the MCoC community who have been severely affected by this sudden announcement.
I agree with the simple solution Brother Idelest, some of the other youtubers/redditors and MCoC forum posters with providing players with rank down tickets and generic 5* awakening gems specifically for Archangel. This compensation needs to be provided asap to prevent a further boycott and further tension between the MCoC community and Kabam.
It speaks well of the patience of the community. Time will tell what it says about the game team.
Dr. Zola
Either post compensation or reinstate thr "bug".
P. S. Why should this stun should be reflected by BPCW?
There's a great video explaining some thoughts on the matter along with a reddit link to a discussion about it. I'm not posting this in an attempt to get the pitchforks out... I'm posting in hopes a moderator will actually pay attention to it and take it to whoever makes the real decisions. It's a simple thing to make this right and give players the confirmation that although this is an overall small change to a champion... They won't get screwed over in the future. That's 100% the worry that needs to be addressed.
https://youtu.be/8QSHDA8j_RQ
why cant those take priority instead of this. why cant you fix the game first then other characters?
you know what we need? old champs to become useful again! how do you do that? adjust them, like kabam mike they did for sentry, and do that for all the old, trashy, useless champs like ant man, spider gwen, oml, and such
CONSTRUCTIVE CRITICISM: if you can fix AA then you can fix bugs and old champs. leaving bugs on going just shows where your priority is and its not fair to your community who devote time and energy and money to this game
I just pulled a 4* AA 6 days ago. Awakened & ranked him up. If RDT were available, I'd consider ranking him down.