RCON: Remote Administration
RCON gives you fast remote control during incidents, but insecure setup can expose full administrative access, so configuration must prioritize security and auditability.
Enabling RCON
In ServerSettings.ini (or your startup script):
Recommended Tools
- MCRcon: Simple command line tool.
- BattleMetrics: Web-based RCON with player history.
Common RCON Commands
broadcast [Message]- Send a message to all players.listplayers- See who is online with SteamIDs.kick [PlayerName]- Remove a player.
Secure RCON Operations
Run RCON as an emergency and maintenance channel, not a permanent open endpoint. Bind access to trusted hosts, rotate credentials regularly, and avoid sharing one password across multiple staff members.
- Access control: Restrict source IP ranges where possible.
- Credential policy: Use long random passwords and rotate after admin turnover.
- Change trace: Document high-impact remote commands in your incident log.
Operational Checklist
Treat this topic as a repeatable server operation, not a one-time change. Schedule changes during lower traffic, announce maintenance windows, and keep a rollback snapshot before each update. If your server is modded, validate changes on a staging copy first so startup logs, world loading, and player joins are confirmed before production rollout.
Validation Steps
- Capture baseline metrics: Record CPU, RAM, and average player ping before changes.
- Apply one change at a time: Avoid batch edits that make root-cause analysis difficult.
- Review logs after restart: Check for version mismatch and dependency warnings immediately.
- Run a real join test: Confirm fresh clients can connect and complete core gameplay actions.
- Observe for at least 24 hours: Validate behavior under peak load, not only right after reboot.
Performance and Stability Notes
Most hosting incidents come from resource spikes combined with configuration drift. Keep restart cadence predictable, review world/save growth weekly, and cap optional systems that generate extreme entity counts. When performance drops, compare with your last known-good baseline and revert recent high-risk changes quickly to reduce downtime.
Backup and Rollback Policy
Use automated daily backups plus pre-change snapshots for risky operations. Keep at least one off-node copy and test restore procedures routinely. A practical retention strategy is 7 daily, 4 weekly, and 2 monthly restore points. If a change causes instability, roll back first, stabilize service, and then reattempt with a narrower test scope.
Game-Specific Hosting Notes
- Mod and DLC compatibility: Revalidate after each patch to avoid startup or save load failures.
- Purge and thrall load: High base density and AI activity can increase server frame time.
- RCon/admin control: Keep audited admin commands and restart messaging to reduce disruption.