[bug?] Dupre won't rejoin after resurrected

[CheekySparrow]

Dupre got killed and upon reviving him, he's no longer in my party and I can't get him to rejoin. I used all of his conversation options, and nope. Looks like he just got turned into a regular NPC somehow.
I left the area and returned, no luck.
I have the latest Exult and Keyring mod installed.
Forum search turned up nothing yet.
I attach a savegame before Lord British with Dupre's body in Avatar's hands

DupreBug.jpg (226.81 KiB) Viewed 6851 times

[CheekySparrow]

Looks like this bug was already reported but didn't progress anywhere
https://sourceforge.net/p/exult/bugs/1668/

[Dominus]

As in that old bug I can reproduce it with your savegame but not when I get him killed again. It's curios that his job answer is the one from being in the party.
Do you know where he got killed and/or can you upload a savegame before he got killed?

[CheekySparrow]

I do have the old savegame, however it is a couple hours before Dupre got whacked; don't know if it's useful, but I attach it below.
He was killed in the dungeon in the Dark forest, and I think I might have killed him accidentally myself using the "flame strike" spell on monsters.

Here are the screenshots of this dungeon.

DupreDungeon.jpg (204.53 KiB) Viewed 6834 times

[CheekySparrow]

A side question - can I still get ol' Dupre back into party somehow? As last savegame was quite long time ago, replaying it wouldn't be fun... also, unrelated complaint, for some reason, wherever I create a named savegame, it overwrites a quicksave. Don't know if it's intentional, but it's a bit unexpected and annoying.
Thanks!

[Dominus]

To get him back add him in our cheat screen:
- enable cheats
- hit f2 (to enter cheat screen), n (npc tool), 4 (which NPC?), n (NPC flags), i (Party), 3x ESC to quit the cheat screen

Yes, that quicksave is "volatile" is kind of intentional. Because loading works by extracting the save file to the gamedat folder. Saving works by writing to the gamedat folder and then archiving that to the save file, except for the quicksave, it only saves to the gamedat folder. Back when we imitated the way the original handled saving and loading we just implemented the quicksave like this and didn't anticipate that it causes the problems you encounter. It's an issue that could use someone to fix (just by saving to quick.sav for example).

[CheekySparrow]

Thanks, really appreciate it, Dominus! I'll chime in if the bug resurfaces, possibly then we will be able to isolate it.