Uploaded May 2017 | Updated November 2026, 3 hours ago
This is a 0th day wrong warp. It's also really dumb.
Also it turns out Kyle made this same video so go watch his it's better youtube.com/watch?v=lIxKEw3CN8o
This is a 0th day wrong warp. It's also really dumb.
Also it turns out Kyle made this same video so go watch his it's better youtube.com/watch?v=lIxKEw3CN8o
![Building a RAM Editor in Ocarina of Time
I mentioned that this specific application may not stay exclusive to Wii U, though that currently looks unlikely. Both the Gamecube and Wii VC versions of the game map the dpad to the N64 L button in their emulators, so without external modification its not possible to use the event editor on those versions. N64 of course has a functioning dpad but its inability to write to misaligned memory addresses makes it unlikely that this functionality can be achieved on that console without ACE.
Below Ill outline the full method for doing this trick, but if youre just interested in messing around with the custom RAM editor (missing textures and all), you can simply write the following values (addresses for version 1.2) to replicate the result of the rta setup without the hassle:
Set 800F9238 to 8001EC00
Set 800E8720 to 800E8730
Set 800E8728 to 800E8732
Doing this glitch requires 4 applications of lightnode srm (some technical information about which is available here https://docs.google.com/document/d/1Xf0mTcGwxbuBBFX1TYhKuRdfdH34wW9492RN-1YmIUM/edit).
Each srm has the same heap setup, shown here https://www.youtube.com/watch?v=Udk4ckbeucY.
The first srm uses the file 1 name, 800FC550 803F0F0A
(file names can be converted from hex to characters with https://lemon32767.github.io/ootfname). The angle for dropping the rock is ACA0, and a setup is shown here https://www.youtube.com/watch?v=vZA7u2XCsoE.
Each time you do lightnode srm it breaks the actor heap, so youll need to transition areas (to deku tree) before doing anything.
After the first srm, die and quit back to title (you can save) and enter 016C0080 800F9235 as file 3. Youll know your srm was successful if Saria greets you when you start file 1 again.
Now file name 3 should be copied to the inf_table flags (at 8011BB8E specfically). Performing another lightnode srm with angle BB8A (setup https://www.youtube.com/watch?v=plY441oAe7M) should open the event editor (at the cost of textures).
Now we can do the same srm with the same angle, except beforehand well use the event editor to write 800E8718 800E8730 to 8011BB8E. In binary this looks like
inf_table[11] inf_table[12]
8 0 0 E 8 7 1 8
1000 0000 0000 1110 1000 0111 0001 1000
inf_table[13] inf_table[14]
8 0 0 E 8 7 3 0
1000 0000 0000 1110 1000 0111 0011 0000
Repeating the srm with these values should cause inf_table[0] to read 1000 0000 0001 0001 and the label of inf_table[2] to become a huge mess of English and katakana.
Now do the same thing again, except this time we write 800E8720 800E8732 to 8011BB8E. In binary,
inf_table[11] inf_table[12]
8 0 0 E 8 7 2 0
1000 0000 0000 1110 1000 0111 0010 0000
inf_table[13] inf_table[14]
8 0 0 E 8 7 3 2
1000 0000 0000 1110 1000 0111 0011 0010
If this final srm is done correctly, inf_table[1] should read 1011 1011 0111 1100 and the label for inf_table[2] should have disappeared.
At this point, scrolling down past inf_table[2] will crash the game. So dont do it. Note that while this can be taken between areas, the function that we hijack to run the event editor does not run everywhere, so it wont be available in some places.
Huge thanks to the OoT discord for finding this. As far as Im aware, the people who participated in discussing/testing are
MrCheeze
Savestate
Natalyahasdied
Blini
Yanis
Mephisto
MutantAura
Evilas
Iyce Building a RAM Editor in Ocarina of Time](https://i.ytimg.com/vi/J95D-gPBDuc/mqdefault.jpg)







![[Concept] Fixing Kamaro BA Text with Keaton BA
[JP 1.0 on Bizhawk]
First I show the crash that Kamaro BA causes. It sets the address Ive called Text Thing, 1F372E, to a nonzero value (specifically 0x17), which causes the game to crash on text boxes or loading zones (saving with this not as 0x00 also invalidates your file).
Second, I manually freeze the value at 0x00 while doing the Kamaro BA to bypass the text box crash, then set it manually to 0x17, going through the load zone to crash.
Third, I freeze it at 0x00 to bypass the text box, set it to 0x17, then use Keaton Mask BA, which sets the text byte back to 0x00, getting rid of the problem. This also sets Temp B back to 0x00, but that should be okay if we get the item onto an actual B button in the process. As far as I can tell, the only part of this that is infeasible on a console is bypassing the initial Kamaro BA textbox. [Concept] Fixing Kamaro BA Text with Keaton BA](https://i.ytimg.com/vi/NvtP996ebYs/mqdefault.jpg)

