Nintendo's future president helped untangle Pokémon's code.

How Iwata Made Room for Kanto

When Pokémon Gold and Silver were being built for the Game Boy, the developers wanted the adventure to continue after its new Johto region. The game’s second half would let players return to Kanto, the region from Red and Blue—a far more ambitious plan than simply adding another map. The obstacle was the cartridge: it had a fixed amount of storage, and the new game’s data was already competing for space.

Satoru Iwata, then president of HAL Laboratory and an experienced programmer, helped Game Freak tackle that limit. He developed tools and compression methods that made the game’s data take up less room. The key was not conjuring extra memory, but finding a more compact way to store what the game needed. That freed enough space for Kanto to be included.

Compression Is a Tradeoff, Not a Cleanup Button

Compression works by encoding data more efficiently. For example, repeated patterns can sometimes be represented once and referred to again instead of being stored over and over. A game must also be able to decode that information as it runs, so the savings come with technical work: developers need to organize the data, build tools to handle it, and make sure the game can still load and use it correctly.

That distinction matters because the famous story is often retold as Iwata rescuing a disastrously written game by tidying up its code. The more grounded point is that he helped solve a storage problem. There is no need to assume the original games were simply a mess: fitting a second region meant squeezing a large amount of additional content into a small, fixed cartridge budget.

A Return That Changed the Scale of the Sequel

Kanto gave players a substantial postgame journey through familiar towns and routes, making Gold and Silver feel unusually expansive for a handheld sequel. Its inclusion was not inevitable; it depended on making the data fit and then building a game that could use it.

The memorable lesson is less that a coding miracle can rescue any project than that a clever technical solution can change what a game is able to contain. In this case, better compression helped turn a planned sequel into an adventure with a whole earlier region waiting after the new one.