Changing the Server Map
Map changes in Conan Exiles are high-impact operations because they affect mods, player progression paths, and existing save compatibility.
Engine.ini Method
To switch to Isle of Siptah, edit Engine.ini:
Savage Wilds (Modded Map)
If using a modded map like Savage Wilds, you must have the mod installed in ActiveMods, then set the map path:
Restoring Exiled Lands
Simply remove the ServerDefaultMap line or set it to:
Map Migration Workflow
When switching maps, prepare migration messaging, validate mod-map compatibility, and explicitly define progression continuity rules. Unexpected map transitions are a common source of player churn, even when technically successful.
- Compatibility pass: Verify all active mods support the target map.
- Data policy: State whether characters, inventories, or builds are preserved.
- Launch validation: Test spawn points, resource nodes, and travel routes before reopening.
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.