Not sure where this should go but i will try it here.
I was doing the scroll quest at Bastion today. Just as i hand in the last scroll and get the come back in a week speech. Somebody kindly logs on and crashes the server.
It was not a time out by me its was a server crash as Yasguard had vanished for the gamespy listing. When the server came back up some of the scrolls at least that i gave to Lyra were back in my pack. But when i talked to her she still gave the come back in a week speech.
So my question, is the experience my character got for the scrolls lost(not exactly sure what she had so its hard to tell). And if there was a roll back to a point before or during handing over the scrolls why does Lyra still think she i have given her my weeks quota.
Another thing that maybe be a bug Lyra gives her come back in a week speech but its not a week more like 9 days. Last couple of times i wrote down the day i gave her scrolls and a week later or 8 days still got the come back in a week speech.
Scroll quest
Moderator: Top Team
-
- Honor Guard: Church of Pants
- Posts: 1292
- Joined: Fri Jun 25, 2004 5:00 pm
- Location: England (GMT+0)
Scroll quest
A quote from a mage, without my magic I am just an Elf in a bathrobe.
I'm not a member of the team but I'll answer this as best as I'm aware regarding these collection type quests.
1) The timing on them is kinda bugged. This is partly due to NWN being absolutely terrible at keeping the time properly, but also as far as I know the way they were originally written meant the minimum time before handing it more was at least 8 days, not seven. This problem exists with some of the collection quests on Avlis too. It's unfortunate, I don't see it changing.
2) It really sucks the server crashed at this point. Collection quest logging is stored in the database. That means it is updated instantly with new data. However, character information is stored in memory and saved when you rest, transition (I think), and when you manually do save character. So the collection data had been saved the moment the conversation script completed, but character information was unfortunately just in memory when the crash occurred, and not updated to disk/bic file.
Hopefully someone in the team can tidy up the edges on my overview on it, and help you out
[/quote]
1) The timing on them is kinda bugged. This is partly due to NWN being absolutely terrible at keeping the time properly, but also as far as I know the way they were originally written meant the minimum time before handing it more was at least 8 days, not seven. This problem exists with some of the collection quests on Avlis too. It's unfortunate, I don't see it changing.
2) It really sucks the server crashed at this point. Collection quest logging is stored in the database. That means it is updated instantly with new data. However, character information is stored in memory and saved when you rest, transition (I think), and when you manually do save character. So the collection data had been saved the moment the conversation script completed, but character information was unfortunately just in memory when the crash occurred, and not updated to disk/bic file.
Hopefully someone in the team can tidy up the edges on my overview on it, and help you out

-
- Knight: Church of Pants
- Posts: 973
- Joined: Mon Dec 27, 2004 5:11 am
- Location: Whats the use of have names if you lose all your friends. That's where I'm from.
Daecon pretty much got it right. The timing and the info for collected scrolls is stored via external DB. It should generally be 8-9 days, because of how it is set up. The script requires a delete command ran through the DB to clear out a variable that is denoted to represent the "one week", and that generally only gets ran once daily, which may not be at a consistant time daily.
And yes, the experience for the scrolls and such is lost since you hadn't rested/saved prior to the crash, there really isn't an easy way to redo it without having to do a bunch of DB editting and hacking.
And yes, the experience for the scrolls and such is lost since you hadn't rested/saved prior to the crash, there really isn't an easy way to redo it without having to do a bunch of DB editting and hacking.