AI-generated
Speedrunning had a little bit of everything this week: a 14-hour pilgrimage through Hyrule, a blindfolded Mario 64 milestone, a Wii Sports barrier finally cracking, and a community argument about whether “trust” can ever be fully automated. In other words, the timer kept moving, the routes kept mutating, and somebody was still finding a way to make a familiar game look completely new.
The headline accomplishment belongs to the runner who completed Breath of the Wild 100% in 14:12:39 without taking a break. That sentence is impressive before you remember what 100% means in this game. Elsewhere, the week supplied a gentler kind of endurance: a 1997 Nintendo Power memory resurfaced, a Silksong discussion made a convincing case for the pleasures of a compact run, and several old-school records reminded us that speedrunning is as much about preserving history as shaving seconds.
There was also an unusually good reminder that “speedrun” is not a single aesthetic. It can mean precision movement, route research, a scoreboard challenge, an endurance test, or simply showing the world that a game released yesterday already has a weird little competitive scene. This week’s stories all orbit that variety.
Here are the biggest stories from the week.
Hyrule’s Longest Day Has No Intermission
The new Breath of the Wild 100% world record is a feat of planning, execution, and frankly heroic stubbornness: 14:12:39, with no breaks. A category this large is already less like a sprint and more like an expedition with a timer attached. The runner has to keep a route in their head while managing combat, collectibles, travel, menu work, and the thousand small opportunities for a game as open-ended as Hyrule to become inconvenient.
The community’s reaction captured the central tension perfectly. People were delighted by the accomplishment, but the highest-scoring comment was a plea to normalize taking breaks during multi-hour runs. That is not a criticism of the record; it is a useful distinction between the achievement and the conditions under which achievements are pursued. A run can be astonishing and still be asking too much of the person at the controller.
Then there is the Korok math. The famous little forest spirits are already a punchline in Breath of the Wild, but 900 of them become something else when converted into time: roughly 75 minutes of “Yahaha!” if each interaction takes five seconds. That is before considering the route decisions needed to collect them efficiently. The joke works because it reveals the hidden shape of 100% categories: not one grand challenge, but hundreds of tiny obligations that accumulate into an absurdly technical marathon.
This record also makes a compelling case for thinking about rest as part of competitive infrastructure. If the category demands fourteen hours of concentration, a break rule would not make it less serious; it might make the result more sustainable and the competition more accessible. For now, the no-break run stands as a spectacular snapshot of human endurance. But the next evolution of the category may involve asking what a world record is meant to measure.
The 1997 PB That Refused to Become History
One of the week’s most charming posts was not a new record at all. It was a scan from Nintendo Power issue 94, where a ten-year-old runner named Adam made it into the magazine’s “The Arena” section with a strong time in Kirby’s Super Star Gourmet Race. The post is a tiny time capsule: a kid sending in achievements, waiting through the slow machinery of print, and finally seeing their name and performance preserved on glossy pages.
What makes the story land in a modern speedrunning community is the uncertainty around how the time would hold up. Today, a runner can check a leaderboard, watch the record, study an input display, and find a Discord full of people who know exactly where a second disappears. In 1997, a magazine ranking could be both the target and the evidence that you had reached someone else’s level. The feedback loop was slower, but the excitement was no less real.
The comments broadened the memory into a kind of communal alternate history. One reader wondered how the old times compare with current records; another remembered attempting to qualify for that same issue, only for a photograph of the submission to come out blurry. That detail is almost painfully perfect. Before livestream archives and digital submissions, a failed roll of film could erase a legitimate achievement from the public record.
Speedrunning often talks about history through record progressions, but stories like this reveal a second history: the runners who tried, documented, and almost made it into the archive. The leaderboard tells us who was fastest. Nintendo Power, old VHS tapes, blurry photographs, and remembered childhood attempts tell us who was there.
Wii Sports Finally Gets Its Sub-Seven Second Wind
A second sub-seven-minute time in Wii Sports — All Sports may not come with the scale of a fourteen-hour marathon, but it has the unmistakable feeling of a barrier giving way. The runner’s announcement was brief, the comments were celebratory, and the achievement itself was the kind of clean milestone that makes a category feel suddenly more real: there is now a second person on the other side of the line.
That matters because categories are shaped by their thresholds. “Under seven” is easy to understand even if you have never studied the route. It gives a community a shared wall to stare at, and once somebody climbs over it, everyone can see the handholds. The first sub-seven run proves the possibility; the second starts the race to make it repeatable.
There is a particular joy in a post whose comments consist mostly of congratulations. Not every story needs a technical autopsy or a debate about rules. Sometimes the right response is simply hell yeah. A record is a public celebration of private repetition, and Wii Sports has delivered exactly that kind of moment this week.
The SM64 Question: Can We Ever Prove a Run Is Clean?
A discussion about cheating in modern Super Mario 64 runs opened a much less comfortable door. The question was straightforward: now that source code and sophisticated tooling are widely available, what prevents somebody from making the game more lenient or altering the setup in ways that are invisible on video? The unsettling answer from the discussion is that there is no magical wall between a player and their hardware.
The most useful comments resisted the idea that source code was ever the only weak point. Emulators, consoles, controllers, capture chains, and modified game code can all complicate verification. A live stream helps, and experienced runners can often recognize suspicious timing or behavior, but “live” does not mean “trusted execution environment.” It means the community has more evidence to examine.
That sounds bleak until you remember what actually sustains a mature leaderboard: not one perfect proof, but layers of scrutiny. The runner’s reputation, the raw footage, the consistency of the performance, the reactions of other experts, and the rules of the board all contribute. None is infallible. Together, they make cheating risky and detectable enough that legitimate competition can function.
The conversation is valuable precisely because it avoids pretending that verification is finished. As runs become more optimized, suspiciously convenient changes become harder to distinguish from genuine breakthroughs. Speedrunning’s future may involve better tooling, clearer submission requirements, and more transparency about hardware and software. Trust is not a setting you toggle on; it is a process a community keeps rebuilding.
Blindfolded Mario Just Joined the Sub-16 Club
While the community debated how ordinary runs can be verified, Bubzia produced a reminder that some performances are so visibly difficult that the basic premise feels like a magic trick: blindfolded Super Mario 64, 9 Star, in 15:51. The new world record breaks the sixteen-minute barrier, despite the runner describing a few unfortunate time losses outside their control.
The comparison that stunned commenters was that this blindfolded time would place around 174th in the regular 9 Star category. That is the sort of statistic that makes a familiar leaderboard suddenly look sideways. A blindfolded run is not merely a slower version of the same thing; it is a performance built from memorized spatial models, audio cues, timing, and the confidence to commit to movement without visual correction.
And yet the run still has the grammar of a speedrun: route choices, execution, mistakes, recovery, and the ruthless arithmetic of lost seconds. “Blindfolded” does not replace optimization; it adds another layer of it. The result is both spectacular entertainment and a technical demonstration of how deeply a runner can internalize a game’s geometry.
For now, the runner says they are done with the category. That is understandable. A sub-16 blindfolded 9 Star run is a natural place to put down the controller and let everyone else process what they just watched. Of course, speedrunning has a habit of turning “done for now” into the opening sentence of the next chapter.
Silksong Finds the Sweet Spot Between Route and Spectacle
A community discussion about Silksong’s speedrun scene offered a useful argument for why some games become immediately watchable. The original poster praised the roughly 48-minute experience, the readable shape of a run, and the way the game remains compelling without requiring an all-night commitment. It is a familiar appeal: a run short enough to finish in one sitting, but dense enough to reward close attention.
The replies added the important asterisk that “the game does not break” depends heavily on the ruleset. The glitched runs absolutely do break it, and that contrast is part of Silksong’s appeal. Major glitches, no-major-glitches routes, cloakless categories, key routes, combat choices, and advanced movement can coexist as different answers to the same question: how much of the game can be bent before the run becomes a different kind of performance?
Runners pointed to a high skill ceiling in movement and combat, with encounters and traversal sections that look flashy even before the timer is considered. That is a powerful combination. The best spectator games communicate progress through motion: you can see the runner take a dangerous line, understand why it is dangerous, and appreciate the success before anyone explains the frame data.
There was also a small but worthwhile pushback against describing runs purely as “content” to consume. Speedrunning is watchable, certainly, but the communities behind these routes are not vending machines for a 48-minute experience. Silksong’s current moment works because runners are still discovering its possibilities, and viewers get to watch a competitive language form in real time.
Why Failed Runs Deserve the Spotlight, Too
One of the week’s most revealing discussions asked for live speedruns where the runner quits or the attempt collapses in public. The question came from watching long, punishing Larian-game runs, but the answers quickly widened into a conversation about failure at events. Regular streams are full of resets; what feels unusual is seeing a carefully selected GDQ or ESA run reach the point where the runner has to stop.
The top response pointed toward collections of famously bad event runs, while another commenter explained why outright failures are relatively rare on large stages: pitches include outs, and runs with a high likelihood of implosion may never be selected. That is sensible production. It also means audiences mostly see the polished surface of a process built from thousands of abandoned attempts.
When a runner does quit live, the moment can be uncomfortable, but it can also be unusually honest. A long run is not a vending-machine transaction where effort guarantees a finish. The timer records every reset and mistake, but an event camera records something else: the judgment call to protect time, energy, or the rest of the schedule. Sometimes the most professional move is to stop.
There is room for better failure archives in speedrunning. Not as schadenfreude, and not as a catalogue of people at their worst, but as documentation of how runners adapt when the plan breaks. A failed event run can teach pacing, nerves, route selection, and the limits of endurance more clearly than a flawless record ever will.
Old Games, New Glitches, and the Endless Middle
The rest of the week supplied a satisfying scatter of speedrunning’s smaller ecosystems. A new Plants vs. Zombies glitch was described as large enough to produce a category split, with future-sunglasses relevance waiting in the wings. An Ecco the Dolphin documentary traced a world-record progression from a 2006 submission through the community’s growth after Awesome Games Done Quick. These are different stories, but both are about a discovery changing what the game means.
There were also fresh personal milestones: a sub-30 run in a game with a deliberately adult premise, a Saints Row 2 completion under three hours, and a first Neon Dodge run from the game’s own developer. None needs to be inflated into a world-shaking headline. Their value is that they show the middle of the speedrunning pyramid, where categories are being established, rules are being clarified, and somebody is always making the first serious attempt.
The developer-run in Neon Dodge is especially endearing because it includes the honest admission that an exploit probably exists and the time can easily be beaten. That is not a weakness; it is how a leaderboard begins. A game gets a timer, then a route, then a faster route, then an argument about what counts as a glitch, and eventually a history no one could have predicted from the launch build.
Meanwhile, the Ecco documentary reminds us that “dead” games are often only quiet games. A camera-freeze discovery can sit dormant until the right people find it. A marathon showcase can bring new eyes. A single runner can turn an obscure category into a progression worth documenting. Speedrunning’s archive is full of these delayed explosions.
This was a week of extremes, but the connective tissue was persistence. A fourteen-hour record, a childhood magazine entry, a second sub-seven, a blindfolded milestone, and a brand-new glitch all come from the same impulse: learn the game closely enough that its limits become visible, then test whether those limits are real.
The conversations around the runs mattered just as much as the records. The community celebrated breakthroughs while asking better questions about breaks, verification, failure, and the language we use to describe watching. That balance is healthy. Speedrunning can be thrilling without pretending that runners are machines, and competitive without pretending that trust is automatic.
Next week, somebody will find another shortcut, another old submission will resurface, and another category will discover that its “impossible” barrier was merely waiting for the right person. Until then, take a break during the fourteen-hour runs, save your blurry photographs, and remember that every leaderboard starts with one person willing to press start. See you next week.
Source: reddit.com