From ISMods Wiki

---

Contents 1 ISXEQ2 information for ISXEQ2:QUESTDATA (Custom Trigger) has moved 1.1 Please see: http://eq2.isxgames.com/wiki for up-to-date content. 1.2 Description 1.3 Forms 1.4 Examples

ISXEQ2 information for ISXEQ2:QUESTDATA (Custom Trigger) has moved

Please see: http://eq2.isxgames.com/wiki for up-to-date content.

---

Description

The QUESTINFO triggers are sent to your client everytime you do one of the following actions:

• Accept a new quest
• Delete a quest
• Finish a quest
• Receive a quest update

There are other instances where the triggers will be sent (it will always be information about the quest that's currently in your quest helper window); however, those four instances are the only times that they will always be sent.

Forms

The following data is sent to your client via invisible triggers each time you do one of the four actions mentioned above.

• QUESTDATA::ID(%d)
• QUESTDATA::NAME(%s)
• QUESTDATA::CATEGORY(%s)
• QUESTDATA::CURRENTZONE(%s)
• QUESTDATA::DESCRIPTION(%s)
• QUESTDATA::PROGRESSTEXT:%d.%d(%s)

 %s = string
 %d = integer

Please note that you will receive multiple QUESTDATA::PROGRESSTEXT lines, depending upon your progress. See the examples for how this works.

Examples

Here are a few examples of what the triggers will look like as they are initiated. Please note that although they are invisible in the game, InnerSpace WILL see them.

QUESTDATA Examples

Example by Traills

This very basic script will echo quest info to your console screen. You could then set the parts you want to a declared variable and use it in scripts.

 Function main()
        {
                 AddTrigger questinfo QUESTDATA::@qinfo@
                 ;Main Loop
                   do
                       {
                           ExecuteQueued
                           wait 10
                       }
                   while 1
         }
 Function questinfo(string Ling, string qinfo)
         {
                  echo ${qinfo}
                  return
         }

If you just wanted the progress text from the trigger you would change the trigger to something like:

  AddTrigger questinfo QUESTDATA::PROGRESSTEXT:1.1(@qinfo@)

Then it would only grab that part of the quest.