This guide covers how to set up your Foundry dedicated server on Legion Hosting, configure startup variables, edit the server settings file, set up world generation, connect to your server, and manage saves and backups. Foundry is a voxel-based factory-building game where players mine resources, build automated production lines, and expand massive factories across a procedurally generated world. For admin controls, player management, and troubleshooting, see Foundry Admin and Server Management.

1. First Start

1. Log in to GPanel and select your Foundry server.
2. Go to the Startup tab and review the configurable variables (see the table in Section 2).
3. Set SERVER_NAME to a name for your server. This appears in the Steam server browser.
4. Set SRV_PW if you want to restrict access. Leave it blank for a public server.
5. Optionally set a MAP_SEED to control world generation. Leave blank for a random seed.
6. Return to the Console tab and click Start.
7. Wait for the console to confirm the server has started. The first launch may take a couple of minutes as the server generates the world and creates initial configuration files.

2. GPanel Startup Variables

The following variables are available in the GPanel Startup tab. These are passed to the server on each start.

3. Server Configuration File

For advanced settings beyond what the startup variables offer, you can edit the server configuration file directly. Stop your server before making changes.

File Location

App.cfg

Open this file using the Files tab in GPanel or connect via SFTP. The file uses a simple key=value format with one setting per line. If the file does not exist, start and stop the server once to generate it.

Key Settings in App.cfg

Example Configuration

server_name=My Legion Factory
server_password=
server_world_name=MyFoundry
server_max_players=16
server_is_public=true
server_port=3724
server_query_port=27015
map_seed=48293175
autosave_interval=300
pause_server_when_empty=true

4. World Generation

Foundry uses procedural world generation to create its voxel terrain. The world is generated from a seed number, which determines the layout of terrain, ore deposits, and biomes.

Map Seed

• Set the map_seed value in App.cfg or the MAP_SEED startup variable to any integer.
• Using the same seed always produces the same world layout, which is useful if you want to share a specific world with others or recreate a world after a reset.
• Leave the seed blank or omit it entirely to let the server generate a random world.
• The seed only affects initial world generation. Changing the seed on an existing world has no effect -- you must create a new world (change server_world_name) for a new seed to take effect.

World Name and Multiple Worlds

The server_world_name setting determines which save folder the server uses. You can maintain multiple worlds by switching between different world names:

• Each unique server_world_name creates a separate world with its own save data, factory state, and player progress.
• To switch worlds, stop the server, change the server_world_name in App.cfg, and restart.
• Previous worlds are preserved and can be loaded again by switching back to their name.

Pause When Empty

The pause_server_when_empty option controls whether your factory continues operating when no players are online:

• true (default) -- The world pauses when all players disconnect. Factories stop producing, resources stop being consumed. Good for saving server resources and keeping the game state predictable.
• false -- The factory keeps running 24/7. Production lines continue, resources accumulate, and the world progresses even when nobody is playing. Can increase server resource usage.

5. How to Connect

Option A -- Steam Server Browser

1. Launch Foundry.
2. From the main menu, select Multiplayer.
3. Click Join Game to open the server browser.
4. Use the search bar to find your server by name.
5. Select your server and click Join. Enter the server password if one is set.

Option B -- Direct Connect

1. Launch Foundry.
2. From the main menu, select Multiplayer.
3. Choose the Direct Connect option.
4. Enter your server's IP address and port from GPanel's Network tab:

   <your-server-ip>:<port>

5. Enter the server password if prompted and click Connect.

6. Save Management

Auto-Save

The server auto-saves at the interval specified by autosave_interval in App.cfg (default: every 300 seconds / 5 minutes). Foundry auto-saves are non-intrusive and do not cause noticeable lag for most factory sizes.

Save File Location

Save files are stored on the server at the path specified by server_persistent_data_override_folder in App.cfg. The default path is:

serverfiles/

This directory contains the full world state including terrain modifications, placed structures, factory machines, conveyor belts, and player inventories.

Manual Backups via SFTP

1. Stop the server from GPanel to ensure all data is written to disk.
2. Connect to your server via SFTP. See How to Upload Files via SFTP for instructions.
3. Download the entire save directory for your world (e.g., serverfiles/).
4. Store the backup in a safe location on your computer.

Restoring a Save

1. Stop the server from GPanel.
2. Connect via SFTP and navigate to the serverfiles/ directory.
3. Upload your backed-up world directory, replacing the existing one.
4. Ensure the folder name matches the server_world_name in App.cfg.
5. Start the server from GPanel. The server will load the restored save.

7. Performance Tips

Foundry is a factory-building game, and server performance is directly affected by factory complexity. Keep these tips in mind as your factory grows:

• Factory complexity: Large numbers of machines, conveyor belts, and logistics networks increase server tick load. If you notice lag, consider consolidating or optimizing production chains.
• Chunk loading: The server processes all loaded chunks. More active factory areas spread across the map means more chunks to simulate. Keeping your factory compact reduces the number of chunks the server must track.
• Player count: More connected players means more chunks loaded around each player. If performance degrades with many players, consider reducing server_max_players.
• Auto-save frequency: Very frequent auto-saves (under 60 seconds) on large worlds can cause periodic hitches. The default 300 seconds is usually fine, but you can increase it if needed.
• Pause when empty: Enabling pause_server_when_empty=true prevents unnecessary simulation when nobody is playing, which helps maintain consistent performance during active play sessions.

Related Articles

• Foundry Admin and Server Management
• How to Find Your Server IP and Port
• How to Upload Files via SFTP
• Server Startup Guide

Need Help?

If you run into issues with your Foundry server that are not covered here, open a support ticket and include your server IP, a description of the problem, and any relevant error messages from the GPanel console.