Uploaded February 2020 | Updated November 2026, 2 days ago
Although a slingshot skip has already been found, the original can only be done by measuring out an inhumanly precise joystick value before the run. It also requires climbing the cliff to lost woods which is slow. This new technique doesn't use controller 3 at all, and skips the slow cliff climb. This comes at a cost however: this method requires three exact-angle setups, which have not been found yet. If these setups are found and are sufficiently fast, sub 8 speedruns are likely possible with this method.
The ACE code path is rather different from what we've been using up until now. Instead of SRMing an actor instance's draw pointer, we SRM actual overlay code to change a branch instruction to point into Link's instance (originally proposed by Jolin). Inside Link's instance, there is a fully manipulable 32 bit word, discovered by Seedborn, that contains link's "movement angle" (roughly the same thing as standing angle), and his "target angle" (the last angle Link got locked to from pressing Z or charging a spin swing). Using this we can jump all the way to filename. Filename loads register $v0 with a pointer to the value that stores what cutscene to plays next, and then jumps to some code from the Gossip Stone overlay that adds 1 to whatever $v0 points to. If we execute this filename 9 times, the next cutscene value will be FFF8, which makes it so that entering house of twins will play the ending sequence.
Notes:
- filename 0807B897 27A2C94A (87Nジほブeぞ)
- collect all permanent rupees in kokiri forest
- collect two random green rupee drops to skip mido chests
- collect grassy wonderitem after exiting shop so it won't cause crashes later
- kokiri to deku with mido visible and sword charged, deku to kokiri
- kokiri to deku with mido visible, deku to kokiri
- kokiri to deku with mido hidden, deku to kokiri
- kokiri todeku with mido visible, return a, deku to kokiri
- it's sometimes necessary to make sure the third deku baba isn't culled during the deku to kokiri transitions
- during WWT, don't let sign heal before rocks load
- pick up rock #6 of 8 (the one at 801F7310)
- need to get an angle between 8F7A and 8FA5 for rock drop
- need to charge a spin with angle 697D to set target angle (can't just press Z because walking while talking disables it)
- the game will crash if the square platforms wonderitem runs its update function, until the angle setup is complete
- need to get a movement angle of exactly 0804 while the square platforms wonderitem runs its update function
- allow the wonderitem to run its update function for exactly 9 frames
- go into house of twins
Obsoleting the exact-controller-3 method has been a high priority for me since its discovery, but finding a viable way to do it has been surprisingly difficult. Many pieces were known, but it took Seedborn's discovery and a reanalysis of all the loaded code to get anything viable. Extra shoutouts to Savestate who has been heavily involved in the ACE research and discussion for branch-instruction-based methods. We're not out of the woods yet, though, as long as no RTA setup yet exists.
Although a slingshot skip has already been found, the original can only be done by measuring out an inhumanly precise joystick value before the run. It also requires climbing the cliff to lost woods which is slow. This new technique doesn't use controller 3 at all, and skips the slow cliff climb. This comes at a cost however: this method requires three exact-angle setups, which have not been found yet. If these setups are found and are sufficiently fast, sub 8 speedruns are likely possible with this method.
The ACE code path is rather different from what we've been using up until now. Instead of SRMing an actor instance's draw pointer, we SRM actual overlay code to change a branch instruction to point into Link's instance (originally proposed by Jolin). Inside Link's instance, there is a fully manipulable 32 bit word, discovered by Seedborn, that contains link's "movement angle" (roughly the same thing as standing angle), and his "target angle" (the last angle Link got locked to from pressing Z or charging a spin swing). Using this we can jump all the way to filename. Filename loads register $v0 with a pointer to the value that stores what cutscene to plays next, and then jumps to some code from the Gossip Stone overlay that adds 1 to whatever $v0 points to. If we execute this filename 9 times, the next cutscene value will be FFF8, which makes it so that entering house of twins will play the ending sequence.
Notes:
- filename 0807B897 27A2C94A (87Nジほブeぞ)
- collect all permanent rupees in kokiri forest
- collect two random green rupee drops to skip mido chests
- collect grassy wonderitem after exiting shop so it won't cause crashes later
- kokiri to deku with mido visible and sword charged, deku to kokiri
- kokiri to deku with mido visible, deku to kokiri
- kokiri to deku with mido hidden, deku to kokiri
- kokiri todeku with mido visible, return a, deku to kokiri
- it's sometimes necessary to make sure the third deku baba isn't culled during the deku to kokiri transitions
- during WWT, don't let sign heal before rocks load
- pick up rock #6 of 8 (the one at 801F7310)
- need to get an angle between 8F7A and 8FA5 for rock drop
- need to charge a spin with angle 697D to set target angle (can't just press Z because walking while talking disables it)
- the game will crash if the square platforms wonderitem runs its update function, until the angle setup is complete
- need to get a movement angle of exactly 0804 while the square platforms wonderitem runs its update function
- allow the wonderitem to run its update function for exactly 9 frames
- go into house of twins
Obsoleting the exact-controller-3 method has been a high priority for me since its discovery, but finding a viable way to do it has been surprisingly difficult. Many pieces were known, but it took Seedborn's discovery and a reanalysis of all the loaded code to get anything viable. Extra shoutouts to Savestate who has been heavily involved in the ACE research and discussion for branch-instruction-based methods. We're not out of the woods yet, though, as long as no RTA setup yet exists.










