ARAM DASH BUG???

Thank you for looking into it! It's definitely not a game breaking bug, but its not fun to play against some champs. Can't wait to see the live fixes [slayer-pantheon-thumbs]

Hey, since disabling the entire game mode would be less than ideal, why not temp disable the worst offending champions for ARAM only? Such as Lee Sin/Thresh/Warwick to name a few.

[{quoted}](name=Riot Stephiroth,realm=NA,application-id=LqLKtMpN,discussion-id=UlYv4mX5,comment-id=000100000000,timestamp=2018-07-25T19:03:03.424+0000)

This is a long discussion we had but there's a few points specifically that stopped us from disabling Snowball.

• The bug actually isn't 100% reproduction rate. It is pretty frequent, between 60-70% of the time, but it is not actually 100%.
• The gameplay pattern impact for players who are hit by Snowball actually isn't changed much from seeing the bugged dash or not. If you see the Snowball hit and mark a minion or allied player, most players know there's a high potential for the enemy to dash. And you know where they're going to end up. It's obviously REALLY shitty, but after some adjustment, it could be played around since there's not a functionality change.
• The champions bug is much worse than what Snowball does (given the above context), but the current champion count for how many exhibit the bug is about 40. Not all players own enough Champions for us to disable 40 of them and still be able to play the mode :(

We did also highly consider disabling ARAM altogether, but felt that was an overall worse experience.

I understand the frustrations of everyone playing ARAM right now, because ARAM is the mode I play the most. We are working on a fix and hoping to get it out to Live ASAP.

I know this won't make you feel better about the situation, but I hope it gives you some insight into how we approached the problem.

I would disagree with playing around only be slightly different. It's immensely different. I pride myself in being able to turn around bad snowball dives. The ability to see someone dive is a HUGE difference. It allows me to save spells and mana and potentially line up my character position to help in the need of a threatened dive. When I can't see them till they're already on top of me or someone else, I pretty much have no choice but to waste the cd every time, on top of that they will always get the jump. Which for assassins is really all they need. Not to mention the team loses all their reaction time they would have spent while that person was traveling in. For a team fight where you can't base heal that's pretty big distinction if its instantly 5v4 all of a sudden.

[{quoted}](name=Riot Stephiroth,realm=NA,application-id=LqLKtMpN,discussion-id=UlYv4mX5,comment-id=000100020001,timestamp=2018-07-26T23:32:56.165+0000)

Hey again :3

I can't go into too much nitty-gritty, but it turns out the issue was related to some network code changes we made that had an odd interaction with the Base Gate we added to ARAM a couple of patches ago. The movement restriction packet for a hero was supposed to only be sent to the clients that can see the hero. However, one of the recent changes somehow sent the packet to all the clients. Later in the game, the clear restriction packet was correctly sent to only the clients that can see the hero leave base. So, anytime an enemy hero (who did not see the champion leave base) saw the champion attempt to do a moveblock, the client didn't properly know where to position it due to this missing information.

Hope this is enough to satiate your curiosity.

[slayer-jinx-catface]

It is, thank you very much! :D

Any info on the bots bug causing an enemy bot to afk even no one on the human side has?

Just ran a match and no bugs! Many many thanks. I work in QA so I understand how hard it can be to quash these things and I much appreciate the time and effort put into making this bug go away. Hope you have a great day and good matches!