Woe is me! (Or, are my quests broken?) - Page 2

Paul Stevens · 09-22-2003, 12:01 PM

In my view, this is a terrible problem. I have
written privately to Cocoa Spud to see what he
thinks. I will let you know what we conclude.

CocoaSpud · 09-22-2003, 03:57 PM

65002 is MAX_QUEST_STAGE+1, and is returned by the quest lookup function
when it cannot find the asked for quest.

We store all quests in the saved game file. So what's probably happening is that you play a design and save the game. Then use the editor to add new quests and events that reference the quests. Now play the edited design and load the saved game and the old quests replace all of the new ones. When you trigger one of your new events, it tries to reference a quest that was removed by loading the saved game.

I think we can fix this problem. Looking at the code it appears that the same problem exists for special items and keys too.

Paul Stevens · 09-23-2003, 10:42 AM

Do you understand what has happened here? I will say what
I understand.

There are two sets of files: 1)The Design and 2) The SaveGame.
When you edit a design you naturally edit the 'Design' files.
So, if you add a quest, you add it only to the 'Design' files
and not to any 'Savegame' files that are lying about.

When you save a game, all the quests are written to the 'Savegame'
files. When you load a savegame, the program discards any
quests that are in the 'Design' files and loads all quests from
the 'Savegame' files. So any quests that you added to the 'Design'
files after saving the game will not be there!!!!

CocoaSpud tells me that he is going to change the behaviour of
the program when it loads a savegame. Instead of deleting all the
quests from the 'Design' files and replacing them with the quests
from the 'Savegame' files, he will update the 'Design' file quests
with the 'Savegame' quests. If the same quest exists in both
files then the 'Design' quest will be replaced with the 'Savegame'
quest. If the quest exists in only one of the files then it, of
course, will be used.

There are some additional, rather technical, details that make this
possible....a little foresight by CocoaSpud several years ago has
paid off.

09-22-2003, 03:57 PM	#12
CocoaSpud Zhentarim Guard Join Date: March 15, 2001 Location: Melbourne, FL, USA Posts: 375	65002 is MAX_QUEST_STAGE+1, and is returned by the quest lookup function when it cannot find the asked for quest. We store all quests in the saved game file. So what's probably happening is that you play a design and save the game. Then use the editor to add new quests and events that reference the quests. Now play the edited design and load the saved game and the old quests replace all of the new ones. When you trigger one of your new events, it tries to reference a quest that was removed by loading the saved game. I think we can fix this problem. Looking at the code it appears that the same problem exists for special items and keys too. __________________ CocoaSpud<br />Dungeon Craft Development Team<br /> [url]\"http://uaf.sourceforge.net\" target=\"_blank\">http://uaf.sourceforge.net</a>

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Is it broken?	Dragonshadow	General Discussion	21	05-15-2006 10:25 PM
Broken quests????	Vohnkar	Miscellaneous Games (RPG or not)	5	11-03-2002 11:07 AM
broken dock get me out	revk	Wizards & Warriors Forum	2	03-09-2002 02:51 PM
Broken sword?	PoesRaven	Baldurs Gate II: Shadows of Amn & Throne of Bhaal	3	12-14-2001 05:41 PM
broken weapons	matt	Baldurs Gate II Archives	2	07-09-2001 12:48 PM

09-22-2003, 12:01 PM	#11
Paul Stevens Drow Warrior Join Date: July 8, 2003 Location: Madison, Wisconsin Age: 85 Posts: 296	In my view, this is a terrible problem. I have written privately to Cocoa Spud to see what he thinks. I will let you know what we conclude.

09-23-2003, 10:42 AM	#13
Paul Stevens Drow Warrior Join Date: July 8, 2003 Location: Madison, Wisconsin Age: 85 Posts: 296	Do you understand what has happened here? I will say what I understand. There are two sets of files: 1)The Design and 2) The SaveGame. When you edit a design you naturally edit the 'Design' files. So, if you add a quest, you add it only to the 'Design' files and not to any 'Savegame' files that are lying about. When you save a game, all the quests are written to the 'Savegame' files. When you load a savegame, the program discards any quests that are in the 'Design' files and loads all quests from the 'Savegame' files. So any quests that you added to the 'Design' files after saving the game will not be there!!!! CocoaSpud tells me that he is going to change the behaviour of the program when it loads a savegame. Instead of deleting all the quests from the 'Design' files and replacing them with the quests from the 'Savegame' files, he will update the 'Design' file quests with the 'Savegame' quests. If the same quest exists in both files then the 'Design' quest will be replaced with the 'Savegame' quest. If the quest exists in only one of the files then it, of course, will be used. There are some additional, rather technical, details that make this possible....a little foresight by CocoaSpud several years ago has paid off.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)