Uploaded April 2017 | Updated November 2026, 3 hours ago
This glitch exploits the owl save system to let us start the game with full rupees.
On the file select screen, some addresses from the 2nd owl save are loaded into memory. Not all of these are wiped when a normal save is started from file 1, allowing certain things to carry over even into a new file. This shows the most practical application of this glitch, which is carrying over the rupee accumulator value. After withdrawing a large number of rupees, the game places them in an 'accumulator' which decreases as they are added to your wallet. This is one of the addresses that carries over, so by having a wallet that's still filling up as I owl save, every file I load in slot 1 will receive those rupees.
Some of the other addresses that carry over include rock sirloin and curse timers (shown here youtube.com/watch?v=2dl1YsjHkyA). Also, Keeta found a way to start cycles on 0th day with this glitch (youtube.com/watch?v=pN-3Ezzs24Y).
It seems that the addresses affected are between the checksum at 801F067A and the save file identifier at 801F3310 (which marks the end of owl save data). Curiously, the addresses in event_inf don't seem to carry over unless the cycle is started at an owl statue (via this sort of method youtube.com/watch?v=-CbSIpjuzXQ).
This glitch exploits the owl save system to let us start the game with full rupees.
On the file select screen, some addresses from the 2nd owl save are loaded into memory. Not all of these are wiped when a normal save is started from file 1, allowing certain things to carry over even into a new file. This shows the most practical application of this glitch, which is carrying over the rupee accumulator value. After withdrawing a large number of rupees, the game places them in an 'accumulator' which decreases as they are added to your wallet. This is one of the addresses that carries over, so by having a wallet that's still filling up as I owl save, every file I load in slot 1 will receive those rupees.
Some of the other addresses that carry over include rock sirloin and curse timers (shown here youtube.com/watch?v=2dl1YsjHkyA). Also, Keeta found a way to start cycles on 0th day with this glitch (youtube.com/watch?v=pN-3Ezzs24Y).
It seems that the addresses affected are between the checksum at 801F067A and the save file identifier at 801F3310 (which marks the end of owl save data). Curiously, the addresses in event_inf don't seem to carry over unless the cycle is started at an owl statue (via this sort of method youtube.com/watch?v=-CbSIpjuzXQ).










