Running a Bellwright dedicated server is the best way to build a stable home for your settlement, allies, and long-term campaign progress. Instead of relying on a player-hosted session, a dedicated server can stay online, handle restarts more cleanly, and give your group better control over performance, backups, and access. Whether you are hosting for a small co-op group or a larger community, the setup process is manageable once you understand the installation path, configuration files, and tuning options.
TLDR: Install the Bellwright dedicated server through Steam or SteamCMD, then configure the server name, password, save settings, ports, and player limits before launching it. Make sure your firewall and router allow the required ports, especially if friends will connect from outside your local network. For best performance, use a machine with strong CPU performance, enough RAM, SSD storage, and regular automated restarts. Always back up your saves before changing settings or updating the server.
Why Host a Dedicated Server?
Bellwright is built around progression: gathering resources, liberating villages, managing companions, expanding bases, and surviving a dangerous medieval world. Because of that, server stability matters. A dedicated server allows your world to persist without requiring the original host to be online and actively playing.
It also gives you more freedom. You can set the server to private, invite only trusted players, schedule maintenance, test configuration changes, and preserve backups before major updates. For groups that play regularly, this makes the game feel more like a shared living world and less like a temporary session.
Recommended Server Requirements
Bellwright can be demanding because it combines survival systems, settlement simulation, AI behavior, combat, and world streaming. Your exact requirements depend on the number of players and how developed the world becomes, but the following baseline is a good starting point:
- CPU: Modern quad-core processor minimum; six or more cores recommended for active groups.
- RAM: 8 GB minimum for a small server; 16 GB or more recommended.
- Storage: SSD strongly recommended for faster loading, saving, and updates.
- Network: Stable broadband with good upload speed; wired Ethernet is preferred.
- Operating system: Windows Server or a modern Windows desktop installation is the simplest route; Linux may require Proton or compatibility work depending on official support.
If you are renting from a hosting provider, choose a plan with dedicated CPU resources rather than the cheapest shared option. Bellwright’s AI and settlement activity can become heavier as the world grows, so headroom is valuable.
Installation Method 1: Steam Client
The easiest installation method is through the Steam client, especially if you are setting up the server on a Windows machine.
- Open Steam and go to your Library.
- Use the library filter and enable Tools.
- Search for Bellwright Dedicated Server.
- Install it to a dedicated folder, preferably on an SSD.
- After installation, open the server directory and review the included files, launch scripts, and configuration examples.
This method is ideal if you want a visual interface and easy updates. The downside is that it requires Steam to be installed, which some server administrators prefer to avoid on production machines.
Installation Method 2: SteamCMD
SteamCMD is the preferred method for VPS, dedicated machines, and automated deployments. It lets you install and update the server from the command line without using the full Steam client.
- Download SteamCMD from Valve’s official developer wiki.
- Extract it to a folder such as
C:\steamcmd. - Create a server folder such as
C:\bellwrightserver. - Run SteamCMD and log in. If anonymous login is supported by the dedicated server package, use
login anonymous; otherwise log in with a Steam account that has access. - Use the server’s Steam app ID with
app_update, then validate the files.
A typical SteamCMD workflow looks like this:
steamcmd
login anonymous
force_install_dir C:\bellwrightserver
app_update <Bellwright Dedicated Server AppID> validate
quitIf the server receives frequent updates, create a small update script so you can patch quickly before launching. Always stop the server before updating to avoid corrupted files or incomplete saves.
Basic Configuration
Once installed, the next step is configuration. File names may differ slightly between versions, but most dedicated servers include a configuration file, command-line launch options, or both. Look for files such as serverconfig, settings, ini, or included sample scripts.
Common options to review include:
- Server name: Choose a clear name your players will recognize.
- Password: Use a password if the server is private or community-only.
- Maximum players: Start conservatively and increase only if performance remains stable.
- Save name or world slot: Keep this consistent to avoid accidentally creating a new world.
- Region or visibility: Public servers should be clearly named; private servers should use passwords.
- Admin list: Add trusted Steam IDs if admin tools are supported.
- Auto-save interval: Shorter intervals reduce progress loss but may cause brief performance dips.
After editing settings, restart the server and check the console or log files for errors. A typo in a configuration file can prevent the server from appearing in the browser or cause it to launch with default settings.
Ports, Firewall, and Router Setup
If players cannot find or join your server, networking is usually the reason. Dedicated servers need open ports for game traffic and, in some cases, query traffic used by server browsers. Check the official Bellwright server documentation or the server config comments for the current required ports.
On a Windows host, allow the server executable through Windows Defender Firewall. If the machine is behind a home router, forward the required UDP and TCP ports to the local IP address of the server. It is also smart to set a static local IP for the host machine so the port forwarding rule does not break after a reboot.
For rented servers, firewall rules may be controlled through a provider dashboard. In that case, open the ports inside the dashboard and inside the operating system firewall. If your server is listed but players time out, double-check both layers.
Launching the Server
Most installations include a launch executable or batch file. You can usually start the server by running the provided script, but for long-term hosting you should consider a process manager or scheduled task.
A simple launch script may include parameters for the server name, port, configuration file, or save directory. Keep a clean copy of your working launch script, and add comments if multiple administrators will manage the server.
After launch, watch the console during startup. The first boot may take longer because the world and save structure need to initialize. Once the server is running, join from a client machine and confirm that settings, password protection, and saving behave as expected.
Backups and Updates
Backups are not optional. Bellwright worlds can represent dozens or hundreds of hours of shared progress, and a failed update or corrupted save can ruin a campaign. At minimum, back up the save folder before every update. Ideally, automate backups daily and keep several previous versions.
- Before updates: Stop the server, back up saves, then update files.
- After updates: Start the server and check logs before inviting players back.
- Before config changes: Copy the working configuration file.
- For communities: Announce maintenance windows so players do not lose progress.
Use compressed archives with timestamps, such as BellwrightBackup_2026_07_13.zip. Store backups outside the main server directory so they are not accidentally deleted during reinstallations.
Performance Tips for a Smoother World
Performance tuning is about keeping the server predictable. Bellwright can become more demanding as settlements grow, NPCs move, and players spread across the map. The goal is to reduce spikes and avoid pushing the machine to its limit.
- Use SSD storage: This improves loading and save operations.
- Limit player count: Do not raise slots just because the server can start with them.
- Schedule restarts: A daily restart during low activity can clear memory buildup and refresh performance.
- Monitor CPU and RAM: If usage is constantly high, reduce player count or upgrade hardware.
- Avoid heavy background tasks: Disable unnecessary software, scans, and downloads during active play.
- Keep drivers and OS updated: Stability patches can matter on long-running hosts.
If players report lag, distinguish between server lag and network lag. Server lag affects everyone: delayed AI, slow interactions, or rubber-banding across the group. Network lag may affect only one player and often comes from Wi-Fi, distance, or poor routing.
Security and Admin Best Practices
Even a small private server should follow basic security habits. Use strong passwords, avoid sharing administrator access casually, and never run unknown scripts from strangers. If remote desktop access is enabled, protect it with strong credentials and preferably a VPN or IP allowlist.
For public servers, moderation becomes part of administration. Keep a list of trusted admins, document rules clearly, and maintain backups before banning, wiping, or changing major settings. A well-managed server is not only faster and safer; it is also more enjoyable for players.
Final Thoughts
A Bellwright dedicated server gives your group a reliable place to build, fight, and expand without depending on one player’s session. The essential formula is simple: install the server cleanly, configure it carefully, open the correct ports, back up your saves, and monitor performance as your world develops. With a little maintenance and sensible settings, your medieval rebellion can keep growing day after day.