ATLAS ServerGrid.json Layout Guide
ATLAS runs multiple game server processes stitched together into a seamless ocean grid. Each process handles a map region — players sail across borders into adjacent cells without loading screens. This tool explains the architecture and generates a starter ServerGrid.json skeleton for simple private setups.
How the Grid Architecture Works
Grid Cells
Each cell is a separate ShooterGameServer process running its own map region. Players and ships seamlessly cross between cells.
Redis Backbone
Redis handles real-time inter-cell communication — passing player handoffs, ship transfers, and world state between server processes.
Home Server
One cell must be marked as the Home Server. This is where players first spawn and where certain global data is anchored.
For full grid editing, use the official desktop app
The ServerGridEditor by GrapeshotGames is the official tool for designing complex multi-cell grids with biomes, islands, and routes. This tool only generates starter JSON for simple 1×1 and 2×2 setups.
Grid Configuration
Grid Size
1×1 is the simplest private setup — one server process covers the full world.
Public IP that clients connect to for each cell.
Default: 7777. Each additional cell increments by 2.
Default: 27015. Each additional cell increments by 1.
Default: 127.0.0.1:6379. All server processes must be able to reach this Redis instance. For multi-machine setups, use the Redis host's LAN IP.
ServerGrid.json Skeleton
{
"RedisServerAddress": "127.0.0.1:6379",
"TotalGridsX": 1,
"TotalGridsY": 1,
"Servers": [
{
"ServerX": 0,
"ServerY": 0,
"IP": "YOUR_SERVER_IP",
"Port": 7777,
"QueryPort": 27015,
"IsHomeServer": true
}
]
}
This skeleton covers the cell-identification fields needed for basic multi-cell communication. Load it into the ServerGridEditor to add islands, biomes, and routes.
Place the completed ServerGrid.json in each cell's ShooterGame/Saved/ directory (or the path specified by -ServerGridFile).
Port Reference
| Service | Default Port | Notes |
|---|---|---|
| Game (UDP) | 7777 | Client connection port. Increment by 2 per additional cell. |
| Query (UDP) | 27015 | Steam server browser query port. Increment by 1 per additional cell. |
| RCON (TCP) | 27020 | Remote admin console. Optional — increment per cell. |
| Redis (TCP) | 6379 | Shared across all cells. Must be reachable by every server process. |
Run your own Atlas server.
Rent a private Atlas server on real hardware — full control-panel access, your mods, your configs, your rules. It's your server; run it your way.
Don't want to run it yourself? Our managed services & consulting team will set it up and keep it running for you — game servers, Windows, Linux, and cloud, from 10+ years of MSP work.