How to Make an ATLAS Server: Step-by-Step Setup Guide

To make an ATLAS dedicated server, install the Windows server files with SteamCMD, design a grid in GrapeshotGames’ ServerGridEditor, create one launch script for each grid cell, run Redis, forward the generated ports, and connect through Steam. A one-cell server is the simplest private option; the default 2×2 layout uses four server processes and four mapped areas. Self-hosting gives you control over files and settings but requires a continuously running Windows machine and network administration. Managed hosting removes much of that work for a recurring fee. The guide below covers both paths, with warnings about historical hardware figures, changing port defaults, and the game’s uncertain long-term support.

What do you need before making an ATLAS server?

Decide first whether the server is for a small private group or a larger persistent world. Each ATLAS grid cell is a separate server process, so map size directly affects CPU, memory, ports, administration and backup work. A one-cell installation is a practical starting point; the commonly documented default 2×2 map requires four server areas.

Self-hosting prerequisites

The Survival Servers setup guide lists a 64-bit Windows environment, SteamCMD, the Visual C++ Redistributable for Visual Studio 2015, and enough disk space and RAM for the selected grid. Those figures are historical guidance rather than a current official requirements matrix. No current official 2026 CPU, memory or storage table is established, so monitor the machine under your intended player load instead of treating an old minimum as a guarantee.

• A continuously running 64-bit Windows computer or dedicated machine.
• SteamCMD and a writable server directory.
• Visual C++ Redistributable for Visual Studio 2015.
• A stable private LAN address for port forwarding.
• Administrative access to the Windows firewall and internet router.
• Separate free ports for every grid cell, plus Redis and any RCON service you choose to expose.
• A backup location for ServerGrid.json, map images, configuration files and saved data.

Community hardware baseline

The community wiki gives an approximate one-grid baseline of 4 GB of RAM, two CPU cores and about 20 GB of storage. It labels these numbers as community-provided, not official support requirements; a multi-cell world or a busy player population can require substantially more headroom.

Self-hosting or managed hosting?

Option	What you control	What you must operate	Best fit
Self-hosted	Server files, grid layout, ports, backups, launch arguments and updates	Windows machine, firewall and router rules, Redis, restarts, troubleshooting and backups	Owners who want maximum control and are comfortable administering Windows
Managed host	Game settings and uploaded grid files through a provider panel	Recurring hosting charges, provider limits and the provider’s availability	Groups that want a persistent server without maintaining a home machine

Managed panels can provide restarts, map uploads and mod management. Nitrado’s documentation describes a main server, expansion servers and home servers, and explains uploading ServerGrid.json and map images. Availability changes: 4Netplayers currently says ATLAS is not in its active portfolio, although it discusses possible reactivation or custom solutions. Check a provider’s current ATLAS support before paying.

Nitrado’s guide also warns that ATLAS has not received a developer update in more than three years. That is a date-qualified statement from the guide, not a verified live 2026 release-status claim; consider population and long-term support before investing in a large grid.

How do you install the ATLAS dedicated-server files with SteamCMD?

Install SteamCMD in its own folder, create a separate destination for the game server, then use SteamCMD to download or validate the dedicated-server app.

1. Create a directory such as C:SteamCMD for SteamCMD and another such as C:atlasserver for ATLAS.
2. Place the SteamCMD executable in its own folder and create a batch file that runs it.
3. Use the documented anonymous installation command:
   steamcmd +login anonymous +force_install_dir C:atlasserver +app_update 1006030 validate +exit
4. Replace C:atlasserver with your actual installation path. Keep the path consistent in every later script.
5. Wait for SteamCMD to finish downloading and validating the files. Run the same command again when you need to repair or update the installation.

The app ID in the command is the community-documented ATLAS dedicated-server app. SteamCMD output should end without download or validation errors before you continue.

How do you create an ATLAS server grid?

Use GrapeshotGames’ ServerGridEditor to define the cells, coordinates, names, IP addresses and ports that the game server processes will use. The editor exports ServerGrid.json and map images; both are part of the grid configuration.

Design the cells before players build

1. Download and open ServerGridEditor, or create a new project.
2. Set a recognizable server name and, if wanted, a password.
3. Add the number of cells you intend to run. A one-cell private server needs one process; a 2×2 layout needs four.
4. Assign each cell its grid coordinates, IP address and unique ports.
5. Choose islands and other map content for each cell, checking that the layout is usable before anyone starts building.
6. Export the project to generate ServerGrid.json and the associated map images.

Moving islands after construction is risky: Nitrado warns that structures and ships can be left behind or stranded. Save a backup before every grid edit and prefer changing an unused area rather than relocating a live cell.

Copy the exported files

For a local installation, copy the exported grid files into the server’s ShooterGame directory under your ATLAS installation. For a managed host, upload ServerGrid.json and the map images through the provider’s configuration interface. The exact panel labels vary, so use the host’s current ATLAS upload instructions.

How do you write launch scripts for each grid cell?

Every cell needs its own batch file. The coordinates, save-directory name and ports in the script must agree with the corresponding entry in ServerGrid.json; duplicate ports or mismatched coordinates prevent cells from starting or communicating correctly.

Documented launch pattern

Use this pattern as a template, replacing every placeholder:

ShooterGameServer.exe Ocean?ServerX=0?ServerY=0?AltSaveDirectoryName=00?ServerAdminPassword=<ADMIN_PASSWORD>?MaxPlayers=30?ReservedPlayerSlots=25?QueryPort=<QUERY_PORT>?Port=<GAME_PORT>?SeamlessIP=<PUBLIC_IP> -log -server -NoBattlEye

• ServerX and ServerY identify the cell’s grid coordinates.
• AltSaveDirectoryName keeps each cell’s saved data distinct; use a different value per cell.
• ServerAdminPassword is the administrator credential. Do not publish it in a forum or share the batch file publicly.
• MaxPlayers and ReservedPlayerSlots set the documented player and reserved-slot values in this example; change them to match your plan.
• QueryPort is used for server discovery, while Port is the game connection port.
• SeamlessIP should be the public address used for travel between cells.
• -log -server starts a dedicated logged process. -NoBattlEye disables BattlEye in the documented pattern; use that only if it matches your server policy.

Make one script per cell

For a 2×2 grid, create four scripts with coordinates such as (0,0), (1,0), (0,1) and (1,1). Give every script a unique game port, query port and seamless-travel port, and use a unique save-directory name. Do not copy the same numbers into every file.

How do you run Redis and start a local grid?

Community setup material instructs self-hosters to start the Redis executable before launching the game-server processes. Redis provides the local database service that the grid expects.

1. Open a command prompt in the Redis directory and start the Redis executable using the configuration supplied with your installation.
2. Leave Redis running while the ATLAS cells are online. Keeping it on the same machine avoids the networking and latency complications of a separate database host.
3. Start each cell’s batch file after Redis is ready.
4. Keep the log windows open during the first launch so you can see port conflicts, missing files or database connection errors.

If a cell exits immediately, stop the other processes and check that its coordinates, save directory and ports are unique and that Redis is still listening. A successful launch should progress through normal startup messages without repeated database or bind errors.

Which firewall and router ports must you open?

Allow the game, query, seamless-travel and any RCON ports assigned to the grid in Windows Firewall, then forward those ports from the router to the server’s private address. The examples in the setup material include game/query families such as 5761/57561 and seamless ports in the 27000 range, but those are examples, not universal defaults.

1. Record the exact ports generated or selected for every cell in a small configuration table.
2. Create inbound Windows Firewall rules for the required TCP/UDP protocols used by your installation and its management services.
3. Forward the same ports on the router to the machine’s fixed private IP address.
4. Do not expose Redis to the public internet; keep it local unless you understand the security and latency implications of separating it.
5. Restart the affected cell after changing a port, then inspect its log for a successful bind.

Port forwarding to the wrong private address is a common failure after a router reboot. Reserve the server machine’s LAN address in the router or configure a static address so the forwarding rule does not silently point to another device.

How do players connect to a self-hosted ATLAS server?

Players can add the server in Steam’s View → Servers → Favorites interface or launch the game with +connect <IP>:<PORT>.

1. Give players the public IP address and the cell’s game connection port, not the private LAN address.
2. In Steam’s server browser, enter the address and query port used by the cell.
3. If the favorite does not appear, try the query port plus one. Nitrado documents this convention with an example of query port 27015 being entered as 27016.
4. Alternatively, close the game, add +connect <IP>:<PORT> to its launch options, and start it.

Discovery depends on the query rule being open and the server process responding. A server can be running correctly yet remain invisible if the router forwards only the game port, the wrong protocol, or the wrong private address.

How do you set up ATLAS on a managed host?

Choose a provider that explicitly supports ATLAS, select the number of server areas you need, and use its panel to upload the grid and map images. The provider handles the machine, operating system and much of the restart work, but you still need to understand coordinates, ports and backups.

1. Confirm current ATLAS availability, supported grid size, player limits, mod policy and backup features before ordering.
2. Create the server instance and note the public address and panel-assigned ports.
3. Build or edit the grid in ServerGridEditor, then upload ServerGrid.json and all exported map images through the panel.
4. Set administrator credentials and gameplay options in the provider’s configuration fields.
5. Restart the server from the panel and inspect its console or log output for configuration errors.
6. Connect through Steam using the host’s address and query information.

Managed hosting reduces router work and keeps the machine online, but provider-dependent file paths, port assignments and panel labels can change. Download your grid and save backups outside the provider account so a cancellation or service change does not remove your only copy.

What should you back up and monitor?

Back up the grid definition before editing and preserve saved data for every cell. A grid file is not a substitute for the world saves: restoring only ServerGrid.json can leave players’ structures and ships unavailable.

• Keep dated copies of ServerGrid.json and the exported map images.
• Back up each cell’s saved data and configuration before updates or map changes.
• Record the public IP, private IP, coordinates, query port, game port, seamless port and save-directory name for every cell.
• Watch CPU, memory, disk space and log growth as more players join; the community baseline is not a performance guarantee.
• Test a restore on a spare directory before making a major live-grid change.

What are the most common setup failures?

SteamCMD downloads but the server will not launch

Run the installation command again with validate, verify the Visual C++ Redistributable is installed, and confirm that each batch file points to the actual ShooterGameServer.exe location.

One cell starts while another fails

Compare the failed script with ServerGrid.json. Duplicate query, game or seamless ports, duplicate save-directory names, invalid coordinates and a typo in the public IP are the usual configuration differences to check first.

The process starts but nobody can join

Check Windows Firewall and router forwarding, then test the public address from outside the hosting LAN. Make sure players use the game port for direct connection and the correct query value for Steam Favorites; the documented plus-one query convention may be required.

Cells cannot exchange data

Confirm Redis was started before the game processes and remains running. Keep Redis local unless you have deliberately configured a separate host and understand the resulting network path.

Players lose access after a map edit

Stop the server, restore the last known-good grid and saved-data backups, and avoid moving occupied islands until you have a tested migration plan. Changing a live cell can strand structures or ships.

Is making an ATLAS server worth it?

It is worthwhile for a small group that wants control over a private world and is prepared to maintain Windows, Redis, ports and backups. Renting is easier when uptime and administration matter more than file-level control. For a large grid, weigh the extra processes and operational burden against the game’s uncertain population and support outlook before committing.

Frequently Asked Questions

Can I start with only one ATLAS grid cell?

Yes. A one-cell server is the least complicated way to verify SteamCMD, Redis, firewall rules and the launch script before expanding. Add cells only after the first process is stable, then assign new coordinates, save directories and ports rather than cloning the original values.

Do players need the server’s public IP or its local address?

Players outside your home network need the router’s public address and the forwarded game port. The private address belongs in the router’s forwarding rule and should not be distributed as the internet connection address.

What happens if the hosting provider stops offering ATLAS?

Your portable assets are the grid definition, map images, saved data and documented launch settings. Keep those backups off-platform so you can move to another Windows machine or a provider that still supports the game.

Should Redis run on a separate computer?

Not for a normal self-hosted installation. The community setup guidance starts Redis locally; separating it introduces network and latency considerations that are unnecessary unless you have a specific, tested reason to do so.