Updating Your Server
Conan Exiles updates can break mods, map settings, and startup flags in one patch cycle, so treat each update like a controlled release with rollback-ready backups.
SteamCMD Command
Conan Exiles Dedicated Server App ID is 443030.
Mod Updates
Updating mods is harder manually. You usually need to download the .pak files from Steam Workshop or use a script that supports mod updating (like DedicatedServerLauncher on Windows).
Patch-Day Runbook
Before updating, freeze admin edits and export your active mod list from ActiveMods. After patching, verify mod load order, map boot, and player authentication in that order. If startup fails after a content patch, disable nonessential mods first, then restore them in small batches to isolate the incompatible package.
- Pre-check: Save current startup arguments and INI files to a timestamped folder.
- Post-check: Confirm server browser visibility and stable join time for at least three test logins.
- Rollback trigger: Revert immediately if crash frequency increases after the first restart window.
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.