TaskGiver NPC

jdoran · #1 03-14-2013, 08:14 PM

An odd question, I know.

When sending a task selector, the header contains the NPC-ID where the task originates. How is this used by the client?

The Lost Heirlooms tasks are good examples of quests that do not begin with an NPC.

(I must apologize for my quest database being out of date, but I'm in crunch mode on a project and do not want to update it just yet. So I don't know if this quest has been implemented yet)

Zamthos · #2 03-14-2013, 09:22 PM

Well, if you take a look at TutorialB* you can assign tasks on entering the zone, on an NPC, or assign specific quests based upon current QGlobals. I don't believe I helped, would you mind elaborating? Are you wanted the task selector or to assign tasks?

Edit*: TutorialB's player.pl has a task assigned upon enter zone then a qglobal is set so they can't get it again.

jdoran · #3 03-14-2013, 10:10 PM

Good call on TutorialB, thanks much.

quest::assigntask() doesn't seem to need an NPC-ID, so I'll see how that works. I'm still puzzled by why the client needs an NPC-ID, but that is a trivial matter.

Zamthos · #4 03-14-2013, 10:32 PM

Err, I'm not 100% sure on this, don't hold me to it, but it may be so that the database can determine which NPC you have to hail/turn items in to, since the handins and everything can be handled by the database, however they can be handled in Perl as well.

jdoran · #5 03-15-2013, 05:47 PM

Just a quick update to report what I've learned.

When you start tutorial-b you are assigned a couple of quests. These do not cause the task selector to come up -- a ninja task add.

If you want the task selector, there must be a mob associated. This is a problem if you want the task selector for a quest that does not involve a mob. Fortunately the client is a mob, and the player's id works.

I suppose the client can hand the ID back to the server later, but I'm still drawing a blank. I expect it will become clear as I start to work with these client-owned tasks.