@Kiki and he would've been low hp meaning g2 are in a good position to win the fight and get drake. the clean play bb did was mindcontrol mad into letting rakan die to akshan ult because for some reason they think bb could tp to their base and ult from there? the chronobreak completely fucked g2
@@grandmastercultistofben "the clean play bb did was mindcontrol mad into letting rakan die to akshan ult because for some reason they think bb could tp to their base and ult from there?" Jesus Christ, cope harder.
That said, I'm disagreeing that Rakan should die due to a visual bug, but am agreeing that the chronobreak could have been done better, as in just have it after the actual fight to reverse the Akshan ult and not the fight itself. They do need to work on how far they can go, to just reverse the bug, not the entire fight.
@@Kamikaz3Badger Regardless of the visual bug, it's quite obvious where akshan was firing from. Additionally, Rakan had no health, no flash, and no ult at 200 health. He was pretty much entirely out of the fight regardless. The VOD shows the askhan ult cutting to an impossible angle, so it's just poor coordination.
@@doobyempires228 bad coordination? They literally responded to the visual they saw at the time as any pro would do. It's not pretty obvious when something visually tells you otherwise. Even then you would still want to eliminate any impact of a bug. It ultimately doesn't matter, G2 lost the series anyway and the chronobreak didn't impact much unless you got that premium copium drip.
@@Kamikaz3Badger Uh, if you saw an impossible angle, by all means you should dismiss it. I think the bug did not affect Carzzy's ability to block the ult. Either way, Riot should put some budget on redoing League Of Legends.
Did you not see the visual bug? Like it's so clear I'm worried if the people commenting are actually blind or just trolls. There was a definite visual bug that occurred that caused a death and bringing Hylissang and FNC tactics into this conversation just makes you look stupid. The problem was NOT that there should have been a chronobreak, the problem was that the chronobreak went before the fight started and not just before the bug.
@@Kamikaz3Badger There was a visual bug, but the mechanics of the ult and the indicator from which way it will be shot was clearly visible a second later. It's bs because if this is allowed, next time they might as well pause when the screen flickers for 0.2 seconds.
@@cleveranonym74 You can't honestly say that the bug didn't have a large impact on decision making at the time though. It indicated the ult was coming from literally the opposite direction, so they reacted accordingly, then it switched without enough time for correction. The issue is that the chronobreak reversed the fight, not that a chronobreak was not necessary. It was not 0.2 seconds so that example doesn't make sense, but let's say there is a screen flicker or keyboard issue for less than a second but it was during a smite fight at world finals, you gonna say nah that's fine player at fault for not predicting the screen flicker and acting accordingly? They DO pause when they have weird issues like this, for good reason. I'm a G2 fan and don't even want MAD to go to MSI, but we have to put our bias aside when looking at these things.
@@joaoreis3290 Yeah that I agree with, they REALLY should have just did the chronobreak up until the Akshan ult started. It might not have changed the entire game since G2 was already behind, but it sure would have changed that fight and dragon situation.
Unfortunately they were losing before the bug and probably would have lost without it since they were still behind. I'd love to think one issue would have made the difference but that's huffing copium at lethal levels
People really out here saying the game 5 comments that a visual bug in a losing game is the reason for the entire series to happen. do yall think before talking? and dont call me mad fanboy or whatever, idc, im watching these in after the fact anyways and am not attached to either teams
I never spend time on comment but... Do you agree that there is someting more than that in this weird on this game? I mean, G2 is behind and suddenly a beautiful outplay from G2 on drake, make them ,honestly, from behind to in front of this game, MAD play bad on one drake occasion and suddenly there is chrono from nothing. Then magically MAD there is nothing wrong with Akshan (I guess) and sudenly G2 lose, what the fuck happened the first pause? I'm pretty sure MAD Lions are weird on this one, wtf is going on?
What are even talking about? MAD were offered a chronobreak because there was a visual bug, they talk about it at 50:50. Do you sincerely believe that somehow there is some conspiracy to have G2 lose the game?
"There is chrono from nothing" - did you even watch the video or what, there was a clear visual bug which hindered Carzzy from blocking the Akshan ult for Hyli, 51:08. Hyli would not have died there if there was no bug. Clueless.
Even if there was no chrono, which was obviously needed because of the bug, g2 would have gotten the drake and a kill, in what world does that put them ahead when they were 7k down at the start of the fight...
How the fuck do casters know so little about the game 😮 of course akshan does not revive from assists, that would be beyond broken, would instantly make him the best team fight champion
He does revive from assists though, if he's still alive when the takedown happens, he doesn't need to be the one killing the scoundrel, he just needs to hit him once.
we need to know though : How are you doing Deficio ?
Broken Blade Ult on Hyli was sooo clean!!! Sucks that there was a visual bug :(
Carzzy would've blocked it if it weren't for the visual bug, no idea what's clean here.
@Kiki and he would've been low hp meaning g2 are in a good position to win the fight and get drake. the clean play bb did was mindcontrol mad into letting rakan die to akshan ult because for some reason they think bb could tp to their base and ult from there?
the chronobreak completely fucked g2
@@grandmastercultistofben 110% agree, that and they knew exactly how/where to stop g2 from getting to the drag.
@@grandmastercultistofben "the clean play bb did was mindcontrol mad into letting rakan die to akshan ult because for some reason they think bb could tp to their base and ult from there?" Jesus Christ, cope harder.
@@Kiki-ps8lumight be his phone screen at that exact moment. "G2 will 3-0 if that was not a bug." - G2 Fans
1:02:42 game continue
2nd continue not even worth it lol
Was the second pause BB not knowing how Akshan works?
@@Alex-ud6zr nah last ditch effort of g2 to get their momentum back 5 sec from game end
Who’s gonna int? Carrzy or Brokenblade. Take your pick. It’s one or the other.
51.10 there was a visiual bug.
BB you are the best 👍🏻
That chronobreak wasn't cool. Xayah didn't block the akshan ult. That's all.
Tell me you didn't watch the VOD without telling you didn't watch it. It's a clear bug, and there are rules when that happens. That's all.
That said, I'm disagreeing that Rakan should die due to a visual bug, but am agreeing that the chronobreak could have been done better, as in just have it after the actual fight to reverse the Akshan ult and not the fight itself. They do need to work on how far they can go, to just reverse the bug, not the entire fight.
@@Kamikaz3Badger Regardless of the visual bug, it's quite obvious where akshan was firing from. Additionally, Rakan had no health, no flash, and no ult at 200 health. He was pretty much entirely out of the fight regardless. The VOD shows the askhan ult cutting to an impossible angle, so it's just poor coordination.
@@doobyempires228 bad coordination? They literally responded to the visual they saw at the time as any pro would do. It's not pretty obvious when something visually tells you otherwise. Even then you would still want to eliminate any impact of a bug. It ultimately doesn't matter, G2 lost the series anyway and the chronobreak didn't impact much unless you got that premium copium drip.
@@Kamikaz3Badger Uh, if you saw an impossible angle, by all means you should dismiss it. I think the bug did not affect Carzzy's ability to block the ult.
Either way, Riot should put some budget on redoing League Of Legends.
This chronobreak was the biggest fucking bs I've ever seen, Hylissang brought his pause tactics from Fnatic all the way to MAD.
Did you not see the visual bug? Like it's so clear I'm worried if the people commenting are actually blind or just trolls. There was a definite visual bug that occurred that caused a death and bringing Hylissang and FNC tactics into this conversation just makes you look stupid. The problem was NOT that there should have been a chronobreak, the problem was that the chronobreak went before the fight started and not just before the bug.
@@Kamikaz3Badger There was a visual bug, but the mechanics of the ult and the indicator from which way it will be shot was clearly visible a second later. It's bs because if this is allowed, next time they might as well pause when the screen flickers for 0.2 seconds.
@@cleveranonym74 You can't honestly say that the bug didn't have a large impact on decision making at the time though. It indicated the ult was coming from literally the opposite direction, so they reacted accordingly, then it switched without enough time for correction. The issue is that the chronobreak reversed the fight, not that a chronobreak was not necessary. It was not 0.2 seconds so that example doesn't make sense, but let's say there is a screen flicker or keyboard issue for less than a second but it was during a smite fight at world finals, you gonna say nah that's fine player at fault for not predicting the screen flicker and acting accordingly? They DO pause when they have weird issues like this, for good reason. I'm a G2 fan and don't even want MAD to go to MSI, but we have to put our bias aside when looking at these things.
@@Kamikaz3BadgerIts a stupid reset. G2 already won the fight, with or not hyli death.
@@joaoreis3290 Yeah that I agree with, they REALLY should have just did the chronobreak up until the Akshan ult started. It might not have changed the entire game since G2 was already behind, but it sure would have changed that fight and dragon situation.
First
It's a shame seeing G2 loosing like this... Due to a fucking bug.
Unfortunately they were losing before the bug and probably would have lost without it since they were still behind. I'd love to think one issue would have made the difference but that's huffing copium at lethal levels
ahahaha sour
People really out here saying the game 5 comments that a visual bug in a losing game is the reason for the entire series to happen. do yall think before talking?
and dont call me mad fanboy or whatever, idc, im watching these in after the fact anyways and am not attached to either teams
I never spend time on comment but...
Do you agree that there is someting more than that in this weird on this game?
I mean, G2 is behind and suddenly a beautiful outplay from G2 on drake, make them ,honestly, from behind to in front of this game, MAD play bad on one drake occasion and suddenly there is chrono from nothing. Then magically MAD there is nothing wrong with Akshan (I guess) and sudenly G2 lose, what the fuck happened the first pause?
I'm pretty sure MAD Lions are weird on this one, wtf is going on?
What are even talking about? MAD were offered a chronobreak because there was a visual bug, they talk about it at 50:50.
Do you sincerely believe that somehow there is some conspiracy to have G2 lose the game?
"There is chrono from nothing" - did you even watch the video or what, there was a clear visual bug which hindered Carzzy from blocking the Akshan ult for Hyli, 51:08. Hyli would not have died there if there was no bug. Clueless.
G2 fan lmao
Even if there was no chrono, which was obviously needed because of the bug, g2 would have gotten the drake and a kill, in what world does that put them ahead when they were 7k down at the start of the fight...
Dont be silly
How the fuck do casters know so little about the game 😮 of course akshan does not revive from assists, that would be beyond broken, would instantly make him the best team fight champion
He does revive from assists though, if he's still alive when the takedown happens, he doesn't need to be the one killing the scoundrel, he just needs to hit him once.
You smart lol 🤓
In ARAM Akshan is the most annoying champ to deal with. 50seconds timer for enemy to be back, meanwhile there is Akshan reviving all four of them.
Akshan revives on assist, as long as HE IS ALIVE as well
how the fuck do you so little about the game?