Fix Brickadia problems by identifying the failure first: high server-browser latency needs a network check, low local frame rate needs a client-performance check, and a “connection timed out” error usually means the dedicated server cannot be reached. For a normal dedicated server, make sure it is fully running, expose UDP port 7777, reserve the host machine’s local address, allow the server through the operating-system firewall, and launch it with a valid hosting token. If your internet connection cannot accept inbound traffic, use Brickadia’s GUI hosting or move the server to a VPS or bare-metal machine. The sections below separate each cause so you do not waste time changing router settings when the real problem is rendering or server CPU load.
How do I identify what kind of Brickadia lag I have?
Start by separating network latency, client frame-rate problems, and overloaded server processing. They can feel similar in play, but each requires a different fix.
High latency in the server browser
If the browser reports high latency, information is taking longer to travel between your machine and the server. Distance, an unstable connection, congestion, or a busy router are more likely than a graphics setting. Steam describes latency as the time information takes to reach the server; higher latency makes lag more likely.
Low frame rate or rendering stutter
If the server’s latency is low but your view stutters, local rendering or CPU load is the first suspect. A crowded scene, mesh processing, visualization work, or another program using the computer can reduce frame rate without any network fault.
A timeout before you join
“Connection timed out” means the client did not complete a connection to the server. Check that the process is running and fully loaded, then verify reachability, port forwarding, the host address, and firewall access before changing in-game graphics.
A three-minute first check
- Look at the server-browser latency and compare it with your local frame rate. Note which one is abnormal.
- Close downloads, uploads, cloud-sync jobs, voice or video streams, and other bandwidth-heavy applications.
- If you are on Wi-Fi, test once over wired Ethernet. A Cat6 cable is useful for this test, but it cannot repair a distant server or an overloaded host.
- For a timeout, confirm the server is running and completely loaded before testing again.
Why does Brickadia say “connection timed out”?
A dedicated Brickadia server normally listens on UDP 7777. A timeout occurs when that UDP traffic cannot reach the server machine, the server is not listening on the expected port, or a firewall blocks it.
Check the server process first
Do not test a port-forward rule against a server that is still starting. Wait until the dedicated-server console indicates that loading has completed, then try again. If the process exits, crashes, or never reaches a ready state, fix the launch problem before troubleshooting the router.
Use the correct port
With the default launch configuration, forward UDP 7777. If you start the server with a different -port= value, forward that custom UDP port instead and use the same number when connecting manually. Forwarding TCP only will not satisfy the dedicated server’s normal requirement.
Check the host firewall
The operating-system firewall must allow incoming traffic for the Brickadia server executable, or an inbound rule for the selected UDP port. A router rule can be correct while the computer still drops the packet locally.
Consider networks that cannot accept inbound traffic
Carrier-grade NAT and some managed or cellular connections do not provide a usable public inbound path. Repeating the same local port-forward changes will not overcome that restriction. Brickadia’s FAQ says GUI hosting does not require port forwarding; a VPS or bare-metal machine is the documented reliability fallback when home hosting cannot receive traffic.
How do I port-forward Brickadia correctly?
Port forwarding is only one part of the path. The rule must point to a stable local address, use UDP, and match the port on which the server is actually listening.
- Give the server computer a stable local address. In the router’s DHCP or LAN settings, create a reservation for that machine. Without a reservation, the computer can receive a different address later and the existing forwarding rule will point at the wrong device.
- Open the router’s port-forwarding page. Router labels vary, but the relevant section is usually called Port Forwarding, NAT, or Virtual Server.
- Create a UDP rule. Set the external and internal port to 7777 for the default server, choose UDP rather than TCP, and enter the reserved local address as the destination.
- Save and apply the rule. Some routers restart networking after applying changes. Wait for the router and server to return to normal before testing.
- Allow the host through its firewall. Permit the dedicated-server executable or an inbound UDP rule for 7777 on the server computer.
- Test from outside the home network. Use a player on another connection and connect through the home network’s public address. Testing only from inside the same LAN can hide an inbound-reachability problem.
If you changed the launch argument to a custom port, substitute that number in every place: the server command, router rule, firewall rule, and manual-connect dialog. A mismatch in any one of those locations produces the same timeout symptom as a blocked port.
How do I launch a Brickadia dedicated server?
The dedicated-server guide requires a hosting token during first registration. The launch command supports the -port=7777 and -token=... arguments.
Use the required launch values
Start with the default port unless you have a reason to change it. A representative launch line contains -port=7777 and your valid -token=... value. Keep the token private; anyone who obtains it may be able to use it for server registration.
Confirm registration and readiness
Watch the dedicated-server console after the first launch. A successful registration should progress to a fully loaded server rather than immediately terminating. If the console reports a token or registration error, resolve that first; no router change can make an unregistered process reachable.
Match the launch port to the network
When you select a custom port, update the router and firewall rules before asking players to connect. The server browser and manual connection must use the same port that appears in the launch argument.
What hardware and network setup does a Linux server need?
The Linux guide lists a baseline, not a guaranteed capacity for every world or player count.
| Requirement | Baseline listed in the Linux guide |
|---|---|
| CPU architecture | x86_64 |
| Processor | Recent 2–4-core CPU |
| Memory | At least 2 GB RAM |
| Internet addressing | Public IP address |
| Inbound networking | UDP 7777 forwarded to the server |
Those figures tell you what is needed to start a server, not how many players a particular world can support. Larger builds, more active players, and running the game client on the same computer can consume additional CPU, memory, and bandwidth. If the host and client compete for the same resources, moving the server process elsewhere is often more effective than lowering visual settings on the client.
How do I connect manually when the server is not listed?
Use Brickadia’s manual connection screen when you know the server address and port.
- Open Brickadia and choose Join Game.
- Select Manual Connect.
- Enter the server’s reachable IP address and port. Use 7777 unless the host configured a custom
-port=value. - Submit the connection and wait for the server to finish its handshake.
For a home-hosted server, the remote player should use the host network’s public address, not the server computer’s private LAN address. The private address is the destination used inside the router’s forwarding rule.
Why does Brickadia connect but still feel laggy?
Once a connection succeeds, troubleshoot the symptom that remains instead of reopening the port-forwarding setup.
When server-browser latency is high
- Close uploads, downloads, cloud synchronization, and voice or video streams, then retest.
- Compare a wired Ethernet test with Wi-Fi. If wired play is substantially steadier, investigate wireless signal quality or local interference.
- Check that the router is ventilated and stable. Steam specifically warns that an overheating router can cause connectivity problems and lag symptoms.
- Consider geographic distance. A server far from the players can have consistently higher latency even when the host’s connection is otherwise healthy.
When the local frame rate is low
- Check whether the server-browser latency remains normal while the image stutters. That combination points toward client rendering or CPU load.
- Close nonessential applications and retest before changing configuration files.
- Update the Brickadia client, especially if the symptom resembles a documented micro-stutter or CPU-heavy mesh and visualization issue.
When everyone experiences simulation or world slowdowns
If several players report the same in-world delay while their network latency is reasonable, the host may be short on processing headroom. Running the game client and dedicated server on one machine can make that worse. Separate the processes where possible, or move the server to a VPS or bare-metal machine so server processing is isolated from the player’s desktop workload.
When only one player is affected
Ask that player to compare Wi-Fi and wired play, close background traffic, and check local frame rate separately from browser latency. A problem isolated to one machine is less likely to be a server-wide CPU or routing failure.
Should I host Brickadia at home, use GUI hosting, or rent a server?
Choose according to inbound reachability, distance to players, available CPU and memory, configuration control, recurring cost, and the support you need.
| Hosting path | Inbound reachability | Control and workload | Best fit |
|---|---|---|---|
| Home dedicated server | Requires a public inbound path, UDP 7777 forwarding, a stable DHCP reservation, and firewall access | Direct control of the machine and configuration; shares the home connection and hardware | Owners who can manage their router and have sufficient local bandwidth and processing headroom |
| GUI hosting | Brickadia’s FAQ says port forwarding is not required | Simpler when router or ISP restrictions prevent inbound connections | Quick sessions or networks behind carrier-grade NAT |
| VPS | Hosted machine provides an internet-reachable address | Moves server processing away from the player’s PC; supports server-side configuration | Reliable operation without depending on a home router |
| Bare-metal machine | Hosted machine provides an internet-reachable address | Dedicated hardware headroom and isolated server processing | Long-running or heavier worlds where consistency matters |
The Brickadia manual recommends a VPS or bare-metal machine for the best reliability. That recommendation trades a recurring hosting charge for a reachable, separately managed server and less dependence on your home network.
Where are Brickadia server configuration files?
The FAQ lists different GameUserSettings.ini locations for Linux and Windows.
| Platform | Configuration path |
|---|---|
| Linux | ~/.config/Epic/Brickadia/Saved/Config/LinuxServer/GameUserSettings.ini |
| Windows | C:Users<yourusername>AppDataLocalBrickadiaSavedConfigWindowsServerGameUserSettings.ini |
- Stop the dedicated server cleanly before opening the file.
- Make one deliberate configuration change and save the file.
- Start the server and wait for it to load completely.
- Retest the original symptom before making another change.
Changing several settings at once makes it difficult to tell which change helped or introduced a new problem. Configuration edits also cannot substitute for a missing hosting token, a blocked UDP port, or an unreachable public address.
Can updating Brickadia fix lag or crashes?
Updating is worthwhile when your symptom matches a documented fix, but it is not a universal lag cure. Recent changelog entries report fixes involving dedicated-server console crashes, client-connect crashes, CPU-heavy mesh and visualization work, and micro-stuttering.
Update both the client and the server where practical, then reproduce the same scenario. If the problem is a timeout caused by forwarding, firewall, or carrier-grade NAT, an update will not create an inbound network path. Likewise, a client-only frame-rate problem may remain after a network-related fix.
What is the most efficient recovery order?
Use this order to avoid mixing unrelated causes:
- Classify the symptom as timeout, high latency, low frame rate, or shared world slowdown.
- Close bandwidth-heavy background applications and perform one wired test if Wi-Fi is involved.
- For a timeout, verify that the server is loaded, the launch token is valid, and the intended port is in use.
- Reserve the server’s DHCP address, forward the correct UDP port, and allow the executable through the host firewall.
- Connect through Join Game → Manual Connect with the matching address and port.
- If inbound traffic cannot reach your home network, stop changing local router rules and choose GUI hosting or a VPS/bare-metal host.
- Only after reachability is working, investigate client rendering, host CPU headroom, router stability, and version-specific fixes.
Frequently Asked Questions
Can a Cat6 Ethernet cable fix Brickadia ping by itself?
No. It can provide a cleaner wired test when Wi-Fi is the variable, but it cannot reduce the physical distance to a server or repair an overloaded host. If wired and wireless results are identical, look beyond the cable at congestion, routing, or server load.
Is 2 GB of RAM enough for every Brickadia server?
No. The Linux documentation presents 2 GB as a startup baseline, not a guaranteed amount for every world or player count. Monitor resource use as the world and player population grow, and move the server to a machine with more headroom if processing becomes the shared bottleneck.
What should I do if local players connect but remote players time out?
That pattern usually means the server process is healthy on the LAN while the internet-facing path is missing or blocked. Recheck the public-address requirement, the UDP rule’s destination address, the host firewall, and whether the ISP places the connection behind carrier-grade NAT.
Can I edit GameUserSettings.ini while the server is running?
Stop the server before editing. Restart it after saving and test one change at a time so the running process does not overwrite the file or obscure which setting affected the result.
Do players need the same port number when I change the default?
Yes. The custom value must match the server launch argument, router forwarding rule, firewall allowance, and the port entered in Manual Connect. A single mismatch can look identical to a completely blocked server.