Brickadia Dedicated Server Setup
Learn how to set up your own Brickadia dedicated server using SteamCMD. This comprehensive guide covers Windows and Linux installation for complete Brickadia server hosting control.
Brickadia Server System Requirements
Windows
Windows 10/11 (64-bit)
Linux
Ubuntu 18.04+ / CentOS 7+ / Debian 9+
Windows
Intel i5-4590 / AMD FX 8350 or equivalent
Linux
Intel i5-4590 / AMD FX 8350 or equivalent
Windows
8 GB RAM minimum, 16 GB recommended
Linux
8 GB RAM minimum, 16 GB recommended
Windows
10 GB available space
Linux
10 GB available space
Windows
Broadband Internet connection
Linux
Broadband Internet connection
Component | Windows | Linux |
---|---|---|
Operating System | Windows 10/11 (64-bit) | Ubuntu 18.04+ / CentOS 7+ / Debian 9+ |
CPU | Intel i5-4590 / AMD FX 8350 or equivalent | Intel i5-4590 / AMD FX 8350 or equivalent |
Memory | 8 GB RAM minimum, 16 GB recommended | 8 GB RAM minimum, 16 GB recommended |
Storage | 10 GB available space | 10 GB available space |
Network | Broadband Internet connection | Broadband Internet connection |
Prerequisites
You must have a Brickadia Dedicated Server Hosting Token to run a server.
How to get your token:
- Launch Brickadia
- Go to Settings → Account
- Click "Create Dedicated Server Hosting Token"
- Copy the generated token
Network Requirements:
- • Static IP address (recommended)
- • Port 7777 (UDP) open for game traffic
- • Stable internet connection
- • Router port forwarding configured
Administrative Access:
- • Administrator/root privileges
- • Firewall configuration access
Windows Brickadia Server Setup
SteamCMD is required to download and manage your Brickadia dedicated server files.
Use SteamCMD to download the Brickadia dedicated server files using the Steam App ID 3017590.
Command Prompt
cd C:\steamcmd
steamcmd +login anonymous +force_install_dir C:\BrickadiaServer +app_update 3017590 validate +quit
Command Breakdown:
- •
+login anonymous
- Login without Steam account - •
+force_install_dir
- Set installation directory - •
+app_update 3017590
- Download Brickadia server (App ID 3017590) - •
validate
- Verify file integrity - •
+quit
- Exit SteamCMD after completion
Navigate to your server directory and start the Brickadia dedicated server with your hosting token.
Command Prompt
cd C:\BrickadiaServer\Brickadia\Binaries\Win64
BrickadiaServer-Win64-Shipping.exe -server -log -port=7777 -token=YOUR_HOSTING_TOKEN_HERE
Replace YOUR_HOSTING_TOKEN_HERE
with the actual token you generated from the Brickadia game client.
Linux Brickadia Server Setup
Install SteamCMD using your distribution's package manager.
Ubuntu/Debian
sudo add-apt-repository multiverse
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install steamcmd
CentOS/RHEL
sudo yum install epel-release
sudo yum install steamcmd
Create a dedicated user for the server and download the Brickadia server files.
Terminal Commands
# Create brickadia user
sudo useradd -m brickadia
sudo su - brickadia
# Create server directory
mkdir ~/brickadia-server
cd ~/brickadia-server
# Download server files
steamcmd +login anonymous +force_install_dir ~/brickadia-server +app_update 3017590 validate +quit
Start the Brickadia server with the Linux binary.
Terminal Commands
cd ~/brickadia-server/Brickadia/Binaries/Linux
chmod +x BrickadiaServer-Linux-Shipping
./BrickadiaServer-Linux-Shipping -server -log -port=7777 -token=YOUR_HOSTING_TOKEN_HERE
Running as a Service (Optional):
For production servers, consider creating a systemd service to automatically start your Brickadia server on boot and restart it if it crashes.
Brickadia Server Management
-server
Runs in dedicated server mode
-log
Enables console logging
-port=7777
Sets the server port (default: 7777)
-token=TOKEN
Your dedicated server hosting token
Troubleshooting Common Issues
- • Verify your hosting token is correct and not expired
- • Check that port 7777 is not already in use
- • Ensure you have sufficient system resources
- • Verify server files are completely downloaded
- • Configure port forwarding for port 7777 (UDP) on your router
- • Check firewall settings on your server
- • Verify your external IP address is accessible
- • Ensure the server is fully loaded before allowing connections