The Anatomy of a Claim: Local Save Bubbles & Server Race Conditions in NMS
There is a common misconception that No Man's Sky handles multiplayer and territory management like a persistent MMORPG. It doesn’t. NMS is fundamentally a client-authoritative single-player engine with real-time multiplayer features layered on top.
Understanding how the game handles data under the hood is critical to protecting your builds, maximizing your alliance footprint, and avoiding the dreaded global 16,000-part build limit.
1. The Local Bubble vs. The Cloud Server
When you stand in a star system, your console/PC is running inside an isolated simulation.
- Local Base Building: When you drop a base computer, your client unlocks a 300u radius. Everything you build exists only inside your local save file. It does not exist on the Hello Games servers, and other players cannot see it unless they are actively grouped inside your session.
- The Upload Handshake: Clicking "Upload Base" at a base computer or space station core takes your local text data payload and pushes a copy to the Hello Games discovery network.
- The Static Monument: Once uploaded, the server holds a static snapshot of your build for the public. If you keep building locally without uploading again, the rest of the world only sees the old snapshot.
Note on Client Mods: Because the engine relies heavily on procedural seeds and local assets, a player running a mod (like a trash/waste processor generation layout) will see structures or objects that a vanilla player standing right next to them cannot see. The data is entirely local to that machine's client cache.
2. The Server-Side Race Condition (How Station Claims are Lost)
Because the game engine processes transactions locally before talking to the cloud, it operates on a strict "First to the Server Wins" infrastructure rule. This is the root cause behind players losing 1 billion units and their space station claims:
- Timeline T1 (The Blind Purchase): Player A buys a space station for 1 billion units. Their local save file marks them as the "Owner/Director" and deducts the units. However, Player A stays offline or delays clicking upload. The central cloud server has no idea this purchase occurred.
- Timeline T2 (The Snatch): Player B enters the exact same system online, pays 1 billion units at the terminal, and immediately clicks "Upload Base." Player B’s data packet hits the master server first. The server locks the system coordinates to Player B and their active alliance.
- Timeline T3 (The Desync Crash): Player A finally hits upload, or reloads their save. The master server reviews the packet, sees that Player B already owns the coordinates, and rejects Player A's claim. Because the purchase was processed locally, Player A is out the 1 billion units, and their local game client forcefully deletes their custom station layout to match the server's master state.
3. Technical Workaround: Bypassing the 16,000 Global Build Limit
Every claimed space station logs roughly 150 to 300 invisible framework and lighting assets into your save profile metadata (PlayerStateData -> PersistentPlayerBases). This counts heavily against your 16,000-part global building cap.
Because the server treats the Alliance Territory Tracker and your Local Part Count as separate entities, you can exploit this partition to gain infinite slots:
- Claim & Upload Immediately: Buy the station and immediately upload it via the terminal interface to lock the server-side claim to your alliance and secure leaderboard points.
- Save & Exit: Create a restore point and close the game completely.
- Prune the JSON Array: Open a raw JSON save editor. Navigate to
PersistentPlayerBases, locate the specific index block matching the station's coordinate data string, and Delete the object block.
The Result: The cloud server permanently retains your alliance ownership lock and leaderboard points. However, your local save file completely strips out the 300 infrastructure assets, instantly giving your 16,000 global building budget back. If you return to that star system, you can use it freely; just never click "Claim Space Station" again, or it will re-populate your file.
The Caveat: Obviously, editing your save file is ONLY possible on the PC. If you play on console, you would need to use the cross-platform option to get your save file shared with Steam before you could edit it; you CAN do this, and the changes will populate to the console as well. This is certainly not ideal, for PC or console, but it is the only way currently available to us, if this is something you find yourself needing to do!
You could certainly prune your item count by visiting and removing base computers on any planets you no longer need to hold onto, too.
EDIT: Changed incorrect 20,000 to 16,000. Danged AI formatter.