The Rakan Bug That Caused A Chronobreak In LEC

Summary

The transcript discusses a bug encountered during a competitive gaming match, particularly in a League of Legends-like scenario. The bug causes a player's champion, 'Raan', to become stuck in the game world after using one of their abilities, leading to confusion and speculation. Commentary reveals that the player may have been unable to use a secondary ability due to this glitch, which severely impacted their gameplay. The League officials are investigating the issue, with the game rolling back to an earlier point to resolve it, and a replay being reviewed to confirm the exact cause.

Takeaways

• 😀 The speaker speculates that there may have been a bug involving a champion's abilities during the game.
• 😀 The bug in question may have caused a champion (Raan) to get stuck in the game environment, possibly by interacting with a ward.
• 😀 The issue could have been related to a champion's E ability malfunctioning, where the ability's charges may not have been used correctly.
• 😀 The speaker suggests that the second E ability was used incorrectly, leading to the champion being unable to move, which affected their gameplay.
• 😀 The speaker mentions the 'Chrono break' mechanic, which rolled back the game to fix the issue and return it to its correct state.
• 😀 League officials are working on confirming the exact nature of the bug, though they have not yet provided full confirmation.
• 😀 The bug, once identified, triggered a pause in the game and was acknowledged as a common issue ('Double Dash game kick').
• 😀 The speaker observes that the champion's movement was halted during the game, which would typically have been an easy dodge with a Flash ability.
• 😀 A replay of the game is being reviewed to understand the exact bug, with a focus on the secondary E ability and the resulting bug interaction.
• 😀 There’s an indication that the bug may have caused an unexpected visual or movement glitch involving the champion and the ward placement, complicating their strategy.

Q & A

What bug is being discussed in the transcript?

The bug being discussed involves a situation where a player’s character, Raan, gets stuck while trying to use the 'E' ability. The issue is believed to be related to a potential bug where the 'E' ability uses both charges at once or gets bugged due to an interaction with the environment, such as getting stuck on a ward.

How was the issue detected during the gameplay?

The issue was noticed when the player, Alvaro, used the first 'E' ability, but the second charge didn't trigger as expected. He was seen pointing at the screen, signaling the absence of the second 'E' usage. This was followed by a pause in the game as officials investigated the bug.

What does the term 'Chrono break' refer to in this context?

'Chrono break' refers to a process where the game is rolled back to a specific point to correct errors, such as bugs that affect gameplay. It was offered to the team after the bug was detected, and the game was reverted to ensure fairness and accuracy.

What was the cause of the game pause?

The game was paused because of the bug affecting Raan's 'E' ability, which led to gameplay issues. Officials paused the game to investigate and confirm the issue before offering a solution like the Chrono break.

What does the player, Jack, speculate could have happened with the bug?

Jack speculates that the bug may have occurred because Raan’s 'E' ability bugged out, possibly due to pressing the 'E' ability twice in quick succession, or being stuck in a ward or object in the environment, preventing the champion from moving.

How did Alvaro react when his champion got stuck?

Alvaro appeared confused and frustrated when his champion got stuck. He tried to use the 'E' ability but couldn't move the character, despite trying to flash away from an incoming Ashe arrow. He was seen pointing at the screen, implying that the issue was on the game’s end.

What did the replay reveal about the bug?

The replay showed that after using the first 'E', Raan's character got stuck on a wall, possibly due to an interaction with a ward or the terrain. This prevented him from moving and using his abilities as intended, which contributed to the issue.

What does the term 'Double Dash game kick' refer to in the transcript?

The term 'Double Dash game kick' is mentioned briefly as part of the bug incident, but it is not fully explained in the transcript. It likely refers to a specific error or event in the game that led to the bug occurring.

Why was there confusion about the bug's cause?

There was confusion about the bug's cause because no one could confirm exactly what triggered it. Different theories were discussed, such as a possible issue with the 'E' ability or the interaction with a ward or other environmental objects, but the official confirmation was still pending at the time of the discussion.

What actions did the officials take to address the issue?

The officials investigated the situation and confirmed the bug was related to Raan’s ability getting stuck. They then offered a Chrono break to roll the game back and restore it to the correct state, ensuring a fair resolution to the issue.