quest_template

Table: quest_template

Contains all basic definitions of available quests.

Structure

Description of the fields

ID

The quest ID. This column is the Primary Key for the Table. Each quest ID must be unique!

QuestType

Accepted values: 0, 1, 2 or 3. Their meaning is described in table below.

QuestLevel

Level of quest. Player receives full experience amount only if their level is less than or equal to Level+5. If Level is set to -1, the player's level will be used as (Quest)Level for the experience calculation.

MinLevel

Minimum level at which a player can get the quest.

MaxLevel

Maximum level at which a player can get the quest.

QuestSortID

This field defines under what category the quest falls in the quest log.

If value > 0 then value is Zone IDs taken from AreaTable.dbc.

if value < 0 then (-value) is quest sort id: (in general profession or class quests. Also see quest_template#RequiredSkillPoints ) Value is ID from QuestSort.dbc

QuestInfoID

These values are ID taken from QuestInfo.dbc

SuggestedGroupNum

Recommended number of players to do the quest together.

LimitTime

Time in seconds that the player has to complete this quest.

RequiredClasses

Classes required to get the quest. 0 means the quest is available for all classes.
This field is a bitmask, you can combine class values. See ChrClasses.dbc

AllowableRaces

Races allowed to get the quest. 0 means the quest is accessible for all races. Field value is a decimal value which must transform to an 8 bits binary in order to be understandable. In binary form, each different bit represents a different race. They're assigned as follows :

Race

These values are 2^ID taken from ChrRaces.dbc

Examples:

0,1791 = All Races

690 (2 + 16 + 32 + 128 + 512) = Horde Quest

1101 (1 + 4 + 8 + 64 + 1024) = Alliance Quest

Mist of Pandaria and all Expansions after:

33555378 (33554432 + 256 + 128 + 32 + 16 + 2 + 512)  = Horde

18875469 (16777216 + 2097152 + 1024 + 64 + 8 + 4 + 1) = Alliance

RequiredSkillId

Skill required to know to accept the quest. See SkillIne.dbc
0 means no skill is required.

RequiredSkillPoints

Skill points required to have in order to accept the quest.

RepObjectiveFaction

Faction ID for an objective to achieve a certain reputation value with. See Faction.dbc

RepObjectiveValue

Reputation value that the player must achieve with the faction in quest_template#RepObjectiveFaction as part of the quest objectives.

RequiredMinRepFaction

Faction ID for reputation requirement. See Faction.dbc

RequiredMinRepValue

Players must have this reputation or higher in order to receive the quest.

RequiredMaxRepFaction

The Faction ID for the faction that controls the maximum reputation value that the player can have and still get the quest. See Faction.dbc

RequiredMaxRepValue

The maximum reputation value that the player can have with a faction and still get the quest. If the player has more reputation than the value in this field, the quest will not be able to be taken anymore.

PrevQuestId

if value > 0: Contains the previous quest id, that must be completed before this quest can be started.

If value < 0: Contains the parent quest id, that must be active before this quest can be started.

See the examples section for examples.

NextQuestId

If value > 0: Contains the next quest id, if PrevQuestId of that quest is not sufficient.

If value < 0: Contains the sub quest id, if PrevQuestId of that quest is not sufficient. If quest have many alternative next quests (class specific quests lead from single not class specific quest) field PrevQuestId in next quests can used for setting this dependence.

See the examples section for examples.

ExclusiveGroup

if ExclusiveGroup > 0

Allows to define a group of quests of which only one may be chosen and completed. E.g. if from quests 1200, 1201 and 1202 only one should be allowed to be chosen, insert 1200 into ExclusiveGroup of all 3 quests.

if ExclusiveGroup < 0

Allows to define a group of quests of which all must be completed and rewarded to start next quest. E.g. if quest 1000 dependent from one of quests 1200, 1201 and 1202 and all this quests have same negative exclusive group then all this quest must be completed and rewarded before quest 1000 can be started.

Note: All quests that use an ExclusiveGroup must also have entries in pool_template and pool_quest in order for the core to choose one randomly. See the examples section for examples.

RewardNextQuest

(Old field name: NextQuestIdChain)

The quest entry from a creature or gameobject that ends a quest and starts a new one. The result is, that if you end the quest, the new quest instantly appears from the quest giver.

See the examples section for examples.

RewardXPDifficulty

According to the quest_template#Level, the basic experience with index RewardXPDifficulty is taken from QuestXP.dbc.

This field also controls the XP given as the XP is calculated from the value in this field by the following formula. If the quest is repeatable, XP will be given only once. The total XP that a character will receive is also affected by the level difference between the character's level and the quest's level.

The formula for calculating XP from the value in this field:
QuestLevel >= 65: XP = RewMoneyMaxLevel / 6.0
QuestLevel h1. 64: XP = RewMoneyMaxLevel / 4.8
QuestLevel 63: XP = RewMoneyMaxLevel / 3.6
QuestLevel h1. 62: XP = RewMoneyMaxLevel / 2.4
QuestLevel 61: XP = RewMoneyMaxLevel / 1.2
QuestLevel <= 60: XP = RewMoneyMaxLevel / 0.6

RewardMoney

Money earned by completing the quest (if value > 0) or money requirement to complete the quest (if value < 0) .

RewardBonusMoney

The money a character at level 80 would get when they complete this quest.

RewardSpell

Spell that is shown to be casted on quest completion in the quest log. Note that this spell will NOT be casted if quest_template#RewardSpellCast is non-zero. The spell in the other field will be casted instead, in which case the spell here only serves as the visual in the quest log.

NOTE: This field comes straight from the WDB and should not be changed.

RewardSpellCast

Spell that will always be casted at player when completing the quest. This can be learn spell and player learned some spell in result, or buff spell, for example. If this field is non-zero then this spell will ALWAYS be casted and the spell in quest_template#RewardSpell will not.

NOTE: This field comes straight from the WDB and should not be changed.

RewardMailTemplateId

If the quest gives as a reward an item from a possible list of items, the ID here corresponds to the proper loot template in quest_mail_loot_template. According to the rules in that loot template, items "looted" will be sent by mail at the completion of the quest.

RewardMailDelay

How many seconds to wait until the mail is sent to the character that turned in a quest rewarding items from a loot template defined in quest_template#RewardMailTemplateId

RewardHonor

Number of honorable kill honor rewarded for completing this quest.

Example: An example value is 15 for quest 8388: At level 80 an honorable kill is 124 honor worth. Multiply this with 15 and you receive 1860, after the multiplication the value is rounded up. So the honor rewarded at level 80 is 1860 for this quest.

RewardHonorMultiplier

Multiplies quest_template#RewardHonor, so if value is 2, it will give double.

WARNING: If this field is 1 and quest_template#RewardHonor is 0, the quest will reward default honor kill value (124 honor at level 80)

StartItem

Items given by the quest giver at beginning of the quest. Items will be deleted when quest is abandoned.

SourceSpellId

Spell cast on player when quest is started. Can be a buff or a learning spell.

Flags

This flag field defines more specifically the type of quest it is. Aside from the daily flag and sharable flag, this field is used just for grouping purposes and NOT for any other quest requirements. The quest requirements are calculated from non-zero values in other quest template fields. Also, while some of these flags are known, others have yet an unknown purpose and the comments below is simply guesswork on them.

Like all flag based fields, QuestFlags can be added for the different types of quest.

Note that some flags may not be supported by core.

SpecialFlags

This has been moved to quest_template_addon.SpecialFlags

This field is a bitmask and is for controlling server side quest functions. This data blizz keeps serverside, and is not sent to the client, so we have to populate the field manually.

• 0: No extra requirements

• 1: Makes the quest repeatable.
• 2: Makes the quest only completable by some external event (an entry in areatrigger_involvedrelation, spell effect quest complete or an entry in spell_scripts with command 7 as some examples)
• 4: Make quest auto-accept. As of patch 3.3.5a only quests in the starter area need this flag.

• 8: Only used for Dungeon Finder quests
• 16: Makes the quest monthly
• 32: The quest requires RequiredOrNpcGo killcredit but NOT kill (a spell cast)

RewardTitleId

The title the character will receive upon completion of the quest. See CharTitles.dbc

RequiredPlayerKills

Displays how much players you need to kill betd class=td class=a class=/td data-linked-resource-default-alias=fore completing the quest.

RewardTalents

Will give X bonus talents to the player completed the quest. Leave'"0"for No Bonus Talent Points.''

RewardArenaPoints

Will Give X Arena Points to the player that completes the quest. Leave"0"For no Arena Points Reward.

RewardChoiceItemId

Id of item available for reward choice.
Number of Charges in rewarded item available.

RewardChoiceItemCount

Will choose how many items will be added for reward. E.g "RewardChoiceItemId" is the reward item and "RewardChoiceItemCount" is the count of how many items will be added as a reward.

RewardItemId

item Id given for reward (no choice).

RewardItemCount

field-no-description|46

RewardFactionId

Faction Id (from Faction.dbc) for which the quest give reputation points.
Number of gain or lost reputation points for Faction at quest completion. This is special reputation rewarding. Normal reputation reward to quest rewarding creature faction calculated and added automatically.

RewardFactionValueId

This field is used for reputation lookup in QuestFactionReward.dbc if quest_template#RewardFactionValueId is 0. Value X in this field indicates RepX column of QuestFactionReward.dbc. If RewardRepValueId is positive, reputation from the first row of QuestFactionReward.dbc will be used, for negative values the second row is used.

RewardFactionValueIdOverride

This field is used to give reputation values not present in QuestFactionReward.dbc or to override them if quest_template#RewardRepValueId is wrong for some reason. The value in this field is 100× the intended reputation reward (if you want to give 400 rep, put 40000 in RewardFactionValueIdOverride).

POIContinent

MapId of a quest point of interest (POI - Point Of Interest). POI will be shown on the map when quest is active.

POIx

X coordinate of quest POI.

POIy

Y coordinate of quest POI.

POIPriority

TODO

Title

Title of the quest.

Objectives

Objectives of the quest. If empty, quest is an auto-complete quest that can be immediately finished without accepting it first.

Details

The quest text. You can use certain placeholders that will be filled in in-game: $B - line break, $N - name, $R - race, $C - class, $Gmale:female; (male and female can be replace with any synonymn you want, but the order must stay the same. IE: boy:girl / man:woman / sir:madam / dude:chick)

EndText

field-no-description|57

OfferRewardText

First text send to the player by the NPC when completing the quest. You can use certain placeholders that will be filled in in-game: $B - line break, $N - name, $R - race, $C - class, $Gmale:female; (male and female can be replace with any synonymn you want, but the order must stay the same. IE: boy:girl / man:woman / sir:madam / dude:chick)

RequestItemsText

Text sent to player when the player tries to talk to the NPC with the quest active but incomplete. (The text under the "Progress" title in Wowhead.) You can use certain placeholders that will be filled in in-game: $B - line break, $N - name, $R - race, $C - class, $Gmale:female; (male and female can be replace with any synonymn you want, but the order must stay the same. IE: boy:girl / man:woman / sir:madam / dude:chick)

CompletedText

field-no-description|59

RequiredNpcOrGo

Value > 0:required creature_template ID the player needs to kill/cast on in order to complete the quest.
Value < 0:required gameobject_template ID the player needs to cast on in order to complete the quest.
If*RequiredSpellCast*is != 0, the objective is to cast on target, else kill.
NOTE: If RequiredSpellCast is != 0 and the spell has effects Send Event or Quest Complete, this field may be left empty.

RequiredNpcOrGoCount

The number of times the creature or gameobject must be killed or casted upon.

RequiredSourceItemId

Item ID that is needed indirectly by the quest. For example, the quests asks for item X but the only way to get item X is by activating item Y; however, item Y is also a quest item. Therefore you set item Y's ID in this field. This requirement will not appear in the quest text, it is just for the core to know when to drop a quest item that isn't in the RequiredItemId field but is still needed by the quest.

RequiredSourceItemCount

The maximum number of copies of the item in RequiredSourceItemId that can be picked up (and dropped by the core).

RequiredItemId
Item_template tc2

Id of required item to complete the quest.

RequiredItemCount

Amount of required items

RequiredSpell

Spell Id required to cast on quest_template#RequiredNpcOrGo to update Objective.

ObjectiveText

Used to define non-standard objective texts, that show up in the questlog. Example, "Heal fallen warrior" and the number gets added by Count values.

DetailsEmote

field-no-description|69

DetailsEmoteDelay

Emote delay in ms

EmoteOnIncomplete

field-no-description|71

EmoteOnComplete

Emote played by the related NPC at the time all quest objects are completed.

OfferRewardEmote

Emote played by the NPC at the time the character is rewarded for the quest.

OfferRewardEmoteDelay

Emote delay in ms

WDBVerified

Examples dealing with quests

Always use PrevQuestId before using NextQuestId. NextQuestId is considered optional and to be used only when PrevQuestId is not sufficient

Basic quest

Single, stand-alone quest with no prerequisites

Prequest

When this quest require another quest to be rewarded

Chain of quests

Player get quests in a strict chain that must be completed in a specific order.

Chain of quests with multiple start quests.

Player should only be allowed to complete one of three possible

Chain of quests with multiple start quests.

Player must complete all three initial quests before D becomes available

Quests with split and a child quest

Completing A unlocks B and C that can be done at the same time. They both need to be completed before D becomes available. X is needed to obtain item for C and this quest should only be available if C is active

Multiple quest chains, leading to one final quest

Player may complete (not required to) X, but has to complete all three quest chains before final quest becomes available

Complicated

Player must first complete A, then B to unlock the chain from C to E. Three other quests in a group will also be unlocked, those can be done at the same time. The three grouped quests must all be completed before I becomes available. Completion of E and I is required to obtain the final quest.

Impossible - many quests may unlock many

Player can choose between two alternative chains (Chain A or B, but not both chains). A2 or B2 should unlock C, D and E when complete. When all three complete, F should be unlocked. If player get A3 or B3 after complete F, depends on if chain A or B was chosen

Note:

If player can choose between chain A or B may be determined by faction status (aldor or scryer), using ReqMinRepFaction = 1. Player should not be able to be neutral+1 with both at the same time. This may be the common threshold to obtain aldor or scryer quests (this is unsure). If that is the case, only the unlock of C, D and E after complete A2 or B2 is the impossible part._Note 2: With the Conditions table now every quest chain is possible.''

/table