Conan Exiles: private server crash from triggering thrall rescue
A specific Conan Exiles Enhanced bug surfaced in late April / early May 2026: private dedicated servers crash when a player triggers a Thrall Rescue mission (the new mechanic where a thrall NPC requests help from a player and spawns an objective). The crash is not deterministic — some triggers crash, others don't — but on affected servers the rate is high enough to derail a session. This page covers the confirmed reproducer, the in-game workaround, and how to recover thralls that get stuck in a crashed rescue mission.
What's actually happening
Thrall Rescue missions spawn dynamic objectives near the player who triggered them. The crash happens in the mission-spawn path when the server attempts to instantiate the objective's encounter group. Specifically:
- The encounter group contains NPCs that reference a CharacterTable entry whose AI behavior tree includes the new "rescue follower" branch.
- If the spawn location is too close to an existing player base structure, the spawn path tries to relocate the encounter and triggers a null-reference in the rescue branch.
- The server crashes with a stack trace pointing to
FNpcDirector::SpawnRescueMissionor a similar internal symbol.
The bug only fires on private dedicated servers, not on official servers, because official servers use a slightly different mission scheduler. Confirmed across both Exiled Lands and Isle of Siptah maps.
Confirming you're hit by this bug
Check your server log file at ConanSandbox/Saved/Logs/ConanSandbox.log. Around the time of the crash, look for:
LogConanExiles: Triggering rescue mission for player <PlayerName>
LogConanExiles: Encounter group <ID> selected
LogOutputDevice: Error: === Critical error: ===
[... null reference exception ...]
SpawnRescueMissionIf the last meaningful log line before the crash mentions a rescue mission or "Triggering rescue," you have the bug. Other crash signatures point at other causes — see the general server crash article for those.
The immediate workaround: disable rescue missions
Edit ConanSandbox/Saved/Config/WindowsServer/ServerSettings.ini (or LinuxServer/ if you're on Linux/Wine) and add:
[ServerSettings]
EnableRescueMissions=False
RescueMissionFrequency=0Stop the server, edit the file, start the server. Rescue missions will no longer trigger. This removes a piece of new content from the experience but prevents the crash.
If you're using the in-game admin panel instead of editing INI files directly: press Insert as admin, go to Server Settings, look for "Enable Rescue Missions" under the Dynamic Events section. Uncheck. The setting writes to the same INI file behind the scenes.
Recovering thralls trapped in a crashed mission
If a player was rescuing a thrall and the server crashed mid-mission, the thrall may be in one of three states when the server comes back:
| State | How to recover |
|---|---|
| Mission marked complete, thrall is in player's inventory | No action needed — the crash happened after the reward was granted |
| Mission marked incomplete, thrall is at original mission location | Player travels back to location, manually interacts with thrall to claim |
| Mission marked incomplete, thrall is missing from world entirely | Admin uses SpawnItem console command to manually grant the thrall type the player was rescuing (note: this is a recovery, not a cheat — match the original mission reward) |
To find the original mission state, admin can query the server save:
# Linux SQLite query against game.db
sqlite3 ConanSandbox/Saved/game.db "SELECT * FROM player_missions WHERE state != 'complete' AND mission_type = 'rescue';"The output shows incomplete rescue missions and which thrall NPC ID was the reward target. Use that to grant the equivalent thrall to the affected player.
Server admin policy: communicate before disabling
Disabling rescue missions removes a feature your players may enjoy. Before unilaterally turning it off:
- Post in your server's Discord that the rescue feature is being temporarily disabled due to crashes
- Note the workaround is server-side only — players don't need to do anything
- State that the feature will return once Funcom patches the underlying bug
- Monitor official patch notes; re-enable when a fix ships
This is the difference between a server that loses players ("things keep breaking and the admin doesn't say anything") and one that retains them ("I know what's going on and when it'll be fixed").
Why this didn't affect official servers
Official Funcom servers use a server-side encounter scheduler that pre-validates spawn locations against player base proximity before triggering the rescue mission spawn path. Private dedicated servers use the simpler client-trigger path. The pre-validation never null-references; the simpler path can. Funcom is expected to backport the official server's path to the dedicated server build in a patch, at which point this workaround can be reverted.
Check the Conan Exiles update notes after each patch. When you see "Fixed crash related to rescue mission spawning" or similar, re-enable rescue missions in your ServerSettings.ini and remove the workaround.
Related articles
- General dedicated server crash diagnosis
- Conan Exiles Enhanced launch notes
- Admin commands reference
- Save file management and backups
For a managed Conan Exiles server with daily backups so you can roll back a crash like this, see Supercraft plans.