An independent magazine about speedrunning and finishing games against the clock. It does not run leaderboards or competitions and is not connected with the former site on this domain.

Updates

Updates: when the game shifts under a runner's feet

For a regular player, an update means bug fixes and perhaps some new content. For a runner, it can turn everything upside down: close a shortcut the whole route relied on or, on the contrary, open a new one. That's why communities keep a close eye on game versions and often split categories so that results on different versions don't get mixed up. We cover this in general terms, without tying it to specific games or dates, so you understand the logic and don't get lost when it affects your game.

A new version of a game doesn't devalue past runs. It simply opens another page where you'll have to learn everything all over again.

— Editor's view

Decisions about splitting categories are made by the communities of individual games. We explain why it happens, but we don't track changes in particular games.

What an update can change in a run

Six typical consequences of a new version for runners.

A fixed glitch

The developers patch a bug that a fast route depended on. The route has to be rebuilt, and times on the new version usually get longer.

Glossary

Different loading speed

Even a small difference in loading times affects the result. That's exactly why many communities time runs without loads.

Glossary

A redesigned level

A moved wall or a new enemy can force you to find another way through a familiar area.

Guides

New content

Extra quests and items change what counts as "everything" in a 100% category, and the rules have to be clarified.

FAQ

Changed controls

A new layout or sensitivity setting means getting used all over again to movements drilled through hundreds of repeats.

Tips

A separate category

If the difference between versions is too big, the community may start a separate leaderboard so that similar runs can be compared fairly.

Reviews

How to keep track of changes

  1. Find out which version the category requires

    Check the rules to see which game version results are accepted on. Sometimes several are allowed, sometimes only one.

  2. Don't rush to update

    If your category is run on an older version, find out whether you can keep it. The process is usually described in the rules or in community notes.

  3. Read the patch notes

    When a new version comes out, the developers list the changes. Mark the ones that affect your route.

  4. Test your route in practice

    Play the key segments on the new version and see whether your usual techniques still work.

  5. State the version with your run

    When submitting an attempt, always name the game version. This helps moderators place the result in the right category.

  • Guides

    Step-by-step guides: how to split a route, record a run and make sense of category rules. The article catalogue lives here too.

  • Tips

    Segment practice, calm resets, practice modes, warming up and taking breaks: everything that helps you improve without burning out.

  • Reviews

    Our checklist: how to tell whether a game suits speedrunning, with no scores and no best-of lists.

  • Glossary

    A runner's dictionary: any%, glitchless, split, personal best, skip, reset, in-game time, real time and more.

What this article is based on

  • Category rules of speedrunning communities (in general terms)
  • Roniksclub editorial material

We write about speedrunning in general terms. Category rules, timing methods and video requirements are set by each game's community and change over time, so before any run always check the current rules for the category you plan to run.