quest_request_items

Table: quest_request_items

This table basically handles 3 quest details:

NPC Emote when quest is completed
NPC Emote when quest is incomplete
Completion text for quests requiring quest items

Field	Type	Attributes	Key	NULL	Default	Comment

Field	Type	Attributes	Key	NULL	Default	Comment
ID	mediumint(8)	unsigned	PRI	NO	0	Unique ID (quest_template.ID)
EmoteOnComplete	smallint(5)	unsigned		NO	0	Quest ender NPC Emote
EmoteOnIncomplete	smallint(5)	unsigned		NO	0	Quest ender NPC Emote
CompletionText	text	utf8_general_ci		YES	NULL	Quest completion text
VerifiedBuild	smallint(5)			NO	0	Game client Build number

Description of the fields:

ID

Quest ID for quests showing a completion text upon turning in an item delivery quest.
Primary Key for this table. Each quest ID must be unique.

EmoteOnComplete

Emote (from Emotes.dbc) played by the quest ender NPC when all quest objectives are completed.

EmoteOnIncomplete

Emote (from Emotes.dbc) played by the quest ender NPC if any of the quest objectives are incomplete.

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 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.