To make a Brickadia server, install the dedicated-server files through Steam or SteamCMD, register a hosting token from your Brickadia account, launch the server on UDP port 7777, configure it in Edit Game, and forward that port through your router. You will also need a public IP, a firewall rule, and a reserved local address if you host from home. The Linux setup documented by the Brickadia Community Wiki uses an x86_64 machine with a recent 2–4-core CPU and at least 2 GB of RAM; those figures are prerequisites for that Steam Early Access setup, not a guaranteed player-capacity target.
This guide covers Linux and Windows file locations, first-run authentication, router configuration, world backups, and the recovery steps that prevent common connection and save-file problems.
What do I need before creating a Brickadia server?
Prepare the host, network, and account requirements before installing anything. A dedicated server is separate from the normal game client, so it needs its own installation directory and a place for configuration and saved worlds.
- Host hardware: The Linux guide specifies x86_64, a recent 2–4-core CPU, and at least 2 GB of RAM for its documented Steam Early Access setup. Treat these as starting requirements rather than a promise of a particular number of players.
- Operating system: The documented dedicated-server executable is Linux-based, while Windows uses a corresponding WindowsServer configuration directory. Use the server tool supplied through Steam or SteamCMD.
- Network: Home hosting requires a public IP, UDP port 7777 forwarded to the host, a DHCP reservation so the host keeps the same local address, and an operating-system firewall rule allowing the server.
- Brickadia account: You must create a dedicated-server hosting token in the Brickadia account center. The token is required on the first launch.
- Storage and backups: Keep the installed server files separate from saved worlds and configuration files. Reserve space for backups of the Saved directory.
No source used for this guide publishes a universal bandwidth figure or player-capacity benchmark. Actual capacity depends on the world, activity, simulation load, network quality, and the rest of the host’s workload.
Should I host at home or on a VPS?
Home hosting gives you direct control and avoids a recurring server bill, but you must handle port forwarding, firewall rules, power outages, backups, and a changing public IP. A VPS or managed host removes most router and uptime work, while adding a monthly charge and another provider’s maintenance and access policies.
| Consideration | Home host | VPS or managed host |
|---|---|---|
| Monthly cost | Uses your existing connection and electricity; no researched price is established here. | Recurring price varies by provider and plan; no current plan was evaluated for this guide. |
| Setup effort | Install files, configure the server, reserve a LAN address, forward UDP 7777, and open the firewall. | Install and configure on the provider’s machine; router work is usually unnecessary. |
| Public reachability | Requires a public IP and a router that permits inbound forwarding. | Normally includes a provider-assigned public address, subject to that provider’s networking rules. |
| Uptime | Depends on your power, internet connection, and home equipment. | Depends on the provider’s infrastructure and maintenance schedule. |
| Control and privacy | Full control of the machine, files, and network. | Administrative control is limited by the host’s policies and access model. |
| Backups and updates | You are responsible for copying worlds and rerunning the update process. | Some services offer backup tools, but coverage and retention must be checked before purchase. |
If your internet service uses carrier-grade NAT, or your router has no inbound-forwarding option, a home dedicated server may not be reachable from the public internet. In that case, use a host with a public address or Brickadia’s in-game GUI hosting mode, which is a different hosting method.
How do I install the Brickadia dedicated-server files?
Steam provides the server tool through the normal client, and SteamCMD can install the same distribution without a graphical Steam session. The current community overview identifies the dedicated-server app as Steam app ID 3017590.
Install with Steam
- Open Steam on the machine that will run the server.
- Find and install the Brickadia Server tool. Choose a dedicated directory for the server installation rather than placing it inside your personal game saves.
- After installation, locate the server executable and keep the installation directory unchanged during future updates.
Install with SteamCMD
- Install SteamCMD for your operating system and create an empty directory for the server files.
- Run SteamCMD anonymously and set that directory as the install target. A standard update invocation is
steamcmd +login anonymous +force_install_dir /path/to/brickadia-server +app_update 3017590 validate +quit; replace the path with your actual directory. - Let SteamCMD finish before launching. Keep saved data outside the install directory so an update or clean reinstall does not overwrite your worlds.
Use the same Steam tool or SteamCMD script for later updates. After an update, check the current Brickadia documentation for changes to the app ID, executable name, token process, default port, or configuration paths.
How do I create and use a hosting token?
A hosting token authenticates a dedicated server with Brickadia. Create it in the Brickadia account center while signed in to the account that will own the server.
- Sign in to the Brickadia account center.
- Create a dedicated-server hosting token and copy it exactly. Treat it like a credential: do not publish it in screenshots, chat, scripts shared with other administrators, or public repositories.
- Pass the token to the first server launch with the
-token=...argument. - Wait for the server to complete registration and loading. The community overview indicates that the token can be omitted on later launches after registration has succeeded.
If the first launch fails, keep the token argument in place and inspect the server log for authentication or connectivity errors. Do not assume that a successful file installation means the token was accepted.
What command starts a Brickadia server on Linux?
From the directory containing the installed server binary, run the documented Linux executable with logging, the default game port, and your token:
./BrickadiaServer-Linux-Shipping -log -port=7777 -token=YOUR_HOSTING_TOKEN- Change into the server installation directory.
- Make sure the
BrickadiaServer-Linux-Shippingfile is executable. - Replace
YOUR_HOSTING_TOKENwith the token created in the account center. - Start the command and leave the terminal open while the server loads. The
-logswitch keeps startup and connection messages visible. - Wait until loading finishes before trying to connect. Starting a client while the world is still loading can look like a network failure.
After the server has registered the token, subsequent launches may omit -token=..., according to the community overview. Keep the argument available for recovery if registration is lost or the installation is moved.
How do I connect to the server for the first test?
Use Brickadia’s manual connection screen from a client that can reach the host.
- Start the dedicated server and wait for its loading messages to settle.
- Open Brickadia and choose Join Game.
- Select Manual Connect.
- Enter the host’s public IP address and the server port, using
7777unless you deliberately configured another port. - Connect from outside the host’s local network first, such as a friend’s connection or a mobile hotspot. Testing only from the same LAN can be misleading because some routers do not support hairpin NAT.
If an outside connection works but a device on your home network cannot connect, the server and forwarding rule may be fine; the remaining issue is likely router loopback behavior or a local firewall rule.
How do I set the server name, password, world, and listing status?
Once the server is running, use the in-game Edit Game screen to establish its identity and access rules. The settings are then represented in GameUserSettings.ini, so stop the server before making manual file edits.
Settings to review in Edit Game
- Server name: Use a distinct name friends can recognize in the browser or direct-connect instructions.
- Description: Explain the world, rules, building theme, or expected play style.
- Password: Set one when the server is private. Share it through a channel intended for your players.
- World: Select the world that should load after startup.
- Public listing: Decide whether the server should appear in the public list or be reachable only by direct connection.
Where is GameUserSettings.ini?
| Platform | Configuration path |
|---|---|
| Linux | ~/.config/Epic/Brickadia/Saved/Config/LinuxServer/GameUserSettings.ini |
| Windows | %localappdata%BrickadiaSavedConfigWindowsServerGameUserSettings.ini |
Make a backup copy before editing the file. If a change prevents startup, restore the backup or remove only the problematic setting rather than deleting the entire Saved directory.
How do I open UDP 7777 on a home network?
Forward UDP port 7777 from the internet-facing router to the host’s reserved local IP address, then allow the same traffic through the host firewall.
- Give the server computer a DHCP reservation in the router. Record the reserved local address, such as
192.168.1.50; the exact address depends on your network. - Create a port-forwarding rule for UDP 7777 from the router’s WAN side to that reserved address and port 7777.
- Add an inbound firewall rule on the server operating system for the server executable or UDP 7777.
- Start the dedicated server and verify that it is listening on the configured port.
- Test from outside your LAN with Manual Connect. Ask another player to connect before announcing the address publicly.
Do not forward a port to a computer whose local address changes. A DHCP lease change can silently send players to the wrong device even though the router rule still appears enabled.
How do I save and restore Brickadia worlds?
Use Brickadia’s world commands for named saves, enable Auto Save, and keep copies of the Saved directory. A server restart does not replace a deliberate backup.
Create a named save
From the server console or an administrator command interface, run:
BR.World.SaveAs savenameReplace savename with a short name that identifies the world or date. Save before maintenance, major building changes, or experiments with new settings.
Load a named save after a restart
Run:
BR.World.Load savenameConfirm that the intended save is loaded before allowing players to build. Keep several dated copies rather than overwriting the only known-good world.
Use Auto Save and custom world files
Enable Auto Save in the advanced settings. Custom .brdb world files belong in the server’s Saved/Worlds folder; copy them there while the server is stopped, then load the appropriate world from the game’s controls or command interface.
What should I back up before updating?
Back up the Saved directory, especially configuration files and world data, before replacing server binaries. Store at least one copy on a different disk or machine so a failing host does not destroy both the live world and its backup.
- Copy
GameUserSettings.iniand any related configuration files. - Copy named saves and custom
.brdbfiles from the Saved/Worlds directory. - Record the launch command, port, token-handling decision, and router’s reserved local address.
- Keep a dated backup before each major update or configuration change.
After updating, start the server with the same Steam tool or SteamCMD script, watch the log for migration errors, and verify the world before inviting players back.
What are the most common Brickadia server problems?
The server starts, but nobody outside the house can join
Check that the router forwards UDP, not only TCP, and that it points to the host’s current reserved address. Confirm the operating-system firewall rule and test from a genuinely external connection. If your ISP uses carrier-grade NAT, normal port forwarding may not provide a public inbound path.
Manual Connect works locally but not remotely
This usually indicates a router, firewall, or public-address issue rather than a Brickadia world problem. Verify the public IP you are giving players, check whether the ISP address changes, and ask the router whether it supports NAT loopback; local-only tests cannot prove internet reachability.
The token is rejected or the server never registers
Stop the process, create or copy a fresh token from the account center, and launch again with the complete -token=... argument. Check the log for authentication errors and confirm that the machine can make outbound connections. Do not remove the token until a successful registration has completed.
The server loads the wrong world
Stop the server, verify the selected world in Edit Game and the relevant configuration file, then use BR.World.Load savename for the intended named save. Confirm that custom files are in the server’s Saved/Worlds folder and that the account running the server can read them.
A restart appears to erase recent building
Enable Auto Save and run BR.World.SaveAs before planned restarts. If a recent build is missing, stop further writes, preserve the current Saved directory, and inspect the dated backups before loading an older file.
How do I keep a server reliable over time?
Reliability comes from a repeatable update and backup routine rather than one successful launch.
- Keep the installation directory separate from Saved data.
- Use one documented Steam or SteamCMD update procedure and record its path.
- Back up configuration and worlds before every update.
- Check the launch log after updates and confirm that the expected executable and port are still valid.
- Test Manual Connect from outside the LAN after router, ISP, firewall, or host changes.
- Review current Brickadia documentation before publishing a setup guide or rebuilding a server, because token registration, executable names, supported platforms, configuration paths, and default ports can change.
The Brickadia Community Wiki identifies itself as community-maintained, so treat its Linux prerequisites and command examples as version-specific guidance. The 2 GB RAM and 2–4-core figures describe that documented Steam Early Access setup, not a guaranteed capacity for every world or player count.
Frequently Asked Questions
Can I run a Brickadia server without a public IP address?
A directly reachable dedicated server normally needs an inbound path from the internet. If your ISP uses carrier-grade NAT or your router cannot forward ports, use a machine with a public address or Brickadia’s in-game GUI hosting mode instead; GUI hosting is a different mode with different uptime and administration behavior.
Do players need the same local network to join?
No. Players on other networks use the host’s public IP and configured port through Manual Connect. A same-LAN test only confirms local routing and may not reveal an incorrect public forwarding rule.
Where should I keep a hosting token?
Keep it in a private administrator-controlled location and avoid putting it in public scripts, screenshots, or repositories. If you believe it has been exposed, create a replacement in the Brickadia account center and update the server’s launch procedure.
What is the safest way to move a server to another computer?
Install the server files on the new machine, copy the backed-up Saved directory and configuration, and launch with the registered token as needed. Update the router’s forwarding rule and DHCP reservation to the new machine, then test from outside the LAN before switching players over.