Summon Corpse Ritual

Conan Exiles PC Discussion PC Bug Reports
1

Game mode: Offline
Type of issue: Bug
Server type: Offline
Region: NA
Mods?: No

Bug Description:

I attempt to use summon corpse ritual (with an extant corpse) and after walking to the ritual start, the character jitters in circles at the ritual point on the circle. Even after starting the ritual at the ritual start location, after the container locks nothing happens after several seconds, then the ritual is seemingly cancelled. Components are not used, but the ritual never completes.

Installed Mods:

None

Steps to Reproduce:

  1. Place components into circle, click ritual (note unlocked through gameplay, not in creative mode, and not fully encumbered).
  2. Observe that bug is encountered.
2

Also note that the spiders in Kurak’s dungeons seem to be having some issues. Last time I ran the dungeon they spawned in a corner and didn’t do anything (again creative mode was not on).

3

Greetings Exile,

Thank you for your report. Can you share with us if you receive any error messages during the ritual?

Also, are you playing on single-player or co-op mode?

Thank you in advance.

4

I didn’t get an error message and I was in single-player.

If you have the time:
Also, not sure if it is a “bug” but lore items like the journal at the start don’t respawn after being picked up (even if the item is dropped/lost). It would be nice if getting ganked in PVP didn’t threaten my access to in game lore items. Thank you for your time.

5

Greetings Exile,

Thank you for your report. Can you please share your saved file with us?

You can find it by following:

Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved

It should be the “game” file for Exiled Lands or “dlc_siptah” for Isle of Siptah.

Also, please share the location of where the ritual took place and failed.

Feel free to reach out in private via direct message if you prefer.

Thank you in advance.

6

Sent

7

I tried to reproduce the bug just to be sure, and it appears the bug is no longer there. Whatever was recently patched fixed the issue. Sorry for taking up your time.