A small Brickadia dedicated server can run on a Linux x86_64 virtual machine with a recent 2–4-core CPU, AVX or AVX2 support, and at least 2GB of RAM. Windows is supported as well. You must make the host reachable, forward UDP port 7777 (unless you deliberately change it), and register a Brickadia hosting token on the first launch. There is no published official disk-space minimum, so storage should be sized around the server files, world saves, logs, backups, and update headroom. For active builds, 4GB is a more practical starting point than the 2GB baseline; large or heavily scripted worlds commonly need 6GB or 8GB-plus.
What are the minimum Brickadia dedicated-server requirements?
The documented baseline is modest, but it has a few non-negotiable compatibility requirements. The Brickadia Community Wiki’s Linux setup guide lists at least 2GB of RAM and a Linux x86_64 virtual machine with a recent 2–4-core CPU. The Brickadia manual says a dedicated machine may run Windows or Linux. The CPU must support AVX or AVX2 instructions; the Community Wiki FAQ identifies this as an explicit requirement for the Unreal Engine 5-based server.
| Component | Documented baseline | Practical planning note |
|---|---|---|
| Operating system | Linux x86_64 or Windows | Choose the platform you can patch, secure and administer reliably. |
| CPU | Recent processor with 2–4 cores | Confirm AVX/AVX2 support before renting or repurposing hardware. |
| Memory | At least 2GB for a small Linux server | Allow 4GB or more as builds, players, physics and plugins grow. |
| Storage | No fixed official capacity published | Reserve space for binaries, saves, logs, backups and updates. |
| Network | UDP 7777 by default | Forward the port and allow it through the host firewall, or change it consistently. |
| Authentication | Brickadia hosting token on first registration | The token can be omitted on later launches after registration. |
These are server-process requirements, not a recommendation for the computer used by each player. A host with a fast connection but no AVX/AVX2 support is not a safe choice, while a machine with many cores but too little memory can still fail when a world becomes large.
How much RAM does a Brickadia server need?
Use 2GB only for a genuinely small server. Brickadia’s memory demand is driven primarily by the amount of construction in the world, not simply the number of connected players. Physics objects, active contraptions, Omegga and other plugins add further overhead.
| RAM | Workload described by current practical guidance | What that means when choosing a host |
|---|---|---|
| 2GB | 1–5 players, small casual builds, no Omegga plugins | Lowest sensible starting point; leave little room for growth. |
| 4GB | 5–15 players, moderate builds, light plugins | Better default for a public server that is expected to grow. |
| 6GB | 15–25 players, large ongoing builds, Omegga | Useful when the world is persistent and plugin activity is material. |
| 8GB or more | 25–30 players, city-scale builds or heavy plugin use | Choose a plan that can be upgraded if construction continues expanding. |
The table is workload guidance from WinterNode’s 2026 hosting article, not an official Brickadia certification. Its author reports roughly 100–200MB for a minimal Omegga setup and 300–500MB for a heavily configured one. Those amounts sit on top of the game server and world’s own usage, so a plugin-heavy installation should not be sized at the bare 2GB baseline.
A useful way to budget memory is to start with the baseline, add headroom for the largest build you expect to keep loaded, then account for peak joins and plugin activity. A server that is comfortable at quiet times can still run out of memory while several players join, a large save loads, or scripts initialize. If your host offers a 16GB DDR4 kit as an upgrade, treat it as general headroom rather than a guaranteed fit: verify the motherboard or virtual-machine plan’s memory limit, DDR generation, form factor and ECC support first.
What CPU and how many cores does Brickadia require?
A recent x86_64 CPU with 2–4 cores is the documented starting point, but instruction-set support matters more than a headline core count. Check that the processor exposes AVX or AVX2. The Community Wiki FAQ states that Brickadia explicitly requires this functionality because it is built on Unreal Engine 5.
Build-focused versus physics-heavy servers
Core count is only a baseline. Build-focused servers are more likely to become memory-bound as brick counts and saved structures rise. Servers running vehicles, complex contraptions, physics interactions or scripted game modes can become CPU-constrained instead. WinterNode’s practical guidance does not establish a universal clock-speed target, so compare the CPU generation and sustained performance rather than relying on gigahertz alone.
How to check compatibility before deployment
- Ask a VPS or bare-metal provider for the exact CPU model or family.
- Check that the model supports AVX and AVX2; do not assume every older x86_64 virtual machine does.
- Confirm that virtualization does not mask the required instruction set from the guest.
- Prefer a plan that lets you add cores or move to a stronger host if physics-heavy gameplay becomes slow.
If a machine lacks AVX/AVX2, adding RAM will not solve the compatibility problem. Select another host or processor before installing the server.
How much storage does a Brickadia dedicated server use?
No reviewed official document gives a fixed minimum number of gigabytes. The Linux guide asks you to choose an installation directory for SteamCMD and the server files, while the dedicated-server reference documents a configurable Saved directory and world-save locations. Storage is therefore a capacity-and-retention decision rather than a single requirement.
What to include in your capacity plan
- The downloaded Brickadia server binaries and SteamCMD files.
- The current world and older saves you retain for rollback.
- Logs, crash output and any diagnostic files.
- Local backups or compressed archives.
- Omegga, plugin and other server-side data.
- Temporary space needed while SteamCMD downloads or replaces an update.
Choose an install volume with room for the largest world you expect to keep and for at least one recoverable backup. Do not advertise a made-up “10GB minimum” or “50GB minimum” as an official Brickadia requirement; the published material does not establish either figure. Check free space before updates and periodically prune obsolete logs or move backups to separate storage.
Which port and network settings are required?
Brickadia uses UDP port 7777 by default. Forward that port from your router to the server’s private address and allow it in the operating-system firewall. A server can appear to start correctly while remaining unreachable if either the router rule or firewall rule is missing.
Changing the default port
You can set another port with the -port= launch argument. The chosen value must be allowed by the firewall, forwarded by the router or provider, and used consistently by players and any external server listing. Changing only the process argument while leaving the network rule on 7777 will make the host appear offline.
Public IP and administration checks
- Confirm the host has a reachable public address or provider networking that supports inbound UDP.
- Reserve a stable private address for a self-hosted machine so the forwarding rule does not break.
- Open only the required game and administration ports, and restrict remote administration to trusted sources.
- Test from outside the local network; a connection that works only from the host or the same LAN does not prove public reachability.
How do I install and register a Brickadia dedicated server?
Server files can be obtained through Steam or anonymously with SteamCMD using app ID 3017590. The exact package and command syntax can change with future releases, but the registration sequence is stable: download the files, launch with a hosting token once, then run without the token after the host is registered.
- Prepare the machine. Use a supported Windows or Linux system, verify AVX/AVX2 support, create a dedicated install directory and ensure the account running the service can write to it.
- Download the server. Install through Steam or use SteamCMD anonymously with app ID
3017590. Keep the SteamCMD directory and server directory on storage with room for saves and updates. - Generate a hosting token. In your Brickadia account area, create the token used to register the dedicated host. Treat it like a credential and do not publish it in screenshots or startup scripts shared with others.
- Launch once with the token. On Linux, the guide’s example is
./BrickadiaServer-Linux-Shipping -log -port=7777 -token=yourTokenHere. Replace the example token with your own value and keep the port aligned with your firewall and router. - Confirm registration and files. Watch the log for successful startup, verify that the Saved directory is being populated, and check that the process remains running after the world loads.
- Restart without the token. After registration, later launches can omit
-token=. Store the final command in your service manager or startup task so restarts use the same port and paths. - Test externally. Join from a different network, then test a second player joining while the world is active. This catches forwarding, firewall and peak-load problems before you announce the server publicly.
On Linux, configuration is placed under ~/.config/Epic/Brickadia/Saved/Config/LinuxServer, including GameUserSettings.ini. Keep that directory in your backup plan; reinstalling binaries does not replace a reliable copy of configuration and world data.
Should I run Brickadia on Windows or Linux?
Both operating systems are supported. The better choice is the one you can maintain confidently, because patching, firewall configuration, backups and recovery matter as much as the initial installation.
| Consideration | Linux | Windows |
|---|---|---|
| Documented support | Linux x86_64 VM is described by the setup guide. | The manual identifies Windows as supported. |
| Typical administration | Shell commands, service units and file permissions. | Graphical administration, Windows Firewall and scheduled tasks or services. |
| Configuration location | ~/.config/Epic/Brickadia/Saved/Config/LinuxServer |
Use the Saved/configuration locations created by the Windows server package. |
| Best fit | Operators comfortable with remote, low-overhead server management. | Operators who prefer Microsoft administration tools or already manage a Windows host. |
The manual recommends a VPS or bare-metal machine from a server-rental company when reliability is the priority. Self-hosting can work when you control the router and power, but you remain responsible for uptime, public addressing, backups, firewall rules and hardware failures.
How should I choose hardware or a hosting plan?
Compare complete resource and networking details, not just the advertised player slot count. A plan that looks inexpensive can be unsuitable if it hides the CPU model, lacks AVX2 exposure, restricts inbound UDP or offers no upgrade path.
- Memory and scaling: Confirm included RAM, whether it is dedicated, and how quickly you can move from 2GB to 4GB, 6GB or 8GB-plus.
- CPU capability: Check AVX/AVX2, CPU generation and sustained physics performance. Vehicles and contraptions deserve more CPU attention than a quiet building server.
- Storage policy: Ask whether disk is local SSD, how much is included, and whether backups or snapshots consume the same quota.
- Networking: Verify a public IP or equivalent inbound UDP service, firewall control and the ability to forward or select a non-default port.
- Administration: Ensure you can use SteamCMD, inspect logs, edit configuration and restart the process remotely.
- Operating system: Pick Windows or Linux according to your maintenance skills, not a claimed performance advantage that the documentation does not establish.
For a private test world, a 2GB Linux VM can be reasonable. For a public community with persistent construction, 4GB provides a safer starting margin. Large cities, heavy scripting and busy physics scenes justify planning for 6GB or 8GB-plus and a CPU upgrade path.
What problems indicate that the server is undersized?
Symptoms should guide the upgrade: increasing memory use during world loads points toward a RAM or save-size issue, while simulation slowdowns around vehicles and contraptions point toward CPU pressure. Keep logs and observe the server during the busiest expected event rather than sizing from an empty map.
- Process is killed or the host swaps: Increase RAM, reduce plugin load and check whether backups or another service are consuming memory.
- Physics becomes sluggish: Move to a faster CPU or add cores if the provider’s plan allows it; more disk space will not improve simulation speed.
- Players cannot connect: Recheck UDP 7777 (or your selected port) at both the router and host firewall, then test from outside the LAN.
- Updates fail: Inspect free disk space and retain temporary headroom for SteamCMD downloads and replacement files.
- World changes disappear after a crash: Verify the Saved directory, permissions and backup schedule before inviting more players.
- Plugin features destabilize the process: Disable nonessential plugins, measure memory and CPU use, then reintroduce them one at a time.
Frequently asked questions
Does a Brickadia dedicated server need a dedicated graphics card?
The reviewed Brickadia setup and manual documentation do not publish a dedicated-GPU specification. When evaluating a virtual machine, prioritize a supported x86_64 CPU, AVX/AVX2 exposure, memory and networking; ask the provider directly if its virtualization layer imposes additional graphics requirements.
Can I move an existing server to another host?
Plan the move around the Saved directory and its world files, configuration and plugin data. Shut down cleanly, copy those files to the new installation, verify permissions, then perform an external connection test before decommissioning the old machine.
What should I monitor after opening the server?
Track resident memory, CPU utilization, free disk space, restart events and world-save or plugin errors during peak activity. Record the largest observed values; that history gives you evidence for an upgrade instead of relying on the nominal player count.
What happens if my CPU does not support AVX2?
The compatibility requirement cannot be fixed by changing a launch option or adding RAM. Use a processor or hosting plan that exposes AVX/AVX2 to the server process before attempting to run Brickadia.
Is 2GB enough for a long-running public community?
It can be enough for a small, lightly built group, but it leaves limited room for world growth, plugins and peak joins. If the community will keep building between sessions, choose a plan that can be expanded without reinstalling the server.
Frequently Asked Questions
Does a Brickadia dedicated server need a dedicated graphics card?
The reviewed Brickadia setup and manual documentation do not publish a dedicated-GPU specification. When evaluating a virtual machine, prioritize a supported x86_64 CPU, AVX/AVX2 exposure, memory and networking; ask the provider directly if its virtualization layer imposes additional graphics requirements.
Can I move an existing server to another host?
Plan the move around the Saved directory and its world files, configuration and plugin data. Shut down cleanly, copy those files to the new installation, verify permissions, then perform an external connection test before decommissioning the old machine.
What should I monitor after opening the server?
Track resident memory, CPU utilization, free disk space, restart events and world-save or plugin errors during peak activity. Record the largest observed values; that history gives you evidence for an upgrade instead of relying on the nominal player count.
What happens if my CPU does not support AVX2?
The compatibility requirement cannot be fixed by changing a launch option or adding RAM. Use a processor or hosting plan that exposes AVX/AVX2 to the server process before attempting to run Brickadia.
Is 2GB enough for a long-running public community?
It can be enough for a small, lightly built group, but it leaves limited room for world growth, plugins and peak joins. If the community will keep building between sessions, choose a plan that can be expanded without reinstalling the server.