Some of these unused levels appear to be simple test maps, while others hint at more fleshed-out ideas. A notable revelation was that the file for Wet-Dry World was named "11ZLDCITY.bin," confirming the long-held theory that the level was built upon geometry originally designed for a beta Zelda 64 town.

A strange, spherical robotic enemy with small legs. Code chunks suggest the Moto would chase Mario, pick him up, and throw him across the stage, much like the Chuckya enemy does in the final game.

Should we analyze how fans used these assets to create ?

This is a fan favorite because it implies Super Mario 64 was almost a survival-horror platformer for a brief moment in development.

, including medium and low-poly versions. This confirmed Shigeru Miyamoto's statements that was intended for a cut multiplayer mode .

: A round, bullying bully-variant enemy designed to pick Mario up and throw him off ledges.

The retail version of Super Mario 64 opted for a bright, high-contrast color palette to accommodate the blurry output of 1990s CRT televisions. The beta assets, however, point to a much moodier, atmospheric experience.

Several fully functional enemies were left on the cutting room floor, surviving only as complete code packages and asset textures within the game's repository.

Note: While the Gigaleak assets are public domain in terms of data preservation, Nintendo actively takes down rom sites hosting the raw dumps. Always preserve legally via archival collections, not commercial piracy.

Before we discuss specific files, we must acknowledge the source. The single best collection of beta assets comes from the .

Several enemies in the final game look vastly different from their terrifying or strange beta counterparts. The asset leaks gave fans a look at what could have been.

Since TPP is open source, accessing it requires compiling the source code into a playable ROM. The official GitHub repository provides detailed instructions. The process is technical but well-documented, involving either a Docker environment or a native Linux/WSL setup. To legally build the ROM, you must supply your own legally obtained Japanese base ROM, from which the tool extracts base assets before applying the new beta content.