Autosplitter+games+github+2021 May 2026

To understand the significance of 2021, one must first understand the tool at the heart of the revolution: the autosplitter.

For years, speedrunners relied on manual timing. A runner would start a timer, play the game, and frantically hit a split button on their keyboard to mark the transition between levels or bosses. This introduced human error; a runner might lose a second simply by fumbling the split key, or worse, forget to split entirely, invalidating a segment of their run.

An autosplitter is a script, usually written in the ASL (Auto-Split Language) or ASLX format, that interacts directly with the game’s memory. It acts as a robotic referee. It reads the game's internal code—looking for specific values like "level ID changed" or "boss health = 0"—and automatically pauses and resumes the timer (typically in LiveSplit) with frame-perfect precision.

By 2021, autosplitters had evolved from simple triggers into complex, logic-driven monitors that could calculate load times, remove lag, and verify game states.

The connection between autosplitters and GitHub was not new in 2021, but it reached a tipping point. Previously, these scripts were often scattered across obscure forums, Discord channels, or uploaded as raw text files to speedrun.com leaderboards. There was no version control, no easy way to update scripts when games patched, and no collaborative environment. autosplitter+games+github+2021

GitHub changed the workflow entirely. By 2021, the vast majority of reputable autosplitters were hosted on GitHub repositories. This shift brought three critical elements to the speedrunning community:

Despite console limitations, the community used a custom autosplitter via a capture card and screen analysis. The GitHub repo for "MK8DX" autosplitter became a hub for discussing frame rules and lap timing, though it relied more on OCR than memory reading due to Switch encryption.

The year 2021 was unique for several reasons. The COVID-19 pandemic had shifted many speedrunning marathons (like GDQ) to online-only formats, increasing the reliance on automated verification. Furthermore, GitHub’s native integration with LiveSplit’s update system made it the perfect host for these scripts.

In 2021, the search query "autosplitter+games+github+2021" spiked as new runners sought to set up their first runs and veteran runners looked for updates following major game patches. To understand the significance of 2021, one must

If the repo was last updated in June 2021, but the game received a patch in 2023, the memory addresses will likely be wrong. Look for Pattern Scanning vs Static Addresses.

// Typical 2021 Script for a Unity Game
async function update() 
  var gameTime = current.gameTime();
  if (gameTime > 0 && vars.startFlag == false) 
    vars.startFlag = true;
    start(); // Start timer
var level = memory.read_bytes("[MonoBehavior:LevelManager] + 0x10", 4);
if (level == 5 && vars.lastLevel != 5) 
split(); // Entered Level 5
vars.lastLevel = level;

Example from a 2021 GitHub Gist.

What changed in 2021? Support for 64-bit pointers became mandatory as games moved away from 32-bit executables. Scripts from 2019 often crashed on 2021 hardware.

For modern researchers looking back, here is how runners in 2021 navigated the ecosystem:

If you watched a speedrun of Celeste, Hades, or Minecraft in 2021, you likely saw a timer ticking down in the corner, splitting automatically at the end of each level. That seamless magic didn’t happen by accident. Behind the scenes, a quiet revolution was taking place on GitHub, fueled by a wave of community-driven autosplitter development.