Banjo-Tooie is a 2000 3D platformer from Rare, originally published by Nintendo for the Nintendo 64. It later received an Xbox Live Arcade release on Xbox 360, with the port credited to 4J Studios and publishing credited to Microsoft Game Studios, and it has continued to circulate through modern re-releases, including Rare Replay and the Nintendo 64 library inside Nintendo Switch Online + Expansion Pack.
As a speedrun, Banjo-Tooie is built around a huge move set, dense worlds, and a hub structure that encourages backtracking and cross-world errands, which is exactly why it condenses so well. The run is usually trying to do two things at once: move through the game’s geography as efficiently as possible, and cut the “intended” item and task load down to the minimum that still unlocks late-game access. The game’s defining mechanical twist, the ability to control Banjo and Kazooie independently in certain contexts and to swap egg types, also gives runners more routing freedom than many neighboring collectathons, because the fastest plan is often shaped by what movement options and utility shots are available at a given moment.
What makes Banjo-Tooie distinct in the wider 3D platformer speedrun landscape is how many different styles of optimization can coexist without changing the game’s identity. There is a natural “clean” version of the run that is about sharp movement, smart warp usage, and tight task order, and there is also a more aggressive approach where sequence breaks and clips can rewrite which worlds matter and when. That spectrum shows up directly in the way the scene organizes its leaderboards, with a main family of categories and additional rule sets that specifically fence off certain high-impact tricks, creating parallel routes that test different skills while still chasing the same core goal: getting through a sprawling, puzzle-box adventure in the fewest and fastest steps possible.
Before Banjo-Tooie had a modern leaderboard ecosystem, a lot of its “first generation” knowledge lived in long-form writeups and personal route notes shared in the wider walkthrough-and-guide culture. One of the clearest artifacts of that era is the dedicated “speed guide” style document, which reads like a blueprint for an efficient full-game clear, complete with level-by-level pacing targets and practical time-saving habits that assume you are learning through repetition. Those early guides helped turn a huge, non-linear collectathon into something runners could plan, test, and compare in a consistent way, even before there was a single dominant public leaderboard for the game.
Formal record-keeping, and the first widely preserved “standard goals,” crystallized through sites that hosted full runs with author notes and definitions rather than just posting a time. Speed Demos Archive is especially important here because it preserved not only the footage but also the reasoning behind it. Its hosted 100% run documents an explicit definition that matches what the game tracks on its totals screens, including core collectibles and even Stop ’n’ Swop-related items, and it also makes clear that the run’s route planning built directly on community-written guides rather than starting from scratch. In other words, the earliest “standard” for 100% was not just “grab a lot of stuff,” it was a spelled-out checklist of tracked completion items that could be verified and repeated.
Timing norms and platform realities were part of that early standardization, too. In the N64 era, runners leaned on manual timing practices, while later releases created new timing assumptions and, eventually, new route families. When the game reappeared on Xbox platforms, the community treated it less like a simple port and more like a distinct competitive environment, since differences like loading behavior, text speed, and patched quirks could force meaningful reroutes. That is why you see separate resources built specifically for an Xbox version 100% route, and why version-awareness in Banjo-Tooie tends to focus on regional and platform differences rather than patch history in the traditional modern sense.
As Banjo-Tooie speedrunning matured into a self-maintaining scene, it followed a familiar pattern: early knowledge circulated through scattered guides, forum posts, and individual uploads, then gradually consolidated into a handful of shared “home bases” where runners could compare rules, troubleshoot tricks, and keep routing knowledge from getting lost. Today, the public-facing record is centered on Speedrun.com, where categories, rules, and verified times are organized in one place, and where a run’s legitimacy is tied to clear documentation and moderator review.
The community’s day-to-day conversation and problem-solving has largely moved to Discord, which functions as the fast-response layer on top of the leaderboard. The Banjo speedrunning community explicitly funnels questions there, and it is also where practical resources tend to live, such as pinned documents explaining specific setups and modern routing notes that are easier to keep current than a forum thread.
The way runs are “made official” is mostly procedural and consistent across the platform. Runners submit through the game’s page and provide the required details and evidence, after which moderators verify and publish the entry according to the board’s settings and standards. Speedrun.com’s own support guidance also sets expectations for the human pace of verification, including a general window in which moderator teams are expected to process submissions, which helps explain why most communities treat submissions as a queue rather than an instant update.
Around that core, discovery and culture still flow through broader public platforms. Twitch broadcasts and archived VODs are how many runners first encounter the game’s routes in motion, while Reddit threads and community posts often act as the “front door” for newcomers asking how to start, what resources matter, and where the real discussion happens.
On the main public leaderboards, the category set is built around a few “completion lenses” rather than one single way to finish the game. The core family includes Any% and 100%, each with additional variants that exist specifically to draw a bright line around the biggest sequence breaks. Alongside those headline categories, the community also keeps separate boards for challenge definitions like All Bosses, Cheato%, Low%, and New Game +, plus a set of level-specific boards for runners who focus on isolated sections instead of full-game routing.
The “big rule decisions” in this game come down to what the run is allowed to do with major warps and boundary breaks. A key example is DCW, short for Delayed Cutscene Warp: a wrong-warp setup built around stored cutscenes that can relocate you to another map and, with the right storage, even warp you to the final fight. The community treats DCW as powerful enough to merit dedicated restriction categories, and it is explicitly excluded in No DCW/BC rule sets.
The other headline restriction is “bitclips,” which function as early-entry or out-of-bounds style boundary breaks that let runners reach places earlier than intended, including standardized setups that the community practices (you will often see these discussed as named clips like Hag 1 Early or Witchyworld Early). That makes “No Bitclips” categories an identity choice more than a minor rules tweak: you are playing essentially the same objective, but with a whole class of early-entry tools removed. A related theme shows up in community discussion of RTA-viable “floating point clip” approaches that can substitute for warps in restricted rule sets, which is part of why the boundary between “warp tech” and “clip tech” matters so much for how the boards are organized.
For 100%, the modern definition is framed around what the game itself records on the Game Totals screen, with Hag 1 still treated as required because it is the final boss. That has an important practical consequence: even when a route reaches Hag 1 early through major tech, the run is not “over” until the totals requirement is satisfied, which is why you will see strategies that treat the Hag 1 fight and the totals screen as separate checklist endpoints rather than the same finish line.
A smaller but very “this community” kind of rule nuance is how the boards handle known manipulations that affect comparability. One documented example is Jinjo manipulation, where the community applies a standardized time adjustment to keep manipulated and non-manipulated runs meaningfully comparable under the same timing format.
Finally, platform policy is baked into the leaderboard structure. The game’s listings and runs are commonly separated by platform families (original hardware versus later console releases), and runners typically treat version and platform as part of the rules context because lag behavior, load behavior, and setup consistency can shift how routes are validated and compared even when the objective is identical.
Banjo-Tooie’s speedrun route has steadily shifted from “do everything efficiently” toward “do only what unlocks progress,” and much of that refinement has come from learning how to control the game’s built-in variability. A classic example is how runners learned to route around Jinjo patterns, because the colors you need for full families change by pattern and can reshape how quickly you can complete key errands. Even in earlier documented routes, you can see the run treating Jinjos as both a collection problem and a cutscene-management problem, with choices made to reduce slow scenes and keep the run’s rhythm intact. From there, the next step in maturation was turning that variability into something you can deliberately set up, with community guides and shared files designed specifically to produce a favorable pattern for competitive runs.
The biggest “paradigm shift” on the glitch side came from Delayed Cutscene Warp, because it reframed what the run was even optimizing. Instead of treating the late game as a lock behind a long list of requirements, DCW exploits the game’s tracking of the last map where a cutscene played, then uses that stored state to wrong-warp when entering Fuel Depot, letting runners reach areas far earlier than the intended progression. Once that door opened, the community’s strategy evolution was not just “get faster,” but “separate the game into rule sets,” creating different competitive identities depending on whether DCW is allowed or intentionally excluded.
In parallel, movement and boundary-breaking became more standardized and teachable, which is when routes began to look less like personal improvisations and more like repeatable technical scripts. The most famous family of tricks here is the set of floor and boundary clips commonly referred to as bitclips, which are powerful precisely because they can be applied in many places and can change access order across multiple worlds. The scene also pushed techniques that were once treated as “theoretical” into real-time consistency, including the kind of floating-point clip work that relies on extremely precise inputs and timing windows. The end result is a run culture where the route is not only faster, but also more modular: you can map the entire game’s fastest solutions, then toggle large classes of tech on or off depending on category rules without losing the core identity of the run.
That same maturation shows up in the tooling and training layer that supports the run. The community has kept practical resources centralized, including a dedicated practice ROM for drilling setups, plus shared route documents, manipulation files, and other aids that preserve hard-won knowledge in a form newcomers can actually use. As more of the scene’s education moved into video tutorials and curated guides, the culture of Banjo-Tooie speedrunning increasingly became about repeatability: not just discovering a trick, but packaging it into a method that can be practiced, verified, and folded into a stable route that holds up across many runners and many attempts.
One of the earliest “this is what a serious Banjo-Tooie run looks like” milestones was the move from private route notes into publicly archived full-game performances with written context. When a complete 100% run is preserved alongside author commentary, route breakdown, and timing caveats, it becomes more than a time to chase. It becomes a shared reference point for what counts as a complete objective, where the run is likely to bleed time, and how the community should think about start and end points when comparing attempts.
A second milestone type is the moment a single discovery forces the scene to define itself in rules, not just in execution. Delayed Cutscene Warp is important in that way because it changes what “progression” even means. Once runners can store a cutscene state and convert it into a wrong-warp pathway with Fuel Depot as the hinge, the route stops being a long march of required unlocks and becomes a question of what tech your category allows. That is the kind of breakthrough that naturally produces parallel leaderboards, including rule sets explicitly built to exclude the biggest warps and boundary breaks to preserve a different style of run.
Another defining milestone is when knowledge stops living in scattered explanations and starts living in tools and maintained references. Banjo-Tooie’s scene has a clear “infrastructure” layer now, including a practice ROM distributed as a shared community resource, plus centralized materials for things like Jinjo pattern tracking and other consistency aids. When those resources are hosted and indexed in one public place, it changes how people learn the game: the run becomes teachable in repeatable pieces, and the community’s standards become easier to preserve across generations of runners.
Visibility milestones matter too, especially when a run has to be understandable to an audience that is not already inside the niche. Banjo-Tooie’s appearances under the Games Done Quick umbrella, including Summer Games Done Quick showcases and shorter-format features through Games Done Quick Hotfix, function as watershed moments because they turn routing and trick explanations into a public performance. That kind of stage tends to raise the bar for clarity, commentary, and demonstration, and it often becomes the run that new runners point to when they are deciding whether to learn the game.
Finally, there is the quieter but lasting milestone of cross-platform normalization. As the game has remained playable through multiple console ecosystems, the leaderboard structure has had to make platform context explicit, with console filters and separated boards reflecting the reality that consistency, loads, and setups can be materially different across releases. The long-term effect is a scene that treats version identity as part of competitive fairness rather than an afterthought, and that can support parallel competition without fragmenting the community’s shared knowledge base.
Falcon – Any% (N64) – 25:49 – ≈ March 2025 – N64 – A modern Any% benchmark on the N64 board, reflecting the fully-developed skip-heavy route.
hagg_ – Any% (N64) – 26:57 – ≈ February 2023 – N64 – A defining WR-era run explicitly framed around “starting with the WW bitclip,” capturing how route-defining clips shaped the category’s identity.
JustAMoose – Any% (Xbox) – 39:52 – January 12, 2026 – Xbox 360 – A recent top mark on the Xbox leaderboard, useful as a reference point for console-era parity and category health beyond N64.
Falcon – Any% No Bitclips (N64) – 41:53 – ≈ July/August 2025 – N64 – A clear “No Bitclips” snapshot that’s historically useful because it preserves what the route looks like when that major class of wall clips is off the table.
Falcon – No DCW/BC (N64) – 2:38:37 – ≈ July/August 2025 – N64 – A leading “No DCW/BC” time representing the community’s long-form, glitch-restricted tradition and how far optimization can go even without the headline skips.
GarageDoorOpener – No DCW/BC (N64) – 2:46:24 – ≈ February 2023 – N64 – Notable as a “route era” marker (even the run description flags a fresh approach), useful for tracking when major re-thinks became the norm in this ruleset.
Hyperresonance – No DCW/BC (N64) – 2:52:20 – ≈ February 2015 – N64 – A classic “older-era” anchor on the No DCW/BC board that helps show how the category looked before later waves of refinement.
Falcon – 100% (N64) – 4:16:15 – ≈ February 2022 – N64 – The current top 100% time on the N64 leaderboard, a headline benchmark for the game’s full-completion tradition.
Duck – 100% (N64) – 4:37:30 – ≈ February 2018 – N64 – A long-form completion reference with a preserved VOD link (even flagged as “at risk”), useful when documenting older record eras and commentary coverage.
Hyperresonance – Single-segment with resets (SDA) – 2:52:57 – 2014-06-10 – N64 – A foundational archive run with extensive runner notes, great for illustrating the pre-speedrun.com “documentation style” and route logic of the time.
Peter ‘Dragorn’ Branam-Lefkove – 100% with deaths (SDA) – 4:54:13 – 2005-12-19 – N64 – A landmark early 100% document that also preserves a detailed written definition of what “100%” meant for the project.
Duck – Any% (marathon showcase) – 36:25 – 2022-06-30 – N64 – A visibility milestone via Games Done Quick (SGDQ 2022), representing how the game is explained and presented to a broad audience.
GarageDoorOpener – Any% (marathon showcase) – 44:47 – 2018-07-01 – N64 – Another major exposure point at SGDQ 2018, helpful when you want to talk about “how the run looked” in that era.
Hyperresonance – Any% (marathon showcase) – 3:01:50 – 2014-06-22 – N64 – Early Games Done Quick representation (SGDQ 2014), useful as a “first big stage” reference for the game.
Nintendo. “New updates for Nintendo Switch Online + Expansion Pack members!” Nintendo (October 28, 2024). Accessed February 1, 2026. URL: https://www.nintendo.com/us/whatsnew/new-updates-for-nintendo-switch-online-expansion-pack-members/
Nintendo Australia. “Nintendo Switch Online Magazine: October Edition 2024.” Nintendo Australia (October 28, 2024). Accessed February 1, 2026. URL: https://www.nintendo.com/au/news-and-articles/nintendo-switch-online-magazine-october-edition-2024/
Nintendo UK. “Banjo Tooie.” Nintendo UK (Nintendo Switch Online – Nintendo 64). Accessed February 1, 2026. URL: https://www.nintendo.com/en-gb/Games/Nintendo-64/Banjo-Tooie-2809713.html
Microsoft. “Banjo-Tooie.” Xbox Store. Accessed February 1, 2026. URL: https://www.xbox.com/en-us/games/store/banjo-tooie/9p7g9bghj4pk
Xbox Wire. “Arcade: Banjo-Tooie.” Xbox News (April 29, 2009). Accessed February 1, 2026. URL: https://news.xbox.com/en-us/2009/04/29/aracde-banjo-tooie/
Hryb, Larry. “Banjo-Tooie Now Available.” MajorNelson.com (April 29, 2009). Accessed February 1, 2026. URL: https://majornelson.com/2009/04/29/banjo-tooie-now-available/
Speedrun.com. “Banjo-Tooie.” Speedrun.com leaderboards hub. Accessed February 1, 2026. URL: https://www.speedrun.com/bt
Speedrun.com. “Banjo-Tooie – Guides.” Speedrun.com. Accessed February 1, 2026. URL: https://www.speedrun.com/bt/guides
Speedrun.com. “Banjo-Tooie – Resources.” Speedrun.com. Accessed February 1, 2026. URL: https://www.speedrun.com/bt/resources
Speedrun.com. “(PLEASE READ BEFORE POSTING) Banjo Speedrunning Discord.” Speedrun.com Forums (Banjo-Tooie). Accessed February 1, 2026. URL: https://www.speedrun.com/bt/forums/qiwhm
Banjo Speedruns. “Banjo Speedruns.” Banjo Speedruns community hub. Accessed February 1, 2026. URL: https://banjospeedruns.com/
Banjo Speedruns. “No DCW/BC (Banjo-Tooie).” Banjo Speedruns. Accessed February 1, 2026. URL: https://banjospeedruns.com/bt/categories/nodcwbc
Speed Demos Archive. “Banjo-Tooie.” Speed Demos Archive. Accessed February 1, 2026. URL: https://speeddemosarchive.com/BanjoTooie.html
Speed Demos Archive Forums. “Banjo Tooie.” Speed Demos Archive Forums. Accessed February 1, 2026. URL: https://forum.speeddemosarchive.com/post/banjo_tooie.html
McKenzie, Michael (mike89). “Banjo-Tooie – Speed Guide (Nintendo 64).” GameFAQs (updated July 8, 2005). Accessed February 1, 2026. URL: https://gamefaqs.gamespot.com/n64/196695-banjo-tooie/faqs/37815
The Rare Witch Project Forums. “Banjo-Tooie Glitch Guide.” The Rare Witch Project Forums (August 30, 2015). Accessed February 1, 2026. URL: https://www.therwp.com/forums/showthread.php?t=54426
Cronikeys. “Warp from Fuel Depot to Hag 1.” YouTube video. Accessed February 1, 2026. URL: https://www.youtube.com/watch?v=19TM9rc6VeQ
The8bitbeast. “Banjo Tooie has a huge new glitch! Split Up Pad Wrong Warp.” YouTube video. Accessed February 1, 2026. URL: https://www.youtube.com/watch?v=6w6rp4p6lsg
Cronikeys. “Banjo-Tooie Glitches.” YouTube playlist. Accessed February 1, 2026. URL: https://www.youtube.com/playlist?list=PLzGKgGmE443V2Ie6rXBrY2OY7LFbPYC68
GDQ Tracker. “Run Index — Summer Games Done Quick 2018.” Games Done Quick Tracker. Accessed February 1, 2026. URL: https://tracker.gamesdonequick.com/tracker/runs/sgdq2018
Games Done Quick. “Banjo Tooie by GarageDoorOpener in 44:47 – SGDQ2018.” YouTube video. Accessed February 1, 2026. URL: https://www.youtube.com/watch?v=zY0uwII2dtY
GDQ Tracker. “Run Index — Summer Games Done Quick 2022.” Games Done Quick Tracker. Accessed February 1, 2026. URL: https://tracker.gamesdonequick.com/tracker/runs/SGDQ2022
Games Done Quick. “Banjo-Tooie by duck in 36:25 – Summer Games Done Quick 2022.” YouTube video. Accessed February 1, 2026. URL: https://www.youtube.com/watch?v=VI3J7Kjq1Q4