Uploaded May 2020 | Updated November 2026, 16 hours ago
This project was completed in Sept. 2018, but I sat on it at the time due to not having the motivation to make a proper explanation video back then. But with the Gold/Silver prototypes having renewed relevance recently, it seems like as good a time as any to release this as it exists.
The most important thing in ACE is of course the entrypoint. Given how limited the demo boundaries are, it wasn't easy to find one, but it exists. Whenever you take a held item from a Pokemon the game runs some code to put it back in the bag. The code that runs depends on what pocket the item is assigned to. If you take an invalid item that doesn't have a pocket assigned, the game glitches and jumps to an address in RAM instead (address EA77 in echo ram, to be specific). This is one key piece of the puzzle.
The other key piece is the select glitch, which is documented on GlitchCity: glitchcity.info/wiki/Select_glitches_(Gold/Silver_Nintendo_Space_World_1997_demo)
Basically, if you have N items in your bag, it's possible to swap any Pokemon in your party with Pokemon slots up to #N. If N is more than 6, this lets you corrupt parts of memory other than party data. With a well chosen set of swaps, it's possible to use this to copy an ACE payload near EA77.
The overall route, then, goes like this:
- Start the demo. You will have 5 items to begin with. Also, you will be randomly assigned a starter, if it's grass or water you can continue, but reset if it's the fire starter.
- catch a Girafarig with a held Apple. (note that it only has a chance of carrying an Apple in the Gold non-debug build, which is the most recently updated of the four '97 builds)
- name the Girafarig C1 9E, which happens to correspond to the Pokedex number of Twinz and the item number of Mail.
- do some overworld movement to set address EB74 to D0 and EB26 to 30
- Take this Apple and the Berry from your starter to get seven items.
- execute a series of several Pokemon swaps with the select glitch: (3-1, 7-2, 7-2, 7-1, 7-1, 7-1, 7-1, take item, 8-2, 3-1)
The effect of these swaps is to reinterpret party data in various ways and accomplish the following:
1) partway through, a Mail item will be held by one of the pokemon, we take it for later.
2) at the end, your second pokemon will be a Twinz, and its held item will be an invalid item. (which invalid item depends on if we had the grass or water starter, both will work)
- open the trainer card, to set addresses EB5E-EB61 to opcodes that don't crash
- open Twinz's move list to set EB5B to C1 and EB5C to 02.
The above set of ram setup steps actually places a very tiny ACE payload in ram in the region near EA77. Next, take Twinz's invalid held item, and this code will execute. Its only effect will be to change the number of items in your bag from eight to a very large number (0x77) and then return without crashing. Notably this code will also not actually take the item away from Twinz, so we still have our entrypoint available to run more ACE later. More importantly, our new expanded pack size means that the select glitch will now let us reach and corrupt a vastly larger area of memory.
- Use the Mail item you obtained earlier, and enter any message. Whatever you enter is what will finally be executed as our ACE payload at the end of all this. Because my video is a TAS, I chose to write a bootstrap program for reading controller inputs. If trying to achieve RTA ACE, which is not difficult, you may prefer to come up with some other final payload.
- Give the mail to your starter pokemon.
- Use the select glitch to swap your starter with a Pokemon far out of bounds, specifically pokemon 0x67. The effect of this will be to copy the Mail text data to address EA80, which is conveniently right where our entrypoint takes us.
- Take the invalid item from Twinz again to trigger the full ACE payload from the mail. Depending on your payload, this is Mission Accomplished! In my case, though, the payload is a bootstrap that I use to construct a still larger payload, which provides the game a mock "ending" that Game Freak wouldn't program into the game for at least another year. :)
Although the video uses TAS levels of optimization, everything shown here is fully RTA viable. If you could send a note 23 years in the past to a kid in Japan, and nobody took the controller away from them once the screen started getting glitchy, you could really have some fun with the people back then. For perspective, this is a year before any of the Pokemon games or anime were even seen in the west.
Source for my payload:
github.com/MrCheeze/pokespaceworld-ace
Since it's been two years, I'll also relink the two videos this was following up on:
youtube.com/watch?v=qTfBpRrB37Q
youtube.com/watch?v=5Qop9TlZs2g
This project was completed in Sept. 2018, but I sat on it at the time due to not having the motivation to make a proper explanation video back then. But with the Gold/Silver prototypes having renewed relevance recently, it seems like as good a time as any to release this as it exists.
The most important thing in ACE is of course the entrypoint. Given how limited the demo boundaries are, it wasn't easy to find one, but it exists. Whenever you take a held item from a Pokemon the game runs some code to put it back in the bag. The code that runs depends on what pocket the item is assigned to. If you take an invalid item that doesn't have a pocket assigned, the game glitches and jumps to an address in RAM instead (address EA77 in echo ram, to be specific). This is one key piece of the puzzle.
The other key piece is the select glitch, which is documented on GlitchCity: glitchcity.info/wiki/Select_glitches_(Gold/Silver_Nintendo_Space_World_1997_demo)
Basically, if you have N items in your bag, it's possible to swap any Pokemon in your party with Pokemon slots up to #N. If N is more than 6, this lets you corrupt parts of memory other than party data. With a well chosen set of swaps, it's possible to use this to copy an ACE payload near EA77.
The overall route, then, goes like this:
- Start the demo. You will have 5 items to begin with. Also, you will be randomly assigned a starter, if it's grass or water you can continue, but reset if it's the fire starter.
- catch a Girafarig with a held Apple. (note that it only has a chance of carrying an Apple in the Gold non-debug build, which is the most recently updated of the four '97 builds)
- name the Girafarig C1 9E, which happens to correspond to the Pokedex number of Twinz and the item number of Mail.
- do some overworld movement to set address EB74 to D0 and EB26 to 30
- Take this Apple and the Berry from your starter to get seven items.
- execute a series of several Pokemon swaps with the select glitch: (3-1, 7-2, 7-2, 7-1, 7-1, 7-1, 7-1, take item, 8-2, 3-1)
The effect of these swaps is to reinterpret party data in various ways and accomplish the following:
1) partway through, a Mail item will be held by one of the pokemon, we take it for later.
2) at the end, your second pokemon will be a Twinz, and its held item will be an invalid item. (which invalid item depends on if we had the grass or water starter, both will work)
- open the trainer card, to set addresses EB5E-EB61 to opcodes that don't crash
- open Twinz's move list to set EB5B to C1 and EB5C to 02.
The above set of ram setup steps actually places a very tiny ACE payload in ram in the region near EA77. Next, take Twinz's invalid held item, and this code will execute. Its only effect will be to change the number of items in your bag from eight to a very large number (0x77) and then return without crashing. Notably this code will also not actually take the item away from Twinz, so we still have our entrypoint available to run more ACE later. More importantly, our new expanded pack size means that the select glitch will now let us reach and corrupt a vastly larger area of memory.
- Use the Mail item you obtained earlier, and enter any message. Whatever you enter is what will finally be executed as our ACE payload at the end of all this. Because my video is a TAS, I chose to write a bootstrap program for reading controller inputs. If trying to achieve RTA ACE, which is not difficult, you may prefer to come up with some other final payload.
- Give the mail to your starter pokemon.
- Use the select glitch to swap your starter with a Pokemon far out of bounds, specifically pokemon 0x67. The effect of this will be to copy the Mail text data to address EA80, which is conveniently right where our entrypoint takes us.
- Take the invalid item from Twinz again to trigger the full ACE payload from the mail. Depending on your payload, this is Mission Accomplished! In my case, though, the payload is a bootstrap that I use to construct a still larger payload, which provides the game a mock "ending" that Game Freak wouldn't program into the game for at least another year. :)
Although the video uses TAS levels of optimization, everything shown here is fully RTA viable. If you could send a note 23 years in the past to a kid in Japan, and nobody took the controller away from them once the screen started getting glitchy, you could really have some fun with the people back then. For perspective, this is a year before any of the Pokemon games or anime were even seen in the west.
Source for my payload:
github.com/MrCheeze/pokespaceworld-ace
Since it's been two years, I'll also relink the two videos this was following up on:
youtube.com/watch?v=qTfBpRrB37Q
youtube.com/watch?v=5Qop9TlZs2g

![Ocarina of Time - any% Slingshot Skip (TAS Only)
Since the discovery of the Kokiri credits warp, there have been two holy grails left for OoT any% speedruns: ocarina skip and slingshot skip. (Sword/shield/nuts cannot realistically ever be skipped.)
On Jan. 18, Jolin012 and r0bd0g found the first ocarina skip, but it was kinda slow, dependent on an RNG seed drop, and required calculating a new heap manip: https://www.youtube.com/watch?v=b45xe0GooZ4
On Jan. 30, before we had even worked out a new heap for the previous method, Blini found a new ocarina skip that suffered none of these issues: https://www.youtube.com/watch?v=hYXq5NgEWcI
So all that remained for any% to be solved is slingshot skip. The reason slingshot has been needed so far is this: Using SRM, we can make it so that the code intended to run a certain immobile rocks draw function instead jumps to elsewhere in memory. But via SRM alone, we can only jump to locations within the actor heap, not to truly manipulable locations such as filename. But slingshot seed rotation gave us one extremely manipulable 32 bit word on the heap, so we were able to use draw pointer SRM to jump to seed rotation, and from seed rotation to filename, and use filename to credits warp.
Eliminating slingshot from the run means either finding something else on the heap we can manipulate enough to form a jump to filename, or else coming up with a new ACE entrypoint other than draw pointer.
One candidate for this is short coordinates. Certain actors, such as deku nuts and spin magic, have their coordinates stored within them as short ints. In particular, their Y and Z coordinates form a single 32 bit word that we can use as an instruction for ACE purposes. Unfortunately were constrained by what Y and Z coordinates are actually achievable in Kokiri Forest, so we cant form a jump to filename instruction. One of the few meaningful instructions we can form is jr, meaning jump to the address currently located in some register. Taking a look at what addresses happen to be located in registers at this time (https://pastebin.com/PGc5f6aH), most of them dont seem to point to manipulable memory... with one notable exception. By some amazing freak coincidence, register $t3 JUST HAPPENS to be pointing exactly at controller 3 inputs in memory. Thats right, controller 3 is making a comeback with this strat. By inputting an exact input on controller 3 - including, most notably, a unit-exact joystick input - we can jump to filename and finally use the filename itself in order to trigger the credits warp, in the same manner as the previous strat.
So, the overall ACE flow goes like this:
Immobile rock draw function pointer (801F9004) - using SRM, we manip this to have a value of 801F8000, so that execution jumps there when we look at the rock.
Spin magic YZ position (801F8000) - climb the cliff and use the setup that I do to set its Y position to 0160-0x017F (decimal 352-383) and its Z position to XX[048C]8 (decimal 8+64*n). Anything satisfying these constraints will form the instruction jr $t3, which jumps us to the address already there for us in the register, which is 801C84E4.
Controller 3 (801C84E4) - Should have the inputs dup + cdown + (105,125) , which forms the instruction j 8011A5F4.
Filename (8011A5F4) - This filename uses the same code as in the previous strat: 3. dベNgべ which is 03EADFC8 A3B8CB53 which is jr $ra; sb $t8, 0xCB53($sp) which will set the next cutscene value to FFF8 on every other frame the kid rock draws, and then return.
Of these steps, only the need for an exact controller 3 joystick makes this whole strat a TAS one. But with this particular execution path, theres no way around that requirement. Ocarina of Time - any% Slingshot Skip (TAS Only)](https://i.ytimg.com/vi/mamKr3ITNaI/mqdefault.jpg)








