How ISZ Works

A long diagnostic of the inner working of Ice Station Z.

Rendering Land Mass
So the land in Ice Station Z are called tiles. Which can be rendered and de-rendered with ease, due to some advanced coding techniques and how the 3ds renders data. Ice Station Z by itself would take over 2 GBs of RAM to render the whole map. Yeah, it's really massive. So Wobbly Tooth made a really optimized system by only spawning in one tile at a time. If this seems complicated right now, it's because it actually is. You see, whenever a player walks onto, I don't know, let us say, Greybase. That is now known as the primary tile. And Greybase's tile number is Tile006_005.obj. Which is rendered in whenever you walk onto it. Which is why some people fall through the map on hills, it's because they're crossing the X, Y, & Z axis all at once which the game can't comprehend. In this bug you fall through the map because the game cannot calculate what tile you're on, so it takes away all tiles assuming you're no longer playing. (You can test this out by using a debugger such as CTRPF or hardware debugging boards).

PVP & Hosting

So now you may be asking yourself: "How does online work?" That's a valid claim to make. Have you ever noticed that during multiplayer if you're PVP'ing at Greybase with multiple people online at the same location, That it drops to 30 FPS or even 15 FPS at times? Well this is also a bug, since the game is loading multiple people, It will drop the FPS to stop overheating of the 3DS or the game crashing. This is one of the only games that does that to stop that from happening, yet its a bug in online. After analyzing that for a month, I saw something big. It was about the hosted 3DS. Since the servers are not hosted by Wobbly Tooth on any web hosted server, you can always play the game. Meaning that the host 3DS when you host a server becomes a Linux code executor, meaning you could run unsigned code by tricking the 3DS into reading that on an unmodded 3DS. So if I were to use an exploit such as Pichaxx. And have a hacked 3DS running CFW, you could trick other 3DS's into reading that code by telling them to search for the save file. That would be replaced by another file and run homebrew from there.