Thread by @OatmealDome

[Splatoon 3]

Here’s how the resource size table leak worked. (see my past RTs for the actual leak) 🧵

Also, a quick and non-spoilery note about Side Order at the end.

Full credits go to @DiamCreeper23, @ashbinary_, @heyheymasa, @asasasa98765, @Coxxs, Watertoon, and @LeanYoshi.

There is something called the “resource size table”. It lists how much RAM each file consumes when it is loaded. This allows the engine to be more efficient with RAM management.

Prior to 5.0.0, the table actually contained info for files from Nintendo’s internal dev build.

So… Why don’t we just make up some file names and see if they exist in the dev build?

Example: we know that the Grizzco Blaster’s file is named “Blaster_Bear”.

If we check the table for the name “Roller_Bear”… Yep, the file exists.

There is a Grizzco Roller in the dev build.

Because the table only contains file *names*, it is not possible to actually open the files and see what’s inside.

(Note: I have simplified this explanation. For example, the table actually contains CRC32 checksums of the file names, not the actual names themselves.)

Unsurprisingly, the dev build has files for Side Order in it.

Because the resource table leak is now public info, it’s possible that someone will find Side Order file names and post about it online.

Of course, we can’t open the files. But file names can be spoilery already.

So, if you’re worried about Side Order spoilers, consider implementing anti-spoiler precautions (for example, muting keywords). At this point, it’s only a matter of time.

Note that I will NOT be posting any information about Side Order until after it is officially released.