Sassy Storm
2005-12-04 19:09:52 UTC
#4315
I think the persistent storage is having trouble keeping track of when it last saved the contents of the chest. Today when I went to check the contents, it displayed the items that I left in it when I left for the tournament yesterday, even though I later switched a few of the items out.
As a result, my dire mace is now missing, but I have an extra bastard sword and tower shield. If you can think of other specific information to help you track this bug down, let me know.
alstromeria
2005-12-04 19:47:37 UTC
#4318
That's the bright side.
My stored stuff's disappeared into the ether.
le sigh.
Arkov
2005-12-04 21:28:07 UTC
#4329
Well drat. Er, be careful with what you put in for now?
Arkov
2005-12-11 10:14:09 UTC
#4718
I'm having trouble duplicating these problems, although I know that they're still occuring. Can anybody who has experienced them provide me with a more detailed account of exactly what happened?
josi
2005-12-11 13:57:38 UTC
#4730
I lost nothing untill I put so many things there that the storage made another page. After that things started to disappear. Usually it is the things on the second page, but one day an item had disappeared from the first page even when there was no second page at all at that time, but the first page was quite full. So it seems that the second page is for some reason affecting to it. I don't know anything of scripting, so I have no idea if this is important or not.
Wrexsoul
2005-12-11 16:37:54 UTC
#4731
Hazarding a wild guess here; can it have something to do with how the game reorders stuff, akin to items in bags/boxes on death? If not, never mind me.
Paha Poika
2005-12-11 16:41:41 UTC
#4732
At first it saved all my stuff, but after that the 4 original stuff that were saved stayed, but everything else that I put in after that disappeared. Today after respawning, the whole storage was empty.
SideKick
2005-12-12 22:53:31 UTC
#4788
Another odd occurrence. My Watch armour, shield and helm all duplicated. A half-plate and tower shield both disappeared.
Hookswords
2005-12-12 22:57:32 UTC
#4789
If it helps I've had no problems so far :D
Arkov
2005-12-13 04:24:03 UTC
#4805
This may be fixed. I wouldn't recommend putting anything extremely important or irreplaceable in storage just yet, though, until the new code has been tested out a bit.
Arkov
2005-12-27 08:46:30 UTC
#5204
Additional feedback on this would be excellent.
josi
2006-01-01 20:19:47 UTC
#5289
Persistant chest still seems to have some problems. I had a shield stored there, but took it out. When I logged in after a reset, I had the shield in the chest, even though I had in the inventory as well. So the storage remembered the content from the earlier time obviously.
Linelle
2006-01-01 20:37:37 UTC
#5290
I put in a plain whip for testing and it was gone after the next reset occured, no sooner, no later, all I know.
prestonhunt
2006-01-02 00:08:17 UTC
#5297
Stored my Chain mail, helm, and tower shield in mine yesterday, and took out the junk Buriel Shroud.
Today, the buriel shroud is back in there, and the other stuff is missing.
Arkov
2006-01-13 03:37:28 UTC
#6102
This isn't yet fixed.
The issue appears to be that database changes aren't being properly committed to the database file, and so when the server cleanly resets, changes to persistent storage are saved, but when the server crashes, all changes to persistent storage since the last reset are lost.
I'm working to determine a fix for this -- anybody with a working knowledge of NWNX APS scripts who wants to lend a hand would be greatly appreciated.
Cawila has also suggested some improvements that should (ideally) end the problem of items being lost from persistent storage due to server crashes (while the chest is open, for example) once and for all -- but we need to get this issue out of the way before I can begin to implement his system.
-Arkov
Arkov
2006-02-04 20:49:04 UTC
#8139
This should be fixed.
Implementing cawila's system is next on the agenda.
Arkov
2006-02-10 08:29:13 UTC
#8672
Nobody has yet reported any issues.
It looks like this is finally fixed.
Wooah!