So what steps have been taken with all the data reported in the format as requested thus far? @Kabam Zibiit
Lets be honest it happens with every champ on every device. They know it. We all know it. Its extremely easy to recreate with every champ against any champ. Come on
I just want to make sure we're all on the same page here. In my first post on this thread, I highlighted that there were two types of backdraft intercepts. I believe the first one was fixed and is working normally now since a fix that was pushed out a few weeks back. What we are concerned with is the second type of backdraft intercept - this is the one where you hit the opponent when they are holding block, followed by a back dash by the player, and a quick light attack to hit them when they dash in at us.
Just wanted to make sure that the game team is looking at the correct backdraft intercept technique, so we avoid a situation where the game team gets back and says they cannot re-create the bug.
AI still has the ability to hit you before you can hit them.....
This is honestly one of the biggest disappointments to land next to all the other bugs. Plus the fact you let it slide for another month and released a stun immune yellowjacket with glancing in your EQ.
Whats your counter to a stun immune fight?....
Backdraft intercepts and baiting specials....
Whats your counter to a stun immune fight with no backdrafting?
Tons of block damage taken and item use.
I feel sorry for the summoners trying to complete Variant 1 with all these issues since backdrafting was one of the main clearing techniques for the masochism chapters.
Also i'm using an iphone 7+. Worked just fine until your Annihilus update patch. I see you implying in threads that this is "performance" related perhaps...so lets talk performance and gaming....
Buy a PS4; 5-7 years shelf life of top end gaming
Buy a Gaming PC; 7-10 years of top end gaming
Buy a Gaming Phone(iPhone); 2 years top end gaming until performance issues....
Might want to reconsider bumping up those graphics and rendering artifacts to make your game look pretty while ignoring hardware standards in the gaming industry thats well established before mobile gaming.
If you need to dish out 1-2000 dollars every 2 years for a mobile game to be playable then perhaps we all need to rethink what we are investing in here.
Oh and FYI its happening on iphone XS max users phones too so i guess that performance issue is no longer debatable BUT I just decided to include some gaming knowledge regardless.
Thanks for the additional information everyone. It has been passed on for review.
Any updates since? Its been nearly a week since this was passed on for review. The first reports of the bug have been out for more than 6 weeks by now. I don't see what is taking this long.
Kabam Miike said in a separate thread that you guys have people who tested the new AW nodes, which would presumably include the Aegis (intercept) node. Really curious - did nobody testing these nodes attempt to clear it with the backdraft intercept technique? Because if anyone testing had a modicum of skill they would have realised that the backdraft intercept technique would be the safest way to clear the node and would also have realised that it was broken at the time.
@Kabam Miike post a video of yourself backdrifting after hitting into their block (they must then dash out at you and you intercept) and I’ll believe you when you say the AI hasn’t changed.
I also think it’d be good for us to show our failed attempts at backdrafts to simply prove that the AI has been altered. The only time I can dash in and out after a blocked hit is when they try a light attack or stand still. If they dash in after I hit their block it’s game over for me...
Kabam Testers, try hitting into block two or three times w a short to midrange dash back champ. go back for the intercept. you will more than likely get hit. This is so easy to reproduce. I test it every few days just to see if its fixed. it is still BROKEN. can we get some sort of update on this? how am I supposed to believe the AI wasn't messed with when this used to be doable? so if it wasn't an AI tweak, its a bug. either way, a comment stating that it's one or the other would be appreciated.
So in testing this some more for free, it seems this is most likely to happen if you have opponent against the wall, hit block twice, and dash back for the intercept. opponent will hit you before you can do anything. playing opponent against the wall is a risky proposition these days anyway, as I've also noticed that finishing a five hit combo with them against the wall and dashing back can also get you wrecked. Same with launching specials with them against the wall. sigh.
So in testing this some more for free, it seems this is most likely to happen if you have opponent against the wall, hit block twice, and dash back for the intercept. opponent will hit you before you can do anything. playing opponent against the wall is a risky proposition these days anyway, as I've also noticed that finishing a five hit combo with them against the wall and dashing back can also get you wrecked. Same with launching specials with them against the wall. sigh.
Good observation, I hope it gets fixed. I don't understand how we can rely on skill when we don't have the tools.
At this point I'd be happy if they would just let us know what's going on. Is this a bug or not? If not, it was an intentional change? Some communication on Kabam's part, even a quick "We're still working on a fix" or "git gud" would at least let us know we're being heard on this. This would be welcomed in some of the other threads that have been open for months, namely the SS bugs and launching specials on block.
I'm pretty sure this is due to an animation/frame rate change or an AI change. It came along with a ton of other bugs like Sentinel and X23 not allowing you to punish their special 1s anymore. Just wish they'd revert it back to how it was.
It is a staple in any players toolkit, it needs to be preserved or all stun immune content has just gotten harder.
This, 100%. The window for parry is smaller now. Many new champions have most of their primary attacks unable to be parried, stun immune, parried reliably (E. Frost, Havok, Maw, Domino, Anni, etc). And now you are tweaking with one of the main ways to intercept quickly on fights that we still have 3 minute timers on with tougher nodes, more reversed controls, etc....
no doubt. I started late 2015 and have def felt changes in the AI, but nothing like this and the specials/dexes/counterpunched when hitting block bugs/tweeks. huge nerf to the actual player imo. Unless these are bugs, in which case I hope they announce incoming fixes in the Known Issues thread for 23.1.
I'm pretty sure this is due to an animation/frame rate change or an AI change. It came along with a ton of other bugs like Sentinel and X23 not allowing you to punish their special 1s anymore. Just wish they'd revert it back to how it was.
It is a staple in any players toolkit, it needs to be preserved or all stun immune content has just gotten harder.
The war on skill must stop.
I think most players agree with this. BUT, kabam keeps saying they did not change the AI response time. But it is extremely OBVIOUS for players that the AI is dashing in A LOT faster than before when we attack their block. AI also recovering faster from specials, AI also countering with specials while hitting block, etc etc etc.... this is like the definition of changing AI response time 😂 yet they still deny it
I'm pretty sure this is due to an animation/frame rate change or an AI change. It came along with a ton of other bugs like Sentinel and X23 not allowing you to punish their special 1s anymore. Just wish they'd revert it back to how it was.
It is a staple in any players toolkit, it needs to be preserved or all stun immune content has just gotten harder.
The war on skill must stop.
I think most players agree with this. BUT, kabam keeps saying they did not change the AI response time. But it is extremely OBVIOUS for players that the AI is dashing in A LOT faster than before when we attack their block. AI also recovering faster from specials, AI also countering with specials while hitting block, etc etc etc.... this is like the definition of changing AI response time 😂 yet they still deny it
And yet miike said in the post about the fix of punishing sentinels sp1, the ai was changed back to the way it was before to make it punishable. Hence the ai was changed.
If I am not mistaken, I believe the official explanation given by Kabam Miike, at least at one point, is that "Sentinel's sp1 was always difficult to punish", and that they had 'increased the window' for it to be punished so that players don't find it too difficult. Prof Hoff made a video of this reply. They have never acknowledged that they changed the AI as far as I'm aware, although pretty much the entire end game community knows that the sentinel issue was an AI/framerate change. Pretty sure the backdraft issue is similarly an AI/framerate change.
Comments
I just want to make sure we're all on the same page here. In my first post on this thread, I highlighted that there were two types of backdraft intercepts. I believe the first one was fixed and is working normally now since a fix that was pushed out a few weeks back. What we are concerned with is the second type of backdraft intercept - this is the one where you hit the opponent when they are holding block, followed by a back dash by the player, and a quick light attack to hit them when they dash in at us.
Just wanted to make sure that the game team is looking at the correct backdraft intercept technique, so we avoid a situation where the game team gets back and says they cannot re-create the bug.
Thanks so much!
This is honestly one of the biggest disappointments to land next to all the other bugs. Plus the fact you let it slide for another month and released a stun immune yellowjacket with glancing in your EQ.
Whats your counter to a stun immune fight?....
Backdraft intercepts and baiting specials....
Whats your counter to a stun immune fight with no backdrafting?
Tons of block damage taken and item use.
I feel sorry for the summoners trying to complete Variant 1 with all these issues since backdrafting was one of the main clearing techniques for the masochism chapters.
Also i'm using an iphone 7+. Worked just fine until your Annihilus update patch. I see you implying in threads that this is "performance" related perhaps...so lets talk performance and gaming....
Buy a PS4; 5-7 years shelf life of top end gaming
Buy a Gaming PC; 7-10 years of top end gaming
Buy a Gaming Phone(iPhone); 2 years top end gaming until performance issues....
Might want to reconsider bumping up those graphics and rendering artifacts to make your game look pretty while ignoring hardware standards in the gaming industry thats well established before mobile gaming.
If you need to dish out 1-2000 dollars every 2 years for a mobile game to be playable then perhaps we all need to rethink what we are investing in here.
Oh and FYI its happening on iphone XS max users phones too so i guess that performance issue is no longer debatable BUT I just decided to include some gaming knowledge regardless.
Kabam Miike said in a separate thread that you guys have people who tested the new AW nodes, which would presumably include the Aegis (intercept) node. Really curious - did nobody testing these nodes attempt to clear it with the backdraft intercept technique? Because if anyone testing had a modicum of skill they would have realised that the backdraft intercept technique would be the safest way to clear the node and would also have realised that it was broken at the time.
Until then I’ll continue to wear my tinfoil hat
Also yes it happens with every champ
It is a staple in any players toolkit, it needs to be preserved or all stun immune content has just gotten harder.
The war on skill must stop.