Alright everyone, the engineering team has done a thorough investigation on this one!Buckle up, it's about to get detailed. Here is what we know:This is a bug, but not with AI behaviour!The attack chain reset timer is based on attacks, it doesn't reset on run in (or even block, block react), and this is where the problem lies. Occasionally you'll get a medium 2 "out of nowhere." Usually summoners experience this as a whiff because only the first medium has a dash built in.Summoners are able to accomplish this as well, it just requires the opponent to Dex/Evade and a very precise, nearly frame-perfect, medium attack. Our team was able to reproduce this as an attacker.Some deeper analysis from the game team: "Although the defender did choose the 'wrong' attack animation in this case, the player would've been hit regardless. It might even be a disadvantage to the defender as they were subject to the post M2 cooldown and couldn't follow it up with a combo."So, as a result, the bug is summarized as: "Attack chain index isn't resetting to zero for certain non attack states"Because it came up during the investigation: what was the perceived disadvantage as an attacker in this situation? That the attack shouldn't have hit at all? Or that "the AI shouldn't have any tools that the Summoner doesn't?" Ok, glad you found a bug, but your way to explain it is that it was my fault anyway?Um, ok man. Whatever you say. Like it or not, that M2 was accelerated and my controls were locked out of a block or a dex as soon as it happened. You can see Spidey go into a block the second he recovers. Wow. Thanks for the response man, but turning it back around on me is ****. Maybe take your licks that your game is bugged beyond belief and fix it instead of taking every opportunity to blame the player. 🙄
Alright everyone, the engineering team has done a thorough investigation on this one!Buckle up, it's about to get detailed. Here is what we know:This is a bug, but not with AI behaviour!The attack chain reset timer is based on attacks, it doesn't reset on run in (or even block, block react), and this is where the problem lies. Occasionally you'll get a medium 2 "out of nowhere." Usually summoners experience this as a whiff because only the first medium has a dash built in.Summoners are able to accomplish this as well, it just requires the opponent to Dex/Evade and a very precise, nearly frame-perfect, medium attack. Our team was able to reproduce this as an attacker.Some deeper analysis from the game team: "Although the defender did choose the 'wrong' attack animation in this case, the player would've been hit regardless. It might even be a disadvantage to the defender as they were subject to the post M2 cooldown and couldn't follow it up with a combo."So, as a result, the bug is summarized as: "Attack chain index isn't resetting to zero for certain non attack states"Because it came up during the investigation: what was the perceived disadvantage as an attacker in this situation? That the attack shouldn't have hit at all? Or that "the AI shouldn't have any tools that the Summoner doesn't?"
Because it came up during the investigation: what was the perceived disadvantage as an attacker in this situation? That the attack shouldn't have hit at all? Or that "the AI shouldn't have any tools that the Summoner doesn't?"
Because it came up during the investigation: what was the perceived disadvantage as an attacker in this situation? That the attack shouldn't have hit at all? Or that "the AI shouldn't have any tools that the Summoner doesn't?" Personally I think the attack chain timer should be reset on walk in. Because it requires a perfectly timed M2, I don't think its something the average player could do. When the AI walks in you will be expecting the animation for a M1 and not a M2 and that could cause you to miss a block/parry that you would normally get.
Hmm. This is an interesting one!I've brought it to the engineers to see if they can sort out what's happening here!Thanks for bringing it to our attention. Thanks, @Kabam Jax … I appreciate the response, but I am going to pile on to what @Manup456 said.I happened to catch this on video, but stuff like this happens ALL OF THE TIME. This is not a unique case and it kinda sucks that it’s gotten to the point where I feel like I have to record every single fight that I do to capture this kind of stuff or I will not be taken seriously. In higher level game modes, it is constant. You can’t even punish heavy attacks anymore, without getting smacked by a special. AI behavior is out of control … this kind of stuff isn’t fun.
Hmm. This is an interesting one!I've brought it to the engineers to see if they can sort out what's happening here!Thanks for bringing it to our attention.
Alright everyone, the engineering team has done a thorough investigation on this one!Buckle up, it's about to get detailed. Here is what we know:This is a bug, but not with AI behaviour!The attack chain reset timer is based on attacks, it doesn't reset on run in (or even block, block react), and this is where the problem lies. Occasionally you'll get a medium 2 "out of nowhere." Usually summoners experience this as a whiff because only the first medium has a dash built in.Summoners are able to accomplish this as well, it just requires the opponent to Dex/Evade and a very precise, nearly frame-perfect, medium attack. Our team was able to reproduce this as an attacker.Some deeper analysis from the game team: "Although the defender did choose the 'wrong' attack animation in this case, the player would've been hit regardless. It might even be a disadvantage to the defender as they were subject to the post M2 cooldown and couldn't follow it up with a combo."So, as a result, the bug is summarized as: "Attack chain index isn't resetting to zero for certain non attack states"Because it came up during the investigation: what was the perceived disadvantage as an attacker in this situation? That the attack shouldn't have hit at all? Or that "the AI shouldn't have any tools that the Summoner doesn't?" Ok, glad you found a bug, but your way to explain it is that it was my fault anyway?Um, ok man. Whatever you say. Like it or not, that M2 was accelerated and my controls were locked out of a block or a dex as soon as it happened. You can see Spidey go into a block the second he recovers. Wow. Thanks for the response man, but turning it back around on me is [childish retort]. Maybe take your licks that your game is bugged beyond belief and fix it instead of taking every opportunity to blame the player. 🙄
@Kabam Jax Did you all hide this post? I can't find it in the first 8 pages of the forum, I can't search for it, and it's not updating to the top of the 1st page after I just posted to it?? The only reason I can still get to it is because I bookmarked it in my browser. What gives?