HUGE BUG JUST HAPPENED at MSI!

This Bug could have absolutely changed the outcome of the game.
Big shutdown, if GAM played the follow-up fight better, we could have had a different winner.

I’m part of the official League Partner Program with Riot Games. You can read about the program here:

Chapters:
0:00 Bug in FNC vs GAM
0:33 Reproducing the bug
0:48 Bug explanation
0:53 Rakan having this bug...

[ShadwWarrr]

Good to see Riot is still following the quality standards

[KingValorox]

Now that they can see how buggy their game is, they will now buff aatrox in response.

[Mache.]

Remember when League launched and until like 10 years ago when if you were already rooted/stunned and you got hit with another hard CC, you could move your champ for like 0.1 seconds? I'm glad to see they're bringing back all the old spaghetti.

[nicklasdamsgaard]

tbh at first i though it was an issue with Rumble ult not doing damage because he was too far away

[Bellicosy]

"Has remained unfixed for years." Why am I not surprised.

[rammuscurtindoochurras]

Just so you guys know, Profane Hydra is currently not giving any lethality stats, despite it saying it gives you 18 lethality, happening on live servers

[bomgoa]

One year ago, there was a bug in the GAM vs TES team fight that caused TES to leave MSI. Now we have encountered another one, but luckily it is not too serious and it didn't make FNC go home 🤣🤣

[nvpg]

Is small indie company, can't expect everything to be pristine and polished.

[wakaran]

"the bugs he posts are not reproducable in a real game srtting"

[zonkodraw]

It's mind boggling that someone has pointed out the bug including the coding necessary to fix yet Riot simply didn't fixed it.

What's even more mind boggling is that they fixed Rakan but didn't bother to check Ahri.

Smol indiana company.

[StarClay]

I saw this live and was so confused how literally noone reacted to it. I brushed it off as a spectator bug yet it still didn't make sense.

[pjemonto]

I mean... For past 2 years I still happen to die from Rengar the moment I use Zhonya.
I click Zhonya the moment Rengar jumps, +I die + Zhonya is on cooldown.
I am not surprised seeing those unfixed bugs anymore...

[Seanana_]

PSA reminder that riot hands out a list of known bugs that are okay to abuse and which are not okay to abuse to pros! This is probably one of them

[Wildcat]

The irony is that this is actually on their new CC system that’s way better overall. I guess when you’re building on spaghetti the end result will always be spaghetti

[aspirion]

Dont worry Vanguard has a better Code =)

[JimnyThePython]

I was surprised they didn't pause after I saw this happen. Made the game much harder for FNC.

[EdwardRichtofen_]

It can also happen with Skarner, sometimes when you "pin" an enemy to a wall, I'm not sure how it's exactly reproduced but i'm guessing the "pushing" cc timer overwrites the "stunned" timer, letting people do actions out of Skarners E wall stun whilst they're stunned, it's cost me a few games now since it makes you unable to follow up with R sometimes.

My guess is it's that or there's a window between the pushing cc and stun cc, where if you channel an ability you can get it off whilst stunned

[gpfenjoyer]

it happened to me yesterday when i somehow used fiora W while being bubbled. Good to see riot working hard on fixing such bugs!

[danielclv]

"we realize CC chains are broken, so adopting the mechanics of combo break in Arena, while also reducing the tenacity stat, all champions will have 0.2seconds of freedom after every CC in the game" RITO probably so they don't have to fix the spaghetti.

[digammaf]

It is very bad design to switch the flag back to true without considering the fact that another cc might be going on. The best thing is, for Sion, they probably fixed it the worst imaginable way, like looking for one kind of cc specifically. Meaning that if they add a new kind of cc in the game, the bug will be right back. At this point, the devs deserve to struggle with that code. They don't care if it will work in the future, they just want it to work now, except that 'now' has been going on for more than 10 years now.