antz

NOTE: This page is auto-generated from the MAGNET Online Packet documentation Editor module (MOPE), Any changes made directly to this page will be lost when it is regenerated. Description of the MangosThree packet CMSG_ADD_FRIEND Usage Informs server that a player character has added another player's character to their Friends list. Opcode Values Description Value Decimal Value 25895 Hex Value 0x6527 Packet Length 0* - Length can vary Packet Structure Follows: Field Name Field Type Field Size Notes friendName string * friendNote string * Packet Example TODO: Example needed auto-generated by the getMaNGOS.eu MAGNET mope module

NOTE: This page is auto-generated from the MAGNET Online Packet documentation Editor module (MOPE), Any changes made directly to this page will be lost when it is regenerated. Description of the MangosThree packet CMSG_ACTIVE_PVP_CHEAT Usage Opcode Values Description Value Decimal Value 5018 Hex Value 0x139A Packet Length 0 Packet Structure Follows: Field Name Field Type Field Size Notes No fields are currently defined! - if you know the layout, please advise us - or ask for access to MAGNET so that you can enter them yourself Packet Example TODO: Example needed auto-generated by the getMaNGOS.eu MAGNET mope module

NOTE: This page is auto-generated from the MAGNET Online Packet documentation Editor module (MOPE), Any changes made directly to this page will be lost when it is regenerated. Description of the MangosThree packet CMSG_ACTIVATETAXIEXPRESS Usage Return a list of Flightpoint nodes Opcode Values Description Value Decimal Value 1301 Hex Value 0x0515 Packet Length 32* - Length can vary Packet Structure Follows: Field Name Field Type Field Size Notes nodeCount uint32 (default) 32 node uint32 (default) 32* There will be nodeCount number of nodes present in the packet. Packet Example TODO: Example needed auto-generated by the getMaNGOS.eu MAGNET mope module

NOTE: This page is auto-generated from the MAGNET Online Packet documentation Editor module (MOPE), Any changes made directly to this page will be lost when it is regenerated. Description of the MangosThree packet CMSG_ACTIVATETAXI Usage This is called when the player selects where to fly to. Opcode Values Description Value Decimal Value 28166 Hex Value 0x6E06 Packet Length 0 Packet Structure Follows: Field Name Field Type Field Size Notes No fields are currently defined! - if you know the layout, please advise us - or ask for access to MAGNET so that you can enter them yourself Packet Example TODO: Example needed auto-generated by the getMaNGOS.eu MAGNET mope module

NOTE: This page is auto-generated from the MAGNET Online Packet documentation Editor module (MOPE), Any changes made directly to this page will be lost when it is regenerated. Description of the MangosThree packet CMSG_ACCEPT_TRADE Usage Indicates player character has clicked the "Accept" button in Item Trade window while engaged in a trade session with another player. Opcode Values Description Value Decimal Value 28944 Hex Value 0x7110 Packet Length 0 Packet Structure Follows: Field Name Field Type Field Size Notes No fields are currently defined! - if you know the layout, please advise us - or ask for access to MAGNET so that you can enter them yourself Packet Example TODO: Example needed auto-generated by the getMaNGOS.eu MAGNET mope module

NOTE: This page is auto-generated from the MAGNET Online Packet documentation Editor module (MOPE), Any changes made directly to this page will be lost when it is regenerated. Description of the MangosThree packet CMSG_ACCEPT_LEVEL_GRANT Usage test 12 Opcode Values Description Value Decimal Value 517 Hex Value 0x0205 Packet Length 0 Packet Structure Follows: Field Name Field Type Field Size Notes No fields are currently defined! - if you know the layout, please advise us - or ask for access to MAGNET so that you can enter them yourself Packet Example CMSG_ACCEPT_LEVEL_GRANT Length = ???? |------------------------------------------------|----------------| |00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F |0123456789ABCDEF| |------------------------------------------------|----------------| |00 0C 3D 00 00 00 A2 41 59 00 00 00 00 00 |..=....AY..... | ------------------------------------------------------------------- auto-generated by the getMaNGOS.eu MAGNET mope module

This is the early attempt to publically document the packets used in MaNGOS MaNGOS has existed for over 10 years and noone has ever attempted this before !! - There is a ton of stuff missing..... and it's up to us to finish documenting it all

Goals for 2019 For 2019 the following are what we would like to achieve: Release Version 22 for Zero, One, Two and Three containing all the recent updates and fixes we have. Redo the server commands to make them a bit more standard and obvious. Break out AHBot into its own daemon process Develop a mangos update daemon, which allows the ability to apply DB content and minor updates automatically Normalise the character DB and remove data blob fields Move some hardcoded values from the core into the DB, possibly some enums as well. Implement Stormlib library for Zero, One and Two and remove mlib Apply the Unified Extractor to Three and Four (requires stormlib) Look at removing DBC usage from the Core and change the extraction process to include importing into a DB for use by the core. Including Multiple locale support. This would facilitate the removal of stormlib / mlib from the core and only be needed by the extraction tools. Look at Adapting EAI to match SAI functionality. As well as some of the more obvious ones: Continue to standardise the code across the cores where its appropriate to do so. Document where it differs and why. Clear down reported bugs on the Project Tracker. Improve the World Database with updates and corrections. Improve the Wiki Documentation. Include some example Eluna scripts to assist those starting out learning to script with Eluna. Include some custom Eluna scripts to help showcase it's abilities. Finally, we would like to get into a twice yearly Release cycle of more major releases. MangosVB (Formerly Spurious) RoadMap for 2017 Add RealmDB from c++ Mangos and modifying MangosVB to be compatible with it. Once done, this will be linked via a git submodule Work out how to get MangosVB to use the standard Mangos map format. Finishing warden functionality (so it can use/read signatures from DB) Merge all of the changes from Zero to One and Two Investigate into voice functionality for One / Two Doing spells.. implementing them like stealth and getting a proper DB script system in place.

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'achievement_criteria_requirement' table for MaNGOSTwo This table contains what needs to be done to complete an achievement criteria. Table Notes This table uses the 'MyISAM' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes criteria_id mediumint(8) NO PRI NULL Matching ID from achievement_criteria.dbc type tinyint(3) unsigned NO PRI '0' The Type of Criteria value1 mediumint(8) unsigned NO '0' value2 mediumint(8) unsigned NO '0' Description of the fields criteria_id mediumint(8) Column 0 (ID) of [See achievement_criteria.dbc] This DBC contains the achievement_id on 2nd column and will be later extracted to show relations. type tinyint(3) unsigned The Type of Criteria Type Id Critieria Name Value1 Value2 0 TYPE_NONE 1 TYPE_T_CREATURE Target creature_template.entry 2 TYPE_T_PLAYER_CLASS_RACE Target Player Class Target Player Race 3 TYPE_T_PLAYER_LESS_HEALTH Target Health percentage 4 TYPE_T_PLAYER_DEAD Team value the source player and target dead player must both meet 5 TYPE_S_AURA Spell Id Effect Index 6 TYPE_S_AREA Area Id from [See AreaTable.dbc] 7 TYPE_T_AURA Spell Id Effect Index 8 TYPE_VALUE Min Value. Value provided with achievement update must be not less that limit 9 TYPE_T_LEVEL Target Min Level 10 TYPE_T_GENDER Gender: 0=Male, 1=Female 11 TYPE_DISABLED Used to prevent achievement criteria to complete if not all requirements are implemented and listed in this table 12 TYPE_MAP_DIFFICULTY Map Difficulty, Refer to Table Below 13 TYPE_MAP_PLAYER_COUNT Count. For criteria 'with less than %u people in the zone' 14 TYPE_T_TEAM Team: HORDE = 67, ALLIANCE = 469 15 TYPE_S_DRUNK An entry from the Drunken State table below 16 TYPE_HOLIDAY Holiday ID which must be active from (See Holiday.dbc) and game_event 17 TYPE_BG_LOSS_TEAM_SCORE min_score max_score 18 TYPE_INSTANCE_SCRIPT Make instance script call for check current criteria requirements fit 19 TYPE_S_EQUIPED_ITEM_LVL Item Level Item Quality 20 TYPE_REQUIRE_NTH_BIRTHDAY nth-birthday 21 TYPE_REQUIRE_KNOWN_TITLE title_id Map Difficulty Table Description Value 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 Drunken State Table Drunken Name Value DRUNKEN_SOBER 0 DRUNKEN_TIPSY 1 DRUNKEN_DRUNK 2 DRUNKEN_SMASHED 3 value1 mediumint(8) unsigned The meaning of this field is based on the Type, see the table above. value2 mediumint(8) unsigned The meaning of this field is based on the Type, see the table above. auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'achievement_criteria_requirement' table for MaNGOSThree This table contains what needs to be done to complete an achievement criteria. Table Notes This table uses the 'MyISAM' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes criteria_id mediumint(8) NO PRI NULL Matching ID from achievement_criteria.dbc type tinyint(3) unsigned NO PRI '0' The Type of Criteria value1 mediumint(8) unsigned NO '0' value2 mediumint(8) unsigned NO '0' Description of the fields criteria_id mediumint(8) Column 0 (ID) of [See achievement_criteria.dbc] This DBC contains the achievement_id on 2nd column and will be later extracted to show relations. type tinyint(3) unsigned The Type of Criteria Map Difficulty Table Description Value 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 Drunken State Table value1 mediumint(8) unsigned The meaning of this field is based on the Type, see the table above. value2 mediumint(8) unsigned The meaning of this field is based on the Type, see the table above. auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'conditions' table for MaNGOSThree With this table and the new conditions it is possible to create tree like and very complicated combined conditions (like HasAura && (HasItem || HasQuest)) Used in: DBScript gossip_menu gossip_menu_option npc_spellclick_spells spell_area areatrigger_teleport Table Notes This table uses the 'MyISAM' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes condition_entry mediumint(8) unsigned NO PRI NULL 'auto_increment' Identifier type tinyint(3) NO MUL '0' Type of the condition. value1 mediumint(8) unsigned NO '0' Data field One for the condition. value2 mediumint(8) unsigned NO '0' Data field Two for the condition. comments varchar(200) YES {Blank String} Description of the fields condition_entry mediumint(8) unsigned Identifier type tinyint(3) Type of the condition: ID Type Description -3 CONDITION_NOT Used to evaluate if another condition is NOT true. See Note 1 -2 CONDITION_OR Used to evaluate if condition OR condition is true. See Note 1 -1 CONDITION_AND Used to evaluate if condition AND condition is true. See Note 1 0 CONDITION_NONE This condition is not used at all. Always returns true. 1 CONDITION_AURA Checks target currently has the specified aura on him/her. 2 CONDITION_ITEM Checks if the player has the required amount (value2) of items in his/hers inventory. 3 CONDITION_ITEM_EQUIPPED Checks if the player has the specified item equipped. 4 CONDITION_AREAID Checks if the player is within the specified area/zone. 5 CONDITION_REPUTATION_RANK_MIN Checks if the player has the minimum required reputation rank with a specific faction. 6 CONDITION_TEAM Checks what team the target is a member of (Alliance or Horde). 7 CONDITION_SKILL Checks if the player has the required minimum skill value of the specified skill. 8 CONDITION_QUESTREWARDED Checks if the player has complete the specified quest. 9 CONDITION_QUESTTAKEN Checks if the player has taken the quest (as in has it in his/hers quest log.) and not completed it yet. 10 CONDITION_AD_COMMISSION_AURA TODO 11 CONDITION_NO_AURA Checks if the target DOES NOT currently have the specified aura on him/her. 12 CONDITION_ACTIVE_GAME_EVENT Checks if a game event is currently active. 13 CONDITION_AREA_FLAG Checks if area_flag is present in current area (if area_flag set != 0) AND if not_have_flag is not present in current area (if not_have_flag != 0) 14 CONDITION_RACE_CLASS Checks if the target is a certain race AND/OR class. 15 CONDITION_LEVEL Checks the targets level. 16 CONDITION_NOITEM Checks if the player DOES NOT have the required amount (value2) of items in his/hers inventory. 17 CONDITION_SPELL Checks if the target has or hasn't (value2) the specified spell. 18 CONDITION_INSTANCE_SCRIPT SD3 based condition 19 CONDITION_QUESTAVAILABLE Checks if the specified quest is available (can start it) for the player. 20 CONDITION_ACHIEVEMENT Has or has no special achievement. 21 CONDITION_ACHIEVEMENT_REALM Realm wide achievement (like 20 above but realm wide). 22 CONDITION_QUEST_NONE Checks if the player has NOT taken the quest AND has NOT been rewarded for the quest. 23 CONDITION_ITEM_WITH_BANK Checks if the player has the required amount (value2) of items in his/hers inventory OR bank. 24 CONDITION_NOITEM_WITH_BANK Checks if the player DOES NOT have count (value2) of items in his/hers inventory OR bank. 25 CONDITION_NOT_ACTIVE_GAME_EVENT Checks if a game event is currently NOT active. 26 CONDITION_ACTIVE_HOLIDAY Checks if a holiday is active 27 CONDITION_NOT_ACTIVE_HOLIDAY Checks if a holiday is not active 28 CONDITION_LEARNABLE_ABILITY Checks if the player can learn ability - using minimum skill value from [See SkillLineAbility.dbc] If the player has spell or has item (when defined) the condition will evaluate to false. 29 CONDITION_SKILL_BELOW TODO 30 CONDITION_REPUTATION_RANK_MAX Checks if the player has a higher reputation rank than specified a faction. 31 CONDITION_COMPLETED_ENCOUNTER Checks if an encounter has been completed. 32 CONDITION_SOURCE_AURA Checks if the source of the condition (like looted npc) has an aura. 33 CONDITION_LAST_WAYPOINT Checks the waypoint-state of the source of the condition. 34 CONDITION_XP_USER Checks if a player has turned XP earning on/off 35 CONDITION_GENDER Checks the gender of a player. 36 CONDITION_DEAD_OR_AWAY TODO 37 CONDITION_CREATURE_IN_RANGE TODO 38 CONDITION_PVP_SCRIPT TODO 39 CONDITION_SPAWN_COUNT Returns if specified count of creature entry exists on map. 36 CONDITION_DEAD_OR_AWAY Checks if a player, a player's group, all players in an instance, or a creature is dead or left the map. Note 1: Meta-Condition types CONDITION_AND (-1) and CONDITION_OR (-2) which are used as: value1 (as condition_entry) AND / OR value2 (as condition_entry). With these meta-conditions it is possible to create tree like and very complicated combined conditions (like HasAura && (HasItem || HasQuest)) value1 mediumint(8) unsigned Data field One for the condition. value2 mediumint(8) unsigned Data field Two for the condition. comments varchar(200) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'conditions' table for MaNGOSTwo With this table and the new conditions it is possible to create tree like and very complicated combined conditions (like HasAura && (HasItem || HasQuest)) Used in: DBScript gossip_menu gossip_menu_option npc_spellclick_spells spell_area areatrigger_teleport Table Notes This table uses the 'MyISAM' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes condition_entry mediumint(8) unsigned NO PRI NULL 'auto_increment' Identifier type tinyint(3) NO MUL '0' Type of the condition. value1 mediumint(8) unsigned NO '0' Data field One for the condition. value2 mediumint(8) unsigned NO '0' Data field Two for the condition. comments varchar(200) YES {Blank String} Description of the fields condition_entry mediumint(8) unsigned Identifier type tinyint(3) Type of the condition: ID Type Description -3 CONDITION_NOT Used to evaluate if another condition is NOT true. See Note 1 -2 CONDITION_OR Used to evaluate if condition OR condition is true. See Note 1 -1 CONDITION_AND Used to evaluate if condition AND condition is true. See Note 1 0 CONDITION_NONE This condition is not used at all. Always returns true. 1 CONDITION_AURA Checks target currently has the specified aura on him/her. 2 CONDITION_ITEM Checks if the player has the required amount (value2) of items in his/hers inventory. 3 CONDITION_ITEM_EQUIPPED Checks if the player has the specified item equipped. 4 CONDITION_AREAID Checks if the player is within the specified area/zone. 5 CONDITION_REPUTATION_RANK_MIN Checks if the player has the minimum required reputation rank with a specific faction. 6 CONDITION_TEAM Checks what team the target is a member of (Alliance or Horde). 7 CONDITION_SKILL Checks if the player has the required minimum skill value of the specified skill. 8 CONDITION_QUESTREWARDED Checks if the player has complete the specified quest. 9 CONDITION_QUESTTAKEN Checks if the player has taken the quest (as in has it in his/hers quest log.) and not completed it yet. 10 CONDITION_AD_COMMISSION_AURA TODO 11 CONDITION_NO_AURA Checks if the target DOES NOT currently have the specified aura on him/her. 12 CONDITION_ACTIVE_GAME_EVENT Checks if a game event is currently active. 13 CONDITION_AREA_FLAG Checks if area_flag is present in current area (if area_flag set != 0) AND if not_have_flag is not present in current area (if not_have_flag != 0) 14 CONDITION_RACE_CLASS Checks if the target is a certain race AND/OR class. 15 CONDITION_LEVEL Checks the targets level. 16 CONDITION_NOITEM Checks if the player DOES NOT have the required amount (value2) of items in his/hers inventory. 17 CONDITION_SPELL Checks if the target has or hasn't (value2) the specified spell. 18 CONDITION_INSTANCE_SCRIPT SD3 based condition 19 CONDITION_QUESTAVAILABLE Checks if the specified quest is available (can start it) for the player. 20 CONDITION_ACHIEVEMENT Has or has no special achievement. 21 CONDITION_ACHIEVEMENT_REALM Realm wide achievement (like 20 above but realm wide). 22 CONDITION_QUEST_NONE Checks if the player has NOT taken the quest AND has NOT been rewarded for the quest. 23 CONDITION_ITEM_WITH_BANK Checks if the player has the required amount (value2) of items in his/hers inventory OR bank. 24 CONDITION_NOITEM_WITH_BANK Checks if the player DOES NOT have count (value2) of items in his/hers inventory OR bank. 25 CONDITION_NOT_ACTIVE_GAME_EVENT Checks if a game event is currently NOT active. 26 CONDITION_ACTIVE_HOLIDAY Checks if a holiday is active 27 CONDITION_NOT_ACTIVE_HOLIDAY Checks if a holiday is not active 28 CONDITION_LEARNABLE_ABILITY Checks if the player can learn ability - using minimum skill value from [See SkillLineAbility.dbc] If the player has spell or has item (when defined) the condition will evaluate to false. 29 CONDITION_SKILL_BELOW TODO 30 CONDITION_REPUTATION_RANK_MAX Checks if the player has a higher reputation rank than specified a faction. 31 CONDITION_COMPLETED_ENCOUNTER Checks if an encounter has been completed. 32 CONDITION_SOURCE_AURA Checks if the source of the condition (like looted npc) has an aura. 33 CONDITION_LAST_WAYPOINT Checks the waypoint-state of the source of the condition. 34 CONDITION_XP_USER Checks if a player has turned XP earning on/off 35 CONDITION_GENDER Checks the gender of a player. 36 CONDITION_DEAD_OR_AWAY TODO 37 CONDITION_CREATURE_IN_RANGE TODO 38 CONDITION_PVP_SCRIPT TODO 39 CONDITION_SPAWN_COUNT Returns if specified count of creature entry exists on map. 36 CONDITION_DEAD_OR_AWAY Checks if a player, a player's group, all players in an instance, or a creature is dead or left the map. Note 1: Meta-Condition types CONDITION_AND (-1) and CONDITION_OR (-2) which are used as: value1 (as condition_entry) AND / OR value2 (as condition_entry). With these meta-conditions it is possible to create tree like and very complicated combined conditions (like HasAura && (HasItem || HasQuest)) value1 mediumint(8) unsigned Data field One for the condition. value2 mediumint(8) unsigned Data field Two for the condition. comments varchar(200) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'conditions' table for MaNGOSOne With this table and the new conditions it is possible to create tree like and very complicated combined conditions (like HasAura && (HasItem || HasQuest)) Used in: DBScript gossip_menu gossip_menu_option npc_spellclick_spells spell_area areatrigger_teleport Table Notes This table uses the 'MyISAM' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes condition_entry mediumint(8) unsigned NO PRI NULL 'auto_increment' Identifier type tinyint(3) NO MUL '0' Type of the condition. value1 mediumint(8) unsigned NO '0' Data field One for the condition. value2 mediumint(8) unsigned NO '0' Data field Two for the condition. comments varchar(200) YES {Blank String} Description of the fields condition_entry mediumint(8) unsigned Identifier type tinyint(3) Type of the condition: ID Type Description -3 CONDITION_NOT Used to evaluate if another condition is NOT true. See Note 1 -2 CONDITION_OR Used to evaluate if condition OR condition is true. See Note 1 -1 CONDITION_AND Used to evaluate if condition AND condition is true. See Note 1 0 CONDITION_NONE This condition is not used at all. Always returns true. 1 CONDITION_AURA Checks target currently has the specified aura on him/her. 2 CONDITION_ITEM Checks if the player has the required amount (value2) of items in his/hers inventory. 3 CONDITION_ITEM_EQUIPPED Checks if the player has the specified item equipped. 4 CONDITION_AREAID Checks if the player is within the specified area/zone. 5 CONDITION_REPUTATION_RANK_MIN Checks if the player has the minimum required reputation rank with a specific faction. 6 CONDITION_TEAM Checks what team the target is a member of (Alliance or Horde). 7 CONDITION_SKILL Checks if the player has the required minimum skill value of the specified skill. 8 CONDITION_QUESTREWARDED Checks if the player has complete the specified quest. 9 CONDITION_QUESTTAKEN Checks if the player has taken the quest (as in has it in his/hers quest log.) and not completed it yet. 10 CONDITION_AD_COMMISSION_AURA TODO 11 CONDITION_NO_AURA Checks if the target DOES NOT currently have the specified aura on him/her. 12 CONDITION_ACTIVE_GAME_EVENT Checks if a game event is currently active. 13 CONDITION_AREA_FLAG Checks if area_flag is present in current area (if area_flag set != 0) AND if not_have_flag is not present in current area (if not_have_flag != 0) 14 CONDITION_RACE_CLASS Checks if the target is a certain race AND/OR class. 15 CONDITION_LEVEL Checks the targets level. 16 CONDITION_NOITEM Checks if the player DOES NOT have the required amount (value2) of items in his/hers inventory. 17 CONDITION_SPELL Checks if the target has or hasn't (value2) the specified spell. 18 CONDITION_INSTANCE_SCRIPT SD3 based condition 19 CONDITION_QUESTAVAILABLE Checks if the specified quest is available (can start it) for the player. 20 CONDITION_ACHIEVEMENT Has or has no special achievement. 21 CONDITION_ACHIEVEMENT_REALM Realm wide achievement (like 20 above but realm wide). 22 CONDITION_QUEST_NONE Checks if the player has NOT taken the quest AND has NOT been rewarded for the quest. 23 CONDITION_ITEM_WITH_BANK Checks if the player has the required amount (value2) of items in his/hers inventory OR bank. 24 CONDITION_NOITEM_WITH_BANK Checks if the player DOES NOT have count (value2) of items in his/hers inventory OR bank. 25 CONDITION_NOT_ACTIVE_GAME_EVENT Checks if a game event is currently NOT active. 26 CONDITION_ACTIVE_HOLIDAY Checks if a holiday is active 27 CONDITION_NOT_ACTIVE_HOLIDAY Checks if a holiday is not active 28 CONDITION_LEARNABLE_ABILITY Checks if the player can learn ability - using minimum skill value from [See SkillLineAbility.dbc] If the player has spell or has item (when defined) the condition will evaluate to false. 29 CONDITION_SKILL_BELOW TODO 30 CONDITION_REPUTATION_RANK_MAX Checks if the player has a higher reputation rank than specified a faction. 31 CONDITION_COMPLETED_ENCOUNTER Checks if an encounter has been completed. 32 CONDITION_SOURCE_AURA Checks if the source of the condition (like looted npc) has an aura. 33 CONDITION_LAST_WAYPOINT Checks the waypoint-state of the source of the condition. 34 CONDITION_XP_USER Checks if a player has turned XP earning on/off 35 CONDITION_GENDER Checks the gender of a player. 36 CONDITION_DEAD_OR_AWAY TODO 37 CONDITION_CREATURE_IN_RANGE TODO 38 CONDITION_PVP_SCRIPT TODO 39 CONDITION_SPAWN_COUNT Returns if specified count of creature entry exists on map. 36 CONDITION_DEAD_OR_AWAY Checks if a player, a player's group, all players in an instance, or a creature is dead or left the map. Note 1: Meta-Condition types CONDITION_AND (-1) and CONDITION_OR (-2) which are used as: value1 (as condition_entry) AND / OR value2 (as condition_entry). With these meta-conditions it is possible to create tree like and very complicated combined conditions (like HasAura && (HasItem || HasQuest)) value1 mediumint(8) unsigned Data field One for the condition. value2 mediumint(8) unsigned Data field Two for the condition. comments varchar(200) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'ahbot_category' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes id bigint(20) NO PRI NULL 'auto_increment' category varchar(45) YES MUL {Blank String} multiplier decimal(20,2) NO NULL max_auction_count bigint(20) NO NULL expire_time bigint(20) NO NULL Description of the fields id bigint(20) Notes: Unique identifier of the category category varchar(45) Notes: An Item category Id multiplier decimal(20,2) Notes: The cost multiplier max_auction_count bigint(20) Notes: The max number of items of this category in the AH. expire_time bigint(20) Notes: The UNIX time when the item will expire. auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'account_data' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes account int(11) unsigned NO PRI '0' type int(11) unsigned NO PRI '0' time bigint(11) unsigned NO '0' data longblob NO NULL Description of the fields account int(11) unsigned type int(11) unsigned time bigint(11) unsigned data longblob auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'ahbot_history' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes id bigint(20) NO PRI NULL 'auto_increment' buytime bigint(20) NO NULL item bigint(20) NO NULL bid bigint(20) NO NULL buyout bigint(20) NO NULL won bigint(20) NO MUL NULL category varchar(45) YES MUL {Blank String} auction_house bigint(20) NO MUL NULL Description of the fields id bigint(20) buytime bigint(20) item bigint(20) bid bigint(20) buyout bigint(20) won bigint(20) category varchar(45) Notes: An Item category Id from the list below: auction_house bigint(20) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'ai_playerbot_names' table for MaNGOSThree 'PlayerbotAI AutoBot names' Table Notes This table uses the 'MyISAM' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes name_id mediumint(8) NO PRI NULL 'auto_increment' name varchar(13) NO UNI {Blank String} gender tinyint(3) unsigned NO NULL race smallint(5) unsigned NO NULL class smallint(5) unsigned NO NULL purpose int(11) unsigned NO NULL priority bit(1) NO NULL in_use bit(1) NO NULL Description of the fields name_id mediumint(8) name varchar(13) gender tinyint(3) unsigned Notes: The Gender of the bot race smallint(5) unsigned Notes: The Race of the bot class smallint(5) unsigned purpose int(11) unsigned priority bit(1) in_use bit(1) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'ahbot_price' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes id bigint(20) NO PRI NULL 'auto_increment' item varchar(45) YES MUL {Blank String} price decimal(20,2) NO NULL auction_house bigint(20) NO NULL Description of the fields id bigint(20) item varchar(45) price decimal(20,2) auction_house bigint(20) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'ai_playerbot_random_bots' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes id bigint(20) NO PRI NULL 'auto_increment' owner bigint(20) NO MUL NULL bot bigint(20) NO MUL NULL time bigint(20) NO NULL validIn bigint(20) YES NULL event varchar(45) YES MUL {Blank String} value bigint(20) YES NULL data varchar(255) YES {Blank String} Description of the fields id bigint(20) owner bigint(20) bot bigint(20) time bigint(20) validIn bigint(20) event varchar(45) value bigint(20) data varchar(255) auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'arena_team' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes arenateamid int(10) unsigned NO PRI '0' name char(255) NO {Blank String} captainguid int(10) unsigned NO '0' type tinyint(3) unsigned NO '0' BackgroundColor int(10) unsigned NO '0' EmblemStyle int(10) unsigned NO '0' EmblemColor int(10) unsigned NO '0' BorderStyle int(10) unsigned NO '0' BorderColor int(10) unsigned NO '0' Description of the fields arenateamid int(10) unsigned name char(255) captainguid int(10) unsigned type tinyint(3) unsigned BackgroundColor int(10) unsigned EmblemStyle int(10) unsigned EmblemColor int(10) unsigned BorderStyle int(10) unsigned BorderColor int(10) unsigned auto-generated by the getMaNGOS.eu MAGNET dbdocs module

NOTE: This page is auto-generated from the MAGNET DBDocs module, Any changes made directly to this page will be lost when it is regenerated. Description of the 'arena_team_stats' table for MaNGOSThree Table Notes This table uses the 'InnoDB' DB Engine The Field definitions follow: Field Name Field Type Nullable Key Default Value Attributes Notes arenateamid int(10) unsigned NO PRI '0' rating int(10) unsigned NO '0' games_week int(10) unsigned NO '0' wins_week int(10) unsigned NO '0' games_season int(10) unsigned NO '0' wins_season int(10) unsigned NO '0' rank int(10) unsigned NO '0' Description of the fields arenateamid int(10) unsigned rating int(10) unsigned games_week int(10) unsigned wins_week int(10) unsigned games_season int(10) unsigned wins_season int(10) unsigned rank int(10) unsigned auto-generated by the getMaNGOS.eu MAGNET dbdocs module