Speedrunners Build | 18052020 _best_
On May 18, 2020, developers working with the Build Engine —the technology behind classic titles like Duke Nukem 3D Shadow Warrior —were actively refining modern source ports and tools.
Based on the development activity of that era (specifically for and related Speedrunner-friendly
tools), here is a feature proposal designed to bridge the gap between "Build Engine" legacy mechanics and modern speedrunning needs. Feature Proposal: "Frame-Perfect Input Buffer & Visualizer"
This feature aims to eliminate the "randomness" of 90s engine physics by giving runners precise control and feedback during high-speed movement. Ghost-Input Buffer
: Speedrunners often rely on "sub-frame" timing for movement like "wall-runs" or "crouch-jumps." This feature would allow runners to "buffer" an input within a 2-3 frame window before a physical collision or sector change, ensuring the engine registers the maximum possible velocity boost without frame-perfect manual precision. Live Momentum Gauge
: A HUD element that visualizes the current X/Y/Z momentum vectors. In the Build Engine, horizontal speed is famously gained by running into corners at specific angles (strafe-running). This gauge would turn green when the runner hits the optimal "Build-Slide" angle. Sector Transition Warning
: Build maps are made of "sectors." Passing through certain sector lines can occasionally "snag" a player's hitbox. This feature would highlight sector boundaries in the runner's field of view that are prone to "clipping" or "snagging" based on current velocity. Implementation for Build Engine Devs To implement this in a port like , developers would focus on: Engine Latency Reduction : Updating the
to polling at a higher frequency than the internal game tick (typically 30Hz or 120Hz depending on the port). Physics Decoupling
: Separating the movement physics from the frame rate to ensure that players with higher refresh rates don't gain an unfair advantage (or disadvantage) during "glitched" jumps. technical breakdown
of how to code a basic speed-meter for a Build Engine source port?
SpeedRunners Build 18052020: A Defining Update for the Competitive Scene
The SpeedRunners Build 18052020, released on May 18, 2020, stands as one of the most critical milestones in the history of the high-octane multiplayer platformer developed by DoubleDutch Games . While the game originally launched years prior, this specific version became a cornerstone for the dedicated community due to its sweeping mechanical refinements and stability improvements. Key Features and Mechanical Overhauls speedrunners build 18052020
The Build 18052020 wasn't just a routine patch; it addressed core gameplay loops that defined the competitive meta. According to technical logs and community archives, this update introduced:
Refined Physics Engine: Adjusted momentum preservation to ensure that veteran players could more reliably execute advanced maneuvers like wall-jump chains without unexpected friction loss.
Enhanced Multiplayer Connectivity: A significant overhaul of the netcode meant reduced latency in four-player matches, which is essential for a game where millisecond reactions decide the winner.
Graphical and UI Polish: Improved overall visual clarity and updated the user interface to better display character status and power-up availability during high-speed chases.
Bug Fixes: Addressed several long-standing community-reported glitches, particularly those related to the grappling hook's interaction with specific map assets. Legacy in the Speedrunning Community
For the speedrunning elite, Build 18052020 became a "gold standard" for stability. Some players specifically seek out this version to bypass later changes that altered the behavior of experimental features.
Procedural Elements: The build refined how the game handled procedurally generated segments, offering a more balanced yet unpredictable challenge.
Experimental Tools: It allowed for deep exploration of "lost" content and glitch-hunting strategies that are still discussed in forums today. How to Access and Play
While newer versions of the game have since been released—including recent updates in 2026—Build 18052020 remains popular for those using specific "Online-Fix" patches to maintain legacy compatibility for private lobbies.
Platform Support: The build is compatible with Windows XP and up, requiring only 1GB of RAM and a 1GHz processor, making it accessible even on older hardware.
Steam Availability: You can find the latest version and official DLC, such as the Youtuber character packs, on the SpeedRunners Steam Store Page . The Future of the Franchise Save 80% on SpeedRunners on Steam On May 18, 2020, developers working with the
SpeedRunners build 18052020" specifically refers to an update released for the competitive platformer SpeedRunners
on May 18, 2020. This build was part of a larger trend in 2020 where the game saw a resurgence in competitive play, despite many players feeling the developers had largely moved on from major content additions. The Significance of the 18052020 Build During this period in May 2020, SpeedRunners
focused on maintaining its niche as a premier "esport" style platformer. Refining the Meta
: The updates around this time often addressed minor physics bugs and server stability to ensure the integrity of ranked matches. Community Spotlight : Around mid-May 2020, community-driven events, such as the SpeedRunners Guild
seasons, were a primary focus, offering physical prizes for top-tier competitive play. Technical Stability
: While major gameplay overhauls were rare by 2020, builds like this were essential for compatibility, eventually leading to later updates that transitioned the game from XNA to FNA on Windows to ensure it remained "future-proof". SpeedRunners in the 2020 Speedrunning Landscape
The year 2020 was pivotal for speedrunning as a whole. While DoubleDutch Games (the developers of SpeedRunners
) were maintaining their title, the broader speedrunning community was experiencing a massive boom. Charity Impact : Events like Summer Games Done Quick (SGDQ) 2020
moved to an all-online format due to the pandemic, proving that the digital speedrunning community could thrive and raise millions for charity remotely. Controversy and Growth
: 2020 also saw high-profile speedrunning incidents, such as the Dream Minecraft cheating scandal
, which sparked intense debate over the use of "modified versions" of games and the role of rigorous verification in record-setting. Essay Conclusion: The Legacy of a "Dead" Game Adoption mechanics
By the time the 18052020 build arrived, some community members joked that the game was "abandoned" due to a lack of new characters or maps. However, the continued existence of these maintenance builds and the active competitive ladder proved that the game’s core mechanics—the
grappling hooks, power-ups, and screen-shrinking elimination
—were robust enough to sustain a community for years without flashy new features.
The 18052020 build represents a moment where a classic indie title transitioned from its "active development" phase into a "legacy competitive" phase, kept alive by a dedicated player base that valued precision over novelty. specific technical changes within that 2020 build, or are you interested in how to revert to older versions for speedrunning purposes?
3. The "Frame 180" Glitch
The most famous exploit in the build occurs exactly 180 frames (3 seconds at 60 FPS) after a slide-jump. If a player inputs a grapple command on the exact frame the slide animation ends, the game fails to reset the vertical velocity. This allows runners to "fly" horizontally for the rest of the level without touching the ground.
Why the Obsession?
For the average player, a missing build isn't a big deal. For speedrunners, it’s archaeology.
Build 18052020 represents the platonic ideal of a broken game. It exists in a quantum state—simultaneously the most optimal route ever theorized and a complete myth. It asks a dangerous question: If you found a build that let you beat the game in 47 seconds instead of 47 minutes, would you still call it a run?
Most purists say no. But the glitch hunters? They’re still looking.
The Origin: It’s Not What You Think (At First)
First, a crucial clarification: "Speedrunners build 18052020" does not refer to an official version of the popular multiplayer game SpeedRunners. The naming convention (DDMMYYYY format) is a dead giveaway. The date "18/05/2020" (May 18th, 2020) does not align with any major patch for the commercial title SpeedRunners, which had left early access years earlier, in 2016.
Instead, the term comes from the ROM hacking and independent game development scene. Specifically, it refers to a fan-made, unofficial "build" (a compiled version of game code) designed to emulate the physics, movement tech, and level design of games like SpeedRunners, but with a singular focus: breaking the game open for record-setting runs.
The build number 18052020 was originally a timestamp left in the source code by an anonymous developer (known only as V0idStrider) who created a custom engine demo for a speedrunning competition on the now-defunct EnGaming forums. The challenge was simple: build a 2D movement sandbox where top speed was limited only by the player’s input precision.
3. The Glitch That Saved a Game
Some believe 18052020 was a stealth patch for Half-Life 2 that accidentally reintroduced the “superboost” glitch. Valve allegedly reverted it within 48 hours, but not before runners captured records using it. The only remaining evidence? A single Reddit comment saying, “thank you build 18052020” — now deleted.
Abstract
This paper examines the "Speedrunners Build 18052020," a custom game modification and community-driven ruleset that emerged within the Speedrunners (by DoubleDutch Games / tinyBuild) competitive scene. It analyzes the build's origins, technical changes, gameplay impacts, community reception, and lasting influence on speedrunning practices. Where primary-source timestamps or developer changelogs are unknown, I infer likely motivations and outcomes based on documented speedrunning culture, common modding practices, and contemporaneous patches for similar titles.
6. Community Response and Governance
- Adoption mechanics
- Tournament organizers and speedrun communities often vote or mandate a build to ensure fairness.
- Verification procedures: runners submit demos, hash checks of binaries, or recordings.
- Debates
- Purists may insist on "vanilla" official builds; others prefer a community-stable build for competitive parity.
- Disputes arise when significant improvements or regressions occur between builds.
- Archiving and reproducibility
- Communities maintain build archives, diffs, and changelogs to preserve competitive integrity and historical runs.
- Case studies
- Comparative parallels from other titles where dated builds created separate leaderboards or split communities (e.g., Super Mario 64, Celeste, Doom source ports).