asol bug clg vs fly quest.
100% a bug. asol animation even makes it look like he wanted to get out of the flight animation. i wish i had a the clip but if u look at it he was locked into the travel. 
[cass-cry]
22 Comments
I find it hard to believe that this bug didn't occur AT ALL prior to this game. I find it hard to believe that someone like Huhi (a guy who is literally only known for playing this character) didn't know of the bug potentially occurring. The fact that CLG is probably going to win yet another series because of an ASOL bug somewhat infuriates me, and leaves kinda a different taste on the character where teams will either be forced to ban it or risk having clg abuse a bug to turn the series around.
My bigger issue here is how CLG is given a chronobreak and a lot of time/options of what to do. meanwhile when FLY's players have a bug and they just tell them what they need to know and say "deal with it". I get it isnt the same as causing a death but it just feels cheap when they gave the chrono to CLG but pretty much nothing to Flyquest
I gotta agree. This bug could have potentially happened previously but since it didn't negatively affect clg (or even help them) they are not going to stop the game. The moment it does then it's a big deal.
The questions should be: is this a game breaking. If so, disable the champ and remake the game. If not then just deal with it, you picked the champ, and as a pro should know the potential consequences.
That's a huge turning point in the game, and clg will never been see as deserving any results of the gauntlet this year.
Honestly is the more interesting part. If huhi did realize the bug happened, why did it take his death for the pause, if he's smashing the button and it's not working then the pause should have been immediately.
There is no way this hasn't happened before, and if you know of an existing bug, then pick a champ with the knowledge that you can call foul and get back a bad play, that's an exploit.
I'm just a silver and it looked like he was DCing...just the way he kept going perfectly straight while the rest of the team is retreating. Just looked odd.
I love how all the salty Flyquest fans in this thread know exactly what all the "common" Asol bugs are, and who does and doesn't know about these bugs.
_Huhi: "Using Asol's E will lock me in the animation and I have no way to cancel it. This is a groundbreaking exploit that will let me win any game". _ Some people are just too dense if they actually believe that.
I also love how they cry for a remake, saying that is the fairest solution, even though the chronobreak was exactly invented for these type of occasions. The death occured due to a bug. They rewind 5 seconds, right up to when the bug occured. Problem solved. What is the problem here? But yes, random players know better than Riot's official referees.
CLG was winning the match when the bug occured, and they crushed FLY during the other 2 games they won. FLY shouldn't even have been in the gauntlet to begin with, they did decent in spring, but were garbage in summer.
I think this just calls for a Worldbreaker Aurelion Sol skin even more.
I don´t even question if it was a bug or not but I got a different problem with this.... I don´t like how you can take advantage of ASOL bugs like this. If you are cronobreakking the game just because of ASOL you could actually get a slight mental advamtage. Also you could just not report the bug if it helps your team. You could just pick ASOL just to hope there´s a bug so you can dodge out of stupid stuff. I find this is not actually fair Just my opinion though
"teams could find out the bugs and use them in LCS"
Wtf are you stupid or were you just not watching the game?
CLG had 0 reason to WANT to chronobreak, they just gained a massive lead and were about to set up for baron. They got a reason when the bug occured and huhi died because of it. It only went back to what, like a minute before it happened? Nothing changed.
Chronobreaking there was totally nonsense. This isn't a rare bug.
I feel like both teams should have to agree to chronobreak rather than full remake. IE; CLG can request chronobreak and FLY could say no - do a remake instead.