In an alternate 1996, Nintendo’s secretive debugging team stumbles upon a fully functional splitscreen multiplayer build of Super Mario 64 —a mode so chaotic and ambitious it threatens to break not just the game, but their understanding of cooperative platforming. Part 1: The Cartridge in the Drawer It’s a humid July evening in Redmond, Washington. Dylan Nguyen, a 24-year-old QA tester for Nintendo of America, is the last one in the dimly lit debugging lab. His job is to verify bug fixes for the Japanese 1.1 revision of Super Mario 64 , but his real passion lies in the game’s unused data—scraps of text, placeholder assets, and one curious file simply labeled SPLIT_MULTI_TEST.bin .
Super Mario 64 on original hardware renders about 30,000 triangles per frame at 30 FPS. Splitscreen forces the N64 to render two full scenes—closer to 55,000 triangles. Even with aggressive LOD scaling (Mario becomes a 50-polygon lump from ten meters away), the frame rate dips to 12–18 FPS in levels like Dire, Dire Docks .
The final nail: Miyamoto’s playtest notes, buried as a text dump. Translated roughly: “Two Marios is fun. But friends should play together, not compete for camera. N64 is for sharing one dream, not two halves of a screen. Focus on single-player. Save multiplayer for next hardware.” Dated October 4, 1995. Dylan and Sandra never release the build. They archive it, write a private report, and return to testing Diddy Kong Racing . The splitscreen mode remains on a single flash cart, locked in Nintendo’s NoA vault.
And every time they reach Cool, Cool Mountain , they still miss the Team Star on the first three tries.
Dylan’s hands tremble. He nudges Control Stick 1. Mario runs right. He nudges Control Stick 2. Luigi jumps in place.
It’s real. Two-player splitscreen. Local. On original hardware. The next morning, Dylan calls his lead, Sandra Okonkwo, a former Rareware engineer. Together, they reverse-engineer the mode.
In an alternate 1996, Nintendo’s secretive debugging team stumbles upon a fully functional splitscreen multiplayer build of Super Mario 64 —a mode so chaotic and ambitious it threatens to break not just the game, but their understanding of cooperative platforming. Part 1: The Cartridge in the Drawer It’s a humid July evening in Redmond, Washington. Dylan Nguyen, a 24-year-old QA tester for Nintendo of America, is the last one in the dimly lit debugging lab. His job is to verify bug fixes for the Japanese 1.1 revision of Super Mario 64 , but his real passion lies in the game’s unused data—scraps of text, placeholder assets, and one curious file simply labeled SPLIT_MULTI_TEST.bin .
Super Mario 64 on original hardware renders about 30,000 triangles per frame at 30 FPS. Splitscreen forces the N64 to render two full scenes—closer to 55,000 triangles. Even with aggressive LOD scaling (Mario becomes a 50-polygon lump from ten meters away), the frame rate dips to 12–18 FPS in levels like Dire, Dire Docks . Super Mario 64 Splitscreen Multiplayer -Normal ...
The final nail: Miyamoto’s playtest notes, buried as a text dump. Translated roughly: “Two Marios is fun. But friends should play together, not compete for camera. N64 is for sharing one dream, not two halves of a screen. Focus on single-player. Save multiplayer for next hardware.” Dated October 4, 1995. Dylan and Sandra never release the build. They archive it, write a private report, and return to testing Diddy Kong Racing . The splitscreen mode remains on a single flash cart, locked in Nintendo’s NoA vault. In an alternate 1996, Nintendo’s secretive debugging team
And every time they reach Cool, Cool Mountain , they still miss the Team Star on the first three tries. His job is to verify bug fixes for the Japanese 1
Dylan’s hands tremble. He nudges Control Stick 1. Mario runs right. He nudges Control Stick 2. Luigi jumps in place.
It’s real. Two-player splitscreen. Local. On original hardware. The next morning, Dylan calls his lead, Sandra Okonkwo, a former Rareware engineer. Together, they reverse-engineer the mode.