A ground breaking game like Super Mario 64, the Legend of Zelda: Ocarina of Time threw Link into 3D and what a great game it was, the only bad thing about it was the long name! It is said that Ocarina of Time runs on a "heavily modified Super Mario 64 game engine" which is a little strange as they're quite different games, however, it allowed Nintendo to finish the N64's first Zelda game quicker than starting fresh.
Even in the released version a debug facility was left in which can be triggered by entering a button combination on the controller when the game has crashed, but only when a small yellow line appears in the upper left hand corner of the screen (like the red square that appears when Mario Kart 64 has crashed). This can be seen in this screenshot:
(Pic to be added.)
One way to crash the game so that the yellow line shows up is by changing a floating-point value in memory so that it is invalid. I did just that by locating one of Link's position variables and modifying it in such a way that it caused the game to crash. After entering a certain combination of buttons on the controller (which is difficult to enter right), the debug screen shows up:
This is from the PAL version running on a real N64. Note that at the top is says 'Floating point exception' because I caused the game to crash since it doesn't know how to interpret the floating-point value stored in memory. But the game hadn't actually totally crashed, I could still enter the Equalizer's (the cheat code cartridge I used) in-game menu.
There are other debug screens but which one that shows it seems depends on the type of crash.
As if a dedication to the game that Ocarina of Time's foundations are based on, there are pictures of Mario and friends in the castle courtyard where Young Link first encounters Princess Zelda.
(Pic to be added.)
You have to look through one of the side windows to see the pictures but I used a code to raise and then lower Link over the wall to get a better look. The Mario picture is of the plumber flying using the wing cap which is an obvious reference to SM64 but what is a little strange is that the pictures are of different sizes and look like they were put in quickly, maybe last minute.
Zelda is a huge game and the use of the exit modifier allows jumping to any of the areas including cut-scenes. I will list values here for the exit modifier but please note that certain condition can affect where you end up including whether you are playing as young or adult Link, and if you have any so-called beta codes on.
Note: 0x means hexadecimal.
0x0088 Ice cavern (1F).
0x00EE Kokiri forest.
0x0166 Fire temple (1F).
0x0188 Hyrule field (from Kokiri forest).
0x019A Zora's river (from sky).
0x01AC Lost woods.
0x0225 Zora's fountain.
0x0284 Hyrule field.
0x0311 Exit from Zora's river to Hyrule field.
0x0380 Zora shop.
0x03C4 Exit from Zora shop to Zora's domain.
0x03D4 Exit from Ice cavern to Zora's fountain.
0x0440 Ganondorf defeated and Zelda freed cutscene.
0x0462 Fishing pond.
0x0488 Thieves' hideout.
0x05A4 Down hole (under gravestone) from Lake Hylia.
0x0604 Warp to Lake Hylia.
[The following is based on a document of mine recorded on: 29/7/4]
The user of the game is allowed to enter a maximum of eight characters for their filename, however, it's actually always eight long since the game program inserts spaces (0x3E) after a name which is shorter than eight letters. Standard ASCII is not used for the filename even though it is for cutscenes and signposts text.
Once a file has been loaded and gameplay starts, the file is ready for editing. For the PAL version that I have, the first character of the filename is stored at address 0x80118434, and the eighth at 0x8011843B, in the RAM.
Lowercase and uppercase latters are allowed, as are the numbers 0-9, and also a couple of other characters including the space character. Any value above 0x3F causes the standard ASCII to be used.
As can be seen from the listing below, the first characters and the values used to select them are fit for hexadecimal as they are ranged as 0-9 and A-F:
As an example, if I wanted the filename to be the same as my first name 'James' I would use these values:
0x13 0x24 0x30 0x28 0x36 0x3E 0x3E 0x3E
I use the Equalizer cheat code cartridge to learn about how Zelda: Ocarina of Time works, mainly using its memory editor which is accessed by pressing the button on the Equalizer, provided that the code generator was enabled at the boot menu. Sometimes the game does crash when exiting the Equalizer's in-game menu, even after doing a search, as if the game suddenly detects the cheat code cartridge. Unlike games such as SM64, even after the game has crashed, the Equalizer's in-game menu can still be triggered.
One annoyance with making codes for Zelda: Ocarina of Time using a cheat code cartridge is that you have to first boot the N64 and Equalizer with a game such as SM64, change the keycode, and then swap with Zelda: Ocarina of Time (after turning the power off first!).
I have also used the emulator Nemu64 for making codes for Zelda: Ocarina of Time which also helps which checking or converting NTSC codes.
Fortunately a lot of the text is stored in ASCII (the standard for storing text) so it can be viewed without any form of converter, which has proved to be very revealling such as references to more advanced features that never made it, such as the 64DD.
Here is some interesting text that can be found loaded into the RAM. Although the addresses are for the PAL game, you can search for the text using your version of the game.
80006B6C I LOVE YOU
80006BF4 Hung Up in thread
80006D2C 98-11-18 17:36:49
801043C0 ACTOR NAME is NULL
801043D8 ACTOR NAME
80106D30 RCP is HUNG UP!!
80106D44 Oh! MY GOD!!
80107568 Stack Trace ROM DEBUG
As characters talk, the text that they say is loaded into the RAM; if you alter it using codes or by RAM editing it has no affect unless you modify text that is not yet displayed.
New: Updated Debug.
How I Hack Zelda Ocarina of Time
Exit Modifier Values.
You can email me at email@example.com