a restore isn't possible, sorry.

I can't currently guarantee 100% correct working of the p-chests, I'll tackle that after the server move.

quite indeed, yes.

I changed the chest-saving script a bit. Please watch your chests over the next few days.

(The error is enormously hard to catch, as it pops up only once in a while and probably only long after the point where the cause-event happened. There is a check if the chest was saved correctly, but it may very well be that this check isn't checking everything that needs to be checked.)

So there are still contents there, but they're different ones now? Which chest was that?

That's interesting, as until then, a bugged chest meant that everything was gone. I call that progress, of some sort :)

Please retest, I tweaked something (namely adjusting the wait period to the amount of stuff in the chest)

Did you find that the saving process were taking longer with the more items you put in? I think this is really an issue of the saving process taking too long - and there is alas no way to check if it has finished, properly or not. :(

I'll probably add in some mechanism to completely & automatically restart the server every day, would 3:00am GMT be an ok time for that?

The idea is good, as I'm looking for just such a thing, alas, I fear no: The player PCs .bic files are saved as flat files in the servervault directory. The chest NP, while also being in .bic format is actually written as a BLOB of data into the database, not onto the filesystem.

Also, vaultster is an external dll which does the filehandling (and thus the checking) while the db-things are done by nwnx2. Would we want to include the same checking code, we'd have to basically completely rewrite nwnx2.

Short answer: Sorry, no :)

(Also: There is some semblance of .bic checking going on already. After saving the chest npc to the db, I try to re-fetch it again, testing if it looks ok. But there are not a lot of testing options that nwnscript offers here, so not all errors are being spotted.)