Uploaded December 2023 | Updated September 2026, 2 weeks ago
This bug has existed as far back as 1.9, and probably even earlier. However, it now manifests differently in 2.2: you are actually given control of the character, unlike in 2.1 where you watch them manually crash, and 1.9 where you've already died by the time you load into the level.
I don't know how to reproduce this on desktop, but on mobile, if you hold down your finger on one main level, then touch the arrow, hold down another finger on another level, and then release at the exact same frame, you get into this glitched state.
The music of one level is paired with the level data of the other, which stops rendering after a given point (but collision and such still works). Upon crashing, trying to open the pause menu or exit to the main menu crashes the game.
This bug has existed as far back as 1.9, and probably even earlier. However, it now manifests differently in 2.2: you are actually given control of the character, unlike in 2.1 where you watch them manually crash, and 1.9 where you've already died by the time you load into the level.
I don't know how to reproduce this on desktop, but on mobile, if you hold down your finger on one main level, then touch the arrow, hold down another finger on another level, and then release at the exact same frame, you get into this glitched state.
The music of one level is paired with the level data of the other, which stops rendering after a given point (but collision and such still works). Upon crashing, trying to open the pause menu or exit to the main menu crashes the game.
