This system is designed to allow module builders to control all basic quest management needs for all quests in their modules with a single set of scripts. Further, the builder can create quests without having to write any scripts at all; just use the scripts already provided for all quest creation needs.
Three versions are available: quest managment without journals, quest management with journals, and finally quest management with persistent journals. Knat's "PQJ - Persistent Quests & Journals" is used for the databasing needs in the latter of the versions. You can view this system seperately by visiting the following link:
Link
If you use the persistent journal version, you must add the following
line of code to your Module OnClientEnter script:
RebuildJournalQuestEntries(GetEnteringObject());
After that, you need to put the following above the main funciton of
the OnClientEneter script:
#include "pqj_include"
The main advantage of this system is that builders can make quests without the need to write scripts. Another advantage of this system is that a builder does not have to have unique quest management scripts for every single quest developed in a module. In the end, this system can litteraly cut out scores of scripts from a module, thus reducing file size and making module development more manageable.
It should be noted that the system manages typical quest needs that are
pretty much universal to all quest building. Quest specific code will still have to be developed by the builder if "special" things are needed. Regardless, the system does
reduce script overhead . . . even for more advanced building needs.
Furthermore, this system is capable of managing quest tracking/advancement,
quest resetting, XP distribution, Gold Reward/Payment,conversation based skill checks, alignment shifts, and item/gold possession prerequisites for conversation conditionals.
To see how the system is implemented, please play through the demo module.
The demo module is actually a brief tutorial that shows the basics of how the system works in a simplistic quest. The tutorial describes what
is happening in the quest conversations and where code is being used.
A builder can make far more complicated quests than that seen in the demo module with a little creativity and planning. You can even make non-linear quests with this system. A simple example would be to make a series of smaller sub-quests that interconnect to bring forth an overlying major plot. To complete the end sequence, the player must do all the sub-plot activity to get clues or items or whatever. They could do the sub-plots in any order, and a final check can be made to see if they have done everything they need to finish the major plot. This system can manage
most of this activity, however it is likely that a few custom scripts will
be needed to check that all sub-plots are finished to move on to the final
plot sequence.
All scripts included start with the prefix "vg_" so that you can manage them easily in the toolset. The only exception is the script "pgj_include" I decided not to change the prefix of this to honor Knat's work as being his
own and not mine.
This system does require the use of journals, but is not persistent. All quest tracking is handled by using bioware standard variable managment as built into the journal keeping system.
Does this system support NPCs that are part of multiple quests? It seems to me that the NPC has to have the variable of a specific quest on them.
As an example, let's say NPC A starts a quest that you need to get Item 1 from NPC B. NPC B has the item for NPC A, and its retrieval updates the quest's progress, but NPC B also has another quest for you, one you could take independently of NPC A's quest. Is that possible?
Posted by Mannast at 2010-06-06 06:52:25 Voted 10.00 on 06/06/10
I just love these scripts. I have put together a small number of secondary scripts and sub-systems that use these as the starting point. Thanks for your hard work!
Posted by hexmendacious at 2008-05-19 03:00:40 Voted 9.75 on 05/19/08
This is a great system and I heartily recommend it.
Posted by Ondaderthad at 2008-02-16 21:43:24 Voted 9.75 on 02/16/08
Thanks for the quick reply. (and I increase my vote rating just for the good level of support from all Vuldrick's scripts)
Will be looking for the update. _________________________ The Best PW system is getting even better. PLATEMAIL Tech Preview
I have an update that I will release soon. I fixed a bug in one script (calling for things backwards) and added a few new scripts to do things that I am finding to be more and more commonly needed. Perhaps I can release a nice detailed README when I upload the update.
As far as the custom item issue is concerned . . . you are right in thinking that you have to use my custom item tag scheme. If you do not follow the "formula" then my scripts will not generate nor take the items using the existing scripts. You could make a copy of the item handling scripts and call for item resrefs and tags in any generic way that you wish. _________________________ Vuldrick Garrison
Posted by Ondaderthad at 2008-02-14 20:05:42 Voted 9.75 on 02/16/08
Good scripts but there are a few problems using this system.
Some better documentation would help. I know there is the demo but reading NPC conversations to find out how to build a quest is not the best.
There is also an issue with the need to make specific quest items with a special tag. It took me ages to figure out how.
TAG: demoItem1
So it is not possible to make a quest using items from either the standard bioware (ie. skeleton knuckles) or items from another system (ie. craft system items)
In this case I am not able to change the tags of the items without breaking the other systems.
For example my first idea for a simple quest was to ask the players to get a woodsman's axe and chop a log (using UOAcraft) The tag of that log is specific and used in other scripts.
So the solution is to make a new script testing for "has_item" but then this defeats the purpose of this system which is to have less scripts.
Or am I missing something else?
_________________________ The Best PW system is getting even better. PLATEMAIL Tech Preview
Posted by hexmendacious at 2007-12-05 22:16:53 Voted 9.75 on 05/19/08
This is great... worth ripping out my current mess of scripts for quests and starting fresh. Thanks!
Posted by Ondaderthad at 2007-10-21 19:24:17 Voted 9.75 on 02/16/08
Very good quest management system.
I just added a script snippet to the alignment and reward scripts to remove the PC from the party.
When used in a PW you don't really want other PCs to get hit with an alignment change especially when the rogue decides to do a Chaotic quest. ;-)
// Quest stuff from knat and forsettii persistent quests system
// Modified to award only the PC and NOT the whole party thank you very much!
object oPC = GetPCSpeaker();
//////////////////////////////////////////////////////////////////
// Now we do not reward every party member
object oPlaceholder = GetFirstFactionMember(oPC);
while (oPlaceholder == oPC)
{
oPlaceholder = GetNextFactionMember(oPC);
// Make oPlayer temporarily independant.
// Remove PC from Party since this is an individual Quest
RemoveFromParty(oPC);
//////////////////////////////////////////////////////////////////
// Here we do stuff to the individual PC..
// Rewards GP, XP, Changes in alignment, remove item etc..
//////////////////////////////////////////////////////////////////
// Give the speaker some gold
// Give the speaker some XP (XP to PC)
// Give the speaker the items
// Remove items from the player's inventory
// Set the variables
AddPersistentJournalQuestEntry(sName, 3, oPC, FALSE, FALSE, FALSE);
///////////////////////////////////////////////////////////////////
// Now we can return the PC to the party.
AddToParty(oPC, oPlaceholder);
} // end while
///////////////////////////////////////////////////////////////////
} // end Main
_________________________ The Best PW system is getting even better. PLATEMAIL Tech Preview
Tops script.Hey any chance of there being a faction change added to the scripts? you have change alignment in there a reputation change would be great.
Posted by rathsrants at 2006-11-22 08:34:04 Voted 10.00 on 11/22/06
All I can say is wow. Great Stuff. _________________________ The Dirty Dwarf
Site
at 2010-07-30 19:38:55
