Uploaded March 2020 | Updated November 2026, 8 hours ago
When the OoT GameCube developers were building the emulator they used to port the game to GC, they couldn't figure out how to emulate the credits correctly without crashing. So instead they made it so that if you ever jump to address 81000000, which isn't a valid N64 address, emulation of the N64 stops and the gamecube starts playing a prerendered video file. This is a setup to trigger that jump.
Note that since I'm testing on an N64 emulator and not Dolphin, triggering the credits isn't actually possible. But on a real GC you would just walk forward and trigger them.
pastebin.com/SmQL9hXQ
The idea to warp to the GC credits via only function calls and not "true ACE" was suggested by ZFG, Danny, Savestate and maybe others, not me.
This method is considered "not ACE" by the current OoT speedrun rules, although the MM ruleset considers instruction pointer manipulation to be equivalent to ACE.
When the OoT GameCube developers were building the emulator they used to port the game to GC, they couldn't figure out how to emulate the credits correctly without crashing. So instead they made it so that if you ever jump to address 81000000, which isn't a valid N64 address, emulation of the N64 stops and the gamecube starts playing a prerendered video file. This is a setup to trigger that jump.
Note that since I'm testing on an N64 emulator and not Dolphin, triggering the credits isn't actually possible. But on a real GC you would just walk forward and trigger them.
pastebin.com/SmQL9hXQ
The idea to warp to the GC credits via only function calls and not "true ACE" was suggested by ZFG, Danny, Savestate and maybe others, not me.
This method is considered "not ACE" by the current OoT speedrun rules, although the MM ruleset considers instruction pointer manipulation to be equivalent to ACE.










