Romestead combines the grand historical landscapes of ancient Roman provinces with detailed agricultural estates, aqueduct engineering, citizen management, and defenses against barbarian invasions. Native Dedicated Server support lets players build a persistent 24-hour provincial world, keeping irrigation, olive oil production, and legion construction running while the group is offline. This article details server setup and .NET 8 runtime configuration.
1. Server environment and runtime dependencies
Romestead's server uses a modern C# / .NET architecture with specific host requirements:
| Configuration | Baseline requirement | Key considerations |
|---|---|---|
| Runtime framework | .NET 8.0 Runtime (x64) | Install .NET Desktop Runtime 8.0 or use a portable package with a bundled runtime |
| CPU architecture | 4 cores / above 2.8 GHz | Supports citizen decision trees and complex water network physics |
| Physical RAM | 8 GB physical RAM | 12 GB+ (for multiple players exploring different provinces) |
| Network port | UDP 8050 |
Core game communication port |
2. SteamCMD deployment command
The Romestead Dedicated Server supports anonymous SteamCMD downloads:
- Server AppID:
4763510 - Executable:
Server.exe(launched throughstart-romestead.bat)
# Download/update the Romestead dedicated server anonymously
steamcmd +login anonymous +app_update 4763510 validate +quit
The first run of Server.exe creates config.json in the server root.
3. Network port planning
Romestead uses one efficient UDP transport channel:
| Port | Protocol | Purpose | Firewall and forwarding policy |
|---|---|---|---|
| 8050 | UDP | Estate citizen commands, building topology, and network synchronization | Core port; allow in the firewall and forward on the router for public access |
Allow the port in Windows PowerShell:
New-NetFirewallRule -DisplayName "Romestead Game UDP" -Direction Inbound -LocalPort 8050 -Protocol UDP -Action Allow
4. Main configuration: config.json
Edit config.json in the server installation root:
{
"ServerName": "Romestead LanGame Province",
"Password": "",
"Port": 8050,
"MaxPlayers": 12,
"AutoSaveIntervalMinutes": 15,
"WorldName": "DefaultProvince",
"EnableCheats": false
}
Port: Default8050; increment it for multiple instances.AutoSaveIntervalMinutes: 15 minutes recommended to persist province construction progress automatically.
5. Open-source LGSM management
We recommend the official open-source LanGame Server Manager (LGSM) (repository: GitHub - SZSLGJCOM/LanGame-Server-Manager).
- Automatic .NET 8 setup: LGSM injects a portable .NET runtime, avoiding additional complex SDK dependencies on the host.
- Visual settings interface: Directly edit server name, maximum population multiplier, and save interval.
- Full live estate backups: Creates scheduled provincial world snapshots to prevent corrupted saves from sudden power loss.
6. Remote multiplayer and network optimization
- Public internet: After forwarding UDP 8050 on the router, friends enter
public IP:8050in the lobby to join the Roman province within seconds. - Networking without a public IP: For rented accommodation or campus networks, use LINK in LanGame OS Orbit. Bring teammates into the same encrypted LAN room and connect through virtual IPs to build an enduring Roman estate together!