Tag: MinishCap

Zelda Day 2025

“Zelda Day” is a random thing over at Metafilter. One day long ago, on December 26th, there was a day in which three Legend-Of-Zelda-themed posts were made in one day. Since then I’ve commemorated the event by making another Legend of Zelda post on the same day each following year.

Here is this year’s post, but you don’t have to follow it because I’ve included the links in this post too.

They’re all videos this year. These first links are to videos by Skawo:

In Minish Cap, there are certain names you can’t put on your save file due to a checksum bug. (11 minutes) The same bug can result in a valid save file being declared corrupted:

I think I mentioned this one before, but again, in Ocarina of Time, if you go back the way you came during the event in Kakariko Village, the world will become a glitchy mess (7 minutes):

In early versions of Ocarina, holding down R while talking to King Zora when he gives you the Blue Tunic causes him to give you a different item instead (14 minutes):

Also in Ocarina of Time, in some areas there’s a mysterious square in the upper-left corner of the screen (6 minutes):

When fighting pairs of Stalfos enemies, the game starts to lag heavily when you defeat one of the two, before the other one is beaten (9 minutes):

Capsyst Animations made three fake commercials for early Zelda games, in the style of the evocative illustrations from the manual. There’s the original Zelda, Zelda II and Link to the Past (all 1 minute long):

And, finally, here are two strange commercials for the Zelda 1 on NES, the Zelda Rap, and whatever this is supposed to be (both ½ minutes):

Capcom’s Weird Save Data Checksum System In GBA Zeldas

Skawo reports on an odd bug in both the Capcom-made Gameboy Advance releases of Zelda games A Link to the Past and The Minish Cap. It’s explained, as is frequently the fashion, in a ten minute Youtube video, here:

The video’s a bit padded with injokes and gimmicks, but beneath it all the bug is really interesting. Many games have checks to ensure the validity of save data, but the developers of both games implemented theirs in an odd way, calculating a 16-bit checksum for the file data twice, once by adding and once by subtracting, saving them both, and them when the File Select screen is setting up adding them to each other and checking for zero with the negative bit set (the high-order bit). It usually works, except when the checksum is exactly zero, which happens one in 65,536 times.

When that occurs, the total will be zero without the negative sign, which will be detected falsely as corrupted save data. As luck would have it, naming your character “God” in the European version of GBA Link to the Past will trigger the bug, and make it so you can’t create the file. But the 1-in-65536 chance comes up every time you save and exit. (The file check is made upon loading the File Select screen, so just saving with a checksum of 0 won’t trigger it; if the player saves later in the same play session, non-zero checksums will be written over the bad ones.)

1-in-65536 is a rare event, but it’s not extremely rare, and it’s absolutely the case that over the years many players have had their games declared corrupted and made unloadable. If a player saves their game, say, 20 times through a playthrough, then that’s about a 1-in-3250 chance of losing all their progress, and both games sold much more than 3,250 copies.

Skawo demonstrates the bug in action in The Minish Cap here, in the peocess responding to some naysayers (10 minutes):