AI-generated
Speedrunning had one of those weeks that refuses to stay in a single lane. A new Portal exploit arrived with a name that sounds like a sci-fi disaster, a blindfolded Super Mario 64 run finally cracked the nine-hour barrier, and Super Mario Bros. remained locked in its familiar, wonderfully unreasonable battle against the limits of human input. Meanwhile, one of the community’s less glamorous problems—where knowledge actually lives—rose to the top of the conversation.
There was celebration, too, in the form of a repaired roof for LeKukie, whose pursuit of a human TAS tie has survived setbacks that would make most of us put the controller down and take up gardening. The week’s posts also offered a useful reminder that speedrunning is not only about records: it is about infrastructure, explanation, gatherings, challenge categories, and the small questions that turn a baffled spectator into a curious runner.
So this week brings both spectacular times and the connective tissue underneath them. Here are the biggest stories from the week.
The Internet’s Fastest Hobby Has a Filing Problem
The week’s biggest Reddit discussion was not about a new record at all. It was about the increasingly familiar experience of finding out that the route, resource, tech explanation, or rules discussion you need exists somewhere inside a Discord server—and nowhere else. The post struck a nerve because this is not an abstract complaint. For a new runner, “join the server” can be the difference between discovering a welcoming game and bouncing off an invisible wall.
Discord is excellent at immediacy. A runner can drop a clip, ask whether a setup is viable, and get an answer while the problem is still warm. But immediacy is a poor substitute for memory. Search engines cannot reliably index private or semi-private channels, old explanations disappear into chat history, and a server’s owner—or its backups and bots—can become a single point of failure. One of the highest-rated replies mourned the loss of public forums and observed that adding “reddit” to a search has become a modern approximation of looking for the old searchable web.
The answer is not to throw Discord away. Speedrunning needs places for rapid conversation, and communities should be able to choose the tools that fit them. The healthier model is redundancy: use Discord for the living room, but publish routes, rules, discoveries, and evergreen explanations somewhere with a durable URL. A wiki, a forum, a guide repository, even a carefully maintained document can turn a fleeting answer into a public piece of infrastructure.
That matters competitively as well as socially. The best communities do not merely produce fast runners; they preserve the path by which the next runner gets fast. If the knowledge is searchable, newcomers can arrive on their own terms. If it is trapped in a chat log, every generation starts by asking the same questions—and every expert spends their time answering them again.
Bubzia Goes Blind and Mario Finally Sees Sub-Ten
Some records announce themselves with a number so clean it feels like a dare. Bubzia’s 9:09:09 in Super Mario 64 blindfolded 120 Star is one of those numbers: a palindrome-shaped monument to concentration, route knowledge, audio cues, and an extraordinary tolerance for uncertainty. It is the first sub-ten-hour completion in the category and the first world record there in four years, improving the previous mark by more than two hours.
The category’s history makes the achievement especially funny and impressive. A commenter pointed out that this is only the second completed run, which gives “first sub-10 hour” a delightful out-of-context quality. In most categories, that phrase suggests years of incremental optimization, a leaderboard packed with runners, and a stopwatch gradually shaved by specialists. Here, the same milestone also carries the energy of a frontier expedition: the route is still being established while the record is being attacked.
Blindfolded Mario is speedrunning with the visual channel removed, but not with the game made simple. Every jump has to be translated into timing, sound, memory, and trust. A mistake does not merely cost a few seconds; it can leave the runner uncertain about where Mario is and what recovery is possible. The result is a run that asks a different question of mastery. It is not only “how quickly can you move?” but “how completely can you understand the game when one of your most useful senses is unavailable?”
The community response landed where it should: somewhere between disbelief and delighted admiration. Even people whose speedrunning knowledge consists mostly of documentary videos could look at the title and understand that something had gone deeply off the normal scale. Bubzia has not just made the category faster; he has given it a proper landmark.
LeKukie’s Roof Is Fixed, and the TAS Chase Lives
There are record updates that happen at the finish line, and there are updates that happen in the real world before a runner can even reach the start button. LeKukie’s fully repaired roof belongs to the second kind. The Super Mario Bros. runner, currently pursuing an any-percent time that can meet the TAS, had his home damaged by a windstorm—a setback with very little to do with frame rules and everything to do with ordinary life.
The community’s response was unusually tangible. A GoFundMe covered the repairs and exceeded its goal by four times, turning a worrying interruption into a public show of support. The most charming reaction described LeKukie as someone who could only be stopped by Mother Nature, with the race now back on. It is a joke, but a revealing one: people are invested not just in the number at the end of the run, but in the person enduring the attempts.
That investment makes sense when the target is this absurdly close. The week’s Super Mario Bros. posts repeatedly circled the gap between Niftski’s 4:54.332 and the RTA-rules TAS at 4:54.265. The difference is measured in frames, but the effort behind those frames is measured in years, specialized hardware, controlled inputs, and a community capable of explaining why one path through World 8-4 is faster even when it looks less intuitive.
So the repaired roof is more than a wholesome sidebar. It is part of the record story. The leaderboard is a thin layer over a thick human infrastructure: a home to repair, a controller to configure, a stream to broadcast, and enough community support to let the runner keep trying. The TAS is waiting. So, thankfully, is LeKukie.
Portal Finds a New Way to Break the Universe
Portal speedrunners have spent 18 years turning a tightly designed puzzle game into a laboratory for movement, and this week the laboratory produced a spectacular new result: Singularity Warp. The exploit begins with an absurdly high mouse sensitivity and a forced-strafe input. Under those conditions, the game’s attempt to represent infinite turning speed is converted into something even stranger—effectively infinite movement speed.
Portal responds to this impossible state the way many old games respond to impossible states: badly, and therefore usefully. A failsafe sends the player to the coordinates 0,0,0. In the right place, that is not a crash or a softlock but a shortcut. The discovery is particularly valuable in Chamber 2, where it can skip a long sequence and potentially redraw the route around the category.
The community’s first reaction was not merely “cool glitch,” but appreciation for the explanation. The video was praised for its production quality, and the top discussion immediately asked the question that defines a breakthrough: does this obsolete the optimized run, or does it create a new category of competition? That distinction matters. A trick can be fast without being legal, useful without being universal, or transformative without making every old skill irrelevant.
Either way, Singularity Warp is a lovely reminder that “fully explored” is a dangerous phrase in speedrunning. Eighteen years of attention did not make Portal predictable; it made the eventual surprise more satisfying. The game was not waiting for a new level. It was waiting for someone to ask what happens when the mouse is set to a number no reasonable person would use.
The World Record Is Four Frames Away—and Everyone Wants the Footnotes
Super Mario Bros. was everywhere in this week’s discussion, but the most useful posts were the ones explaining why a visible timer is not always the official time. Niftski’s stream can show a clean-looking 4:54.39, while the leaderboard records 4:54.332. For a casual viewer, that appears to be a contradiction. For a category this close to its TAS, it is the difference between a manually operated display and a frame-accurate measurement.
LiveSplit-style timers are designed to be readable and practical. The runner starts them by hand, and a few hundredths of a second of button timing error is entirely normal. Super Mario Bros. has a more exact clock available in the game itself: moderators can use frame information, including the behavior of the final sequence, to determine the precise timing of the run. The official result is therefore not whatever digits happened to appear on stream at the instant someone pressed a key.
That distinction can sound like bookkeeping until the record is only a handful of frames from the TAS. Then it becomes the story. A video deep dive into the first recorded SMB any-percent run and Niftski’s recent record used frame rules to connect the category’s history to its current edge-of-humanity state. The comments responded with the dream scenario: Niftski and LeKukie racing live and tying the TAS simultaneously.
Even the basic questions are wonderfully technical. Why take the blue path in World 8-4 after a fast acceleration? Because Mario’s speed is capped in ways that make the seemingly direct red route unreachable at the required angle. Why is the start timer so precise? Because the runner is aiming for a narrow frame window, not simply clicking “go” when the level looks ready. The magic is not that the tricks look impossible; it is that the explanations reveal a machine made of tiny, comprehensible rules.
The Marathon Calendar Is Bigger Than One Initialism
A question about large-scale events not run by GDQ prompted a useful correction to the idea that speedrunning’s live community has one obvious address. GDQ is enormous and important, but it is not the whole calendar. The replies pointed toward ESA in Europe, RTA in Japan, Speedons in France, AusSpeedruns in Australia, and BSG, alongside online communities such as SpeedGaming and its tournament scene.
These events do different jobs. Some are in-person marathons with their own regional identity; some offer English restreams; some center on tournament formats and commentary rather than a single giant stage. That variety is healthy because it gives runners more than one route into the social side of the hobby. A person who cannot travel to one event may find a local gathering, a different language community, or an online race that fits them better.
The discussion also exposed a familiar tension: asking for more points of access was met with downvotes by some readers, even though the request was fundamentally about expanding the ecosystem. Speedrunning benefits when attention, expertise, and opportunity are distributed. A bigger calendar means more hosts, more commentators, more games represented, and more chances for a runner to discover that their community is not a niche corner but part of a much larger map.
And if you want a historical way into that map, the answer may be Super Metroid. A thread asking which game has appeared most often at GDQ produced a cautiously researched favorite: 25 mainline appearances for Super Metroid, ahead of Super Mario 64’s 21, with Ocarina of Time and Super Mario World close behind. Count the ROM hacks and the spreadsheet gets murkier, but the larger point is clear: a marathon’s identity is built over time by games that can keep returning to the stage.
Small Games, Strange Categories, Big Personal Wins
The leaderboard posts lower on the week’s list still captured why speedrunning keeps growing. A runner took the world record in the demo for Smash N’ Grab with a 5.93-second any-percent run, a tiny time in a tiny game that nevertheless demands the same essentials as a famous marathon category: clean execution, route familiarity, and the willingness to keep resetting for a better attempt. One commenter had played the demo at Gamescom and could immediately feel the gap between a 13-second personal effort and a sub-six-second run.
At the other end of the scale, an Octopath Traveler challenge run defeated Galdera at level 1 in 5:23:00. It is not a formal leaderboard category, and the runner was clear about that. That honesty is part of the appeal. Challenge runs are where route design, self-imposed restrictions, and “can this even work?” thinking meet, often producing categories that are too particular to be official but too interesting to ignore.
There was also a community race for King’s Quest VI, a space run with a current record in the hundreds, and the pleasingly niche business of optimizing a demo nobody has had time to over-explain yet. None of these stories needs to compete with the headline records. They are evidence that the hobby’s frontier is not one line on one leaderboard. It is every game where someone looks at a timer and thinks, “I wonder what happens if I try this properly.”
That is the through-line between a five-second demo and a five-hour challenge: the category is an invitation. Sometimes the reward is a world record. Sometimes it is a route no one else has bothered to document, a new personal best, or a comment section full of people learning how the rules work. Speedrunning is at its best when all of those victories are allowed to matter.
A Week of Records, Repairs, and Better Explanations
This week’s stories shared a surprisingly consistent message. The spectacular moments—the blindfolded sub-ten, the Portal warp, the four-frame SMB chase—are only possible because someone has built an ecosystem around them. Runners preserve techniques, viewers ask questions, moderators measure the exact frames, event organizers make room on the schedule, and communities show up when a roof needs fixing.
That is also why the argument about Discord matters. Speedrunning’s future depends on lowering the cost of curiosity. The next Bubzia should be able to find the route. The next Portal discovery should be explainable six months later. The next person wondering why Mario takes the blue path should encounter an answer that survives longer than a scroll through chat. Fast communities need durable memory.
For now, the records keep moving and the questions keep getting more specific. A timer can be wrong by a few hundredths; a path can look slower and be faster; a game can be solved for 18 years and still hide a singularity. That combination of precision and surprise is the reason speedrunning never quite becomes routine.
Keep the routes public, keep the events multiplying, and keep an eye on that SMB finish. See you next week.
Source: reddit.com