Is there any way to obtain multiple quests from the same quest giver eg. guild quests?
Multiple quests from same quest giver?
Débuté par
slave of slaanesh
, avril 19 2011 08:51
Retour en haut
#2
Posté 19 avril 2011 - 02:13
Ralthis
-
- Members
- 55 messages
There most certainly is. (Note: the following assumes you've already created the quest in your Journal, and have a starting entry for that quest.) Here are 2 ways to do it:
1. On the Other Actions tab in a given conversation node (i.e.: the point in the conversation where you want the PC to obtain the quest), there is a Journal selection tool. Click on the drop-down menu and choose the name of your quest. Next, choose the Journal entry number for that quest you would like to give at that point. This can be done for any amount of Journal quests, assuming you've already written them in your Journal. All you have to do is place the different quests in the correct conversation nodes.
2. You can custom script them in the Actions Taken tab. Create a new script (call it at_(whatever), or anything else you like) for each journal quest you want to give. Place each in the conversation node where you would like to give the quest. In each script, initialize the PC speaker with :
object oPC = GetPCSpeaker();
Then, give him the quest entry with:
AddJournalQuestEntry(your quest's tag here, the quest node number here, oPC, FALSE);
Presto! You're done.
1. On the Other Actions tab in a given conversation node (i.e.: the point in the conversation where you want the PC to obtain the quest), there is a Journal selection tool. Click on the drop-down menu and choose the name of your quest. Next, choose the Journal entry number for that quest you would like to give at that point. This can be done for any amount of Journal quests, assuming you've already written them in your Journal. All you have to do is place the different quests in the correct conversation nodes.
2. You can custom script them in the Actions Taken tab. Create a new script (call it at_(whatever), or anything else you like) for each journal quest you want to give. Place each in the conversation node where you would like to give the quest. In each script, initialize the PC speaker with :
object oPC = GetPCSpeaker();
Then, give him the quest entry with:
AddJournalQuestEntry(your quest's tag here, the quest node number here, oPC, FALSE);
Presto! You're done.
#3
Posté 19 avril 2011 - 06:20
TSMDude
-
- Members
- 865 messages
#4
Posté 19 avril 2011 - 06:32
_Guile
-
- Members
- 685 messages
It's often best to use one NPC for multiple quest, because you can save yourself time & resources by having fewer NPCs on your palette... Because most builders spawn in NPCs, they have to put them on the palette, when the palette becomes bloated you start running into errors within the module as you become lower on resources or exceed the maximum threshold... (Not desirable)
Most builders who exceed system resources for the palette run into a variety of problems, like scripts not firing, NPCs not acting correctly, and yes the list goes on and on...
It's rather trivial to handle most quest, it either works off an item or a variable set on the PC...
When the PC kills the boss, the PC should get a variable, that shows they did it, and of course everyone in the party...
When the PC returns to the quest giver, the quest giver will check to see if the PC has the variable on them..
Naturally you would set that the PC has been given the quest by placing an int on them, more specifically on an item they have, this is why I give them a very unique token, so it will be persistent across restarts, or if it's for single player use, give them an item instead... Making quest persistent however is a bit more tricky and requires scripting in the module's OnClientEnter event, this way they get all the quest they completed & are doing when they enter, every time...
Most builders who exceed system resources for the palette run into a variety of problems, like scripts not firing, NPCs not acting correctly, and yes the list goes on and on...
It's rather trivial to handle most quest, it either works off an item or a variable set on the PC...
When the PC kills the boss, the PC should get a variable, that shows they did it, and of course everyone in the party...
When the PC returns to the quest giver, the quest giver will check to see if the PC has the variable on them..
Naturally you would set that the PC has been given the quest by placing an int on them, more specifically on an item they have, this is why I give them a very unique token, so it will be persistent across restarts, or if it's for single player use, give them an item instead... Making quest persistent however is a bit more tricky and requires scripting in the module's OnClientEnter event, this way they get all the quest they completed & are doing when they enter, every time...
Modifié par _Guile, 19 avril 2011 - 06:37 .
#5
Posté 20 avril 2011 - 05:42
zero-feeling
-
- Members
- 144 messages
knats system include and editor for DMs in my projects
might want to follow previous link for a demo, but it's really easy to use.
zero
might want to follow previous link for a demo, but it's really easy to use.
zero
#6
Posté 21 avril 2011 - 09:58
slave of slaanesh
-
- Members
- 18 messages
Thanks guys, thats a great help.
