Achievement_criteria_requirement

Back to world database list of tables.

The `achievement_criteria_requirement` table

This table contains what need to be done to complete an achievement criteria.

Structure

Field	Type	Attributes	Can be null	Default	Comments
criteria_id	mediumint(8)	signed	NO	None
type	tintint(3)	unsigned	NO	0
value1	mediumint(8)	unsigned	NO	0
value2	mediumint(8)	unsigned	NO	0

Description of the fields

criteria_id

Column 0 (ID) of achievement_criteria.dbc This DBC contains the achievement_id on 2nd column and will be later extracted to show relations.

type

Describes how to use value1 and value2.

Type	Name
0	TYPE_NONE
1	TYPE_T_CREATURE
2	TYPE_T_PLAYER_CLASS_RACE
3	TYPE_T_PLAYER_LESS_HEALTH
4	TYPE_T_PLAYER_DEAD
5	TYPE_S_AURA
6	TYPE_S_AREA
7	TYPE_T_AURA
8	TYPE_VALUE
9	TYPE_T_LEVEL
10	TYPE_T_GENDER
11	TYPE_DISABLED
12	TYPE_MAP_DIFFICULTY
13	TYPE_MAP_PLAYER_COUNT
14	TYPE_T_TEAM
15	TYPE_S_DRUNK
16	TYPE_HOLIDAY
17	TYPE_BG_LOSS_TEAM_SCORE
18	TYPE_INSTANCE_SCRIPT
19	TYPE_S_EQUIPED_ITEM_LVL
20	TYPE_REQUIRE_NTH_BIRTHDAY
21	TYPE_REQUIRE_KNOWN_TITLE

OtherFields

Depending on what Type was set, the meaning and use for the following fields varies. TYPE_T are for targets and TYPE_S are for sources

• TYPE_T_CREATURE = 1
  • value1: Target creature_template.entry

• ’’’TYPE_T_PLAYER_CLASS_RACE = 2 ‘’’
  • value1: Target Player class
  • value2: Target Player race

• ’’’TYPE_T_PLAYER_LESS_HEALTH = 3 ‘’’
  • value1: Target Health percentage

• ’’’TYPE_T_PLAYER_DEAD = 4 ‘’’
  • value1: Team value the source player and target dead player must both meet

• ’’’TYPE_S_AURA = 5 ‘’’
  • value1: Spell ID
  • value2: Effect index

• ’’’TYPE_S_AREA = 6 ‘’’
  • value1: Area ID from AreaTable.dbc

• ’’’TYPE_T_AURA = 7 ‘’’
  • value1: Spell ID
  • value2: Effect index

• TYPE_VALUE = 8
  • value1: Min Value. Value provided with achievement update must be not less that limit

• TYPE_T_LEVEL = 9
  • value1: Target Min Level

• TYPE_T_GENDER = 10
  • value1: Gender: 0=Male, 1=Female

• TYPE_DISABLED = 11

Used to prevent achievement criteria to complete if not all requirements are implemented and listed in this table

• TYPE_MAP_DIFFICULTY = 12
  • value1: Map difficulty:

Description	Flag
DUNGEON_DIFFICULTY_NORMAL	0
DUNGEON_DIFFICULTY_HEROIC	1
RAID_DIFFICULTY_10MAN_NORMAL	0
RAID_DIFFICULTY_25MAN_NORMAL	1
RAID_DIFFICULTY_10MAN_HEROIC	2
RAID_DIFFICULTY_25MAN_HEROIC	3

• TYPE_MAP_PLAYER_COUNT = 13
  • value1: Count. For criteria "with less than %u people in the zone"

• TYPE_T_TEAM = 14
  • value1: Team: HORDE = 67, ALLIANCE = 469

• TYPE_S_DRUNK = 15
  • value1: Druken State. DRUNKEN_SOBER = 0, DRUNKEN_TIPSY = 1, DRUNKEN_DRUNK = 2, DRUNKEN_SMASHED = 3

• TYPE_HOLIDAY = 16
  • value1: Holiday ID which must be active from Holiday.dbc and game_event

• ’’’TYPE_BG_LOSS_TEAM_SCORE = 17 ‘’’
  • value1: min_score
  • value2: max_score

• ’’’TYPE_INSTANCE_SCRIPT = 18 ‘’’

Make instance script call for check current criteria requirements fit

• ’’’TYPE_S_EQUIPED_ITEM_LVL = 19 ‘’’
  • value1: item_level
  • value2: item_quality

For equipped item in slot `misc1` to item level and quality

• ’’’TYPE_REQUIRE_NTH_BIRTHDAY = 20 ‘’’
  • value1: nth-birthday

• ’’’TYPE_CRITERIA_REQUIRE_KNOWN_TITLE = 21 ‘’’
  • value1: title_id