Why impossible leaderboard scores exist
Some impossible-looking Rayman Legends leaderboard entries are not ordinary external cheat-tool values. Several game glitches can change the submitted time, distance or even the type of data the leaderboard believes it is receiving.
The result can be tiny times such as 0.00 seconds, absurd multi-kilometre distances or enormous corrupted values that still rank in first place.
1. Pause glitch: subtracting frames from a time
On relevant timed challenges, manually pausing the game, selecting Continue and resuming can cause the final submitted time to lose one frame. Repeating the process repeatedly can shave multiple frames from an otherwise normal run.
A simple double-tap of pause is not enough; the menu has to be resumed through Continue for the effect to occur.
2. Pit Distance void fall: effectively unlimited distance
A broken Murfy-related state can let the character reach areas above the normal ceiling and then fall beneath the stage geometry. Once out of bounds, the game can continue treating downward movement as challenge distance.
Because the fall can continue for a very long time, the submitted distance can grow into values that are impossible through normal forward movement.
3. Pit Speed exploit: finishing before the timer properly begins
A related out-of-bounds setup can reach the required Pit Speed distance from an invalid area before the challenge timer has properly registered the run. The result can be near-zero or literal 0.00-second leaderboard entries.
The Double Murfy limitation
The two pit exploits depend on preserving a Murfy-glitch state through a compatible Extreme Challenge. If both Extreme slots rotate to Murfy challenges at the same time, entering them breaks the required state. This temporarily removes the setup route for those pit exploits until the rotation changes.
4. Training Room / Puma glitch: corrupting the leaderboard metric
The most chaotic method involves the hidden developer training room used to configure challenge parameters. Through platform-specific transition or lobby glitches, players can carry parts of that configuration state into an online challenge.
The active challenge metric can then become mismatched. For example, a board expecting a fastest-time value can receive data produced as a distance value instead.
That corrupted submission may display as an enormous time or another nonsensical number. Internally, however, the server can interpret the malformed value as better than legitimate positive times, leaving the entry at the top of the leaderboard.
Four common explanations
| Pause glitch | Removes individual frames from a submitted time. |
|---|---|
| Pit Distance void fall | Uses an out-of-bounds fall to generate extreme distance values. |
| Pit Speed timer exploit | Triggers the goal before the timer properly records the run. |
| Training Room / Puma glitch | Corrupts the expected leaderboard metric and creates enormous malformed values. |