AzerothCore
Posts (Latest 10 updated) :
Read all

quest_details

 

Table: quest_details

This table handles Quest NPC emotes with emote delays.

 

Field Type Attributes Key NULL Default Comment
ID mediumint(8) unsigned PRI NO 0 Unique ID (quest_template.ID)
Emote1 smallint(5) unsigned   NO 0 Quest NPC Emote
Emote2 smallint(5) unsigned   NO 0 Quest NPC Emote
Emote3 smallint(5) unsigned   NO 0 Quest NPC Emote
Emote4 smallint(5) unsigned   NO 0 Quest NPC Emote
EmoteDelay1 int(10) unsigned   NO 0 Emote delay in milliseconds
EmoteDelay2 int(10) unsigned   NO 0 Emote delay in milliseconds
EmoteDelay3 int(10) unsigned   NO 0 Emote delay in milliseconds
EmoteDelay4 int(10) unsigned   NO 0 Emote delay in milliseconds
VerifiedBuild smallint(5)     NO 0 Game client Build number or manually set value

 

Description of the fields:

ID

Unique ID (quest_template.ID)

Emote1

Emote (from Emotes.dbc) played by NPC

Emote2

Emote (from Emotes.dbc) played by NPC

Emote3

Emote (from Emotes.dbc) played by NPC

Emote4

Emote (from Emotes.dbc) played by NPC

EmoteDelay1

Emote delay in milliseconds

EmoteDelay2

Emote delay in milliseconds

EmoteDelay3

Emote delay in milliseconds

EmoteDelay4

Emote delay in milliseconds

VerifiedBuild

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

  • If value is 0, it has not been parsed yet.
  • If value is > 0, it has been parsed with WDB files from that specific Client Build.
  • If value is -1, it is just a place holder until proper data are found on WDBs.
  • If value is -Client Build, it was parsed with WDB files from that specific client build and manually edited later for some specific necessity.