Skip to content

quest_request_items

This table basically handles 3 quest details:

  1. NPC Emote when quest is completed
  2. NPC Emote when quest is incomplete
  3. Completion text for quests requiring quest items

Structure ​

FieldTypeAttributesKeyNullDefaultExtraComment
IDintunsignedPRINO0
EmoteOnCompletesmallintunsignedNO0
EmoteOnIncompletesmallintunsignedNO0
EmoteOnCompleteDelayintunsignedNO0
EmoteOnIncompleteDelayintunsignedNO0
CompletionTextmediumtextYESNULL
VerifiedBuildintsignedNO0
 

Description of fields ​

ID ​

references quest_template.ID  

EmoteOnComplete ​

Emote ID played by the quest ender NPC when all quest objectives are completed.  

EmoteOnIncomplete ​

Emote ID played by the quest ender NPC if any of the quest objectives are incomplete.  

EmoteOnCompleteDelay ​

Delay in milliseconds before triggers the emote ID defined in EmoteOnComplete

EmoteOnIncompleteDelay ​

Delay in milliseconds before triggers the emote ID defined in EmoteOnIncomplete

CompletionText ​

Quest gossip text shown in the final gossip dialogue window when turning in an item delivery quest. The quest item(s) involved in the quest can either be provided by the quest giver or collected by the player.  

VerifiedBuild ​

This field is used by the TrinityDB Team to determine whether a template has been verified from WDB files.

If value is 0 then it has not been parsed yet.

If value is above 0 then it has been parsed with WDB files from that specific client build.

If value is -1 then it is just a place holder until proper data are found on WDBs.

If value is -Client Build then it was parsed with WDB files from that specific client build and manually edited later for some special necessity.