Description of the 'instance_reset' table for MaNGOSZero

This table holds information about the instance reset time.

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

mapid int(11) unsigned

The map ID of the instance. [See Map.dbc]

resettime bigint(40) unsigned

Dungeon reset time in seconds.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'item_instance' table for MaNGOSZero

This table holds individual item instance information for all items currently equipped or in some kind of character bag or bank.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

guid int(11) unsigned

The GUID of the item. This number is unique for each item instance.

owner_guid int(11) unsigned

The GUID of the character who has ownership of this item. [See character.guid]

data longtext

Much like the playerbytes fields in the characters table, this field has many number fields all separated by a space which contain specific individual item information like any enchantments applied to the item, etc.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'item_loot' table for MaNGOSZero

Contains the items associated with a lootable inventory items. This table is populated the first time the player right-clicks to open an item. Rows are deleted when the player either removes an item or destroys the container item.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

guid int(11) unsigned

Global unique ID of the item loot entry.

owner_guid int(11) unsigned

The GUID of the owner. [See character.guid]

itemid int(11) unsigned

Item template entry ID of the item.

amount int(11) unsigned

Total number of the item.

property int(11)

Item random property.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'item_text' table for MaNGOSZero

This table is part of the mail system and holds the text information of every letter.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

id int(11) unsigned

The text entry ID. This number is unique to every text entry in this table.

text longtext

The actual text that was sent as mail using the mail system. There are some special messages that are sent through the mail and therefore use this table but have a special format to them:

Auction won (sent to bidder): "<owner's GUID as hex>:<winning bid in copper>:<buyout price in copper>"

Auction successful (sent to owner): "<bidder's GUID as hex>:<winning bid in copper>:0: <deposit in copper>:<auction cut in copper>"

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'mail' table for MaNGOSZero

This table contains main data about all mails in the game.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

id int(11) unsigned

Unique message id. Every new message gets a new auto incremented id.

messageType tinyint(3) unsigned

The type of the Message:

stationery tinyint(3)

The StationeryID [See Stationery.dbc].

mailTemplateId mediumint(8) unsigned

The Mail Template Id [See MailTemplate.dbc]

sender int(11) unsigned

Guid of the character who sends the mail.

receiver int(11) unsigned

Guid of the character who receives the mail.

subject longtext

The Subject of the mail.

itemTextId int(11) unsigned

The item_text ID of the massage within the mail.

has_items tinyint(3) unsigned

Boolean value showing whether or not atems have been sent.

0 = no item included in the mail.
1 = items included in the mail.

expire_time bigint(40) unsigned

Current Unix Time + Unix Time till expiry.
Example:
current unix time + 86400 (seconds for one day) = expiry date
In this example the mail would expire after one day.

deliver_time bigint(40) unsigned

Current Unix Time + Unix Time till delivery.
Example:
current unix time + 86400 (seconds for one day) = delivery date
In this example the mail would be delivered after one day.

money int(11) unsigned

Amount of money sent.
If you want to send 100 gold 55 silver 33 copper then its 1005533

cod int(11) unsigned

Amount of money needed (COD).

checked tinyint(3) unsigned

checked_flag

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'mail_items' table for MaNGOSZero

This table contains data regarding items from item_instance which are being sent via email.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

mail_id int(11)

The Mail Id [See mail.id].

item_guid int(11)

The GUID of the item.

item_template int(11)

The entry ID of the item in the item_template table.

receiver int(11) unsigned

Guid of the character who receives the mail.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'pet_aura' table for MaNGOSZero

This table contains aura information that is loaded when a pet is loaded, so the auras that were on the pet when the owner character logged out are still kept when they log back in. A spell can have up to three auras, one in each of its effects.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

guid int(11) unsigned

The GUID of the target affected by the aura. [See character.guid]

caster_guid bigint(20) unsigned

The GUID of the player or creature who casted the aura. [See character.guid]

item_guid int(11) unsigned

Guid of the item that is casting the aura on the pet.

spell int(11) unsigned

The spell from which the aura was applied. [See Spell.dbc column 1]

stackcount int(11) unsigned

This is the total number of times the aura can be stacked on the pet.

remaincharges int(11) unsigned

The number of charges remaining on the aura.

basepoints0 int(11)

Primary effect, such as healing.

basepoints1 int(11)

Secondary effect (appears to be only healing related)

basepoints2 int(11)

Secondary effect (appears to be only damage related)

periodictime0 int(11) unsigned

Primary effect over time.

periodictime1 int(11) unsigned

Secondary effect (healing) over time

periodictime2 int(11) unsigned

Secondary effect (damage) over time.

maxduration int(11)

The maximum duration of the aura.

remaintime int(11)

The time remaining in seconds on the aura. -1 means that the aura is indefinite.

effIndexMask int(11) unsigned

The effect index of the spell from which the aura came from. A spell has up to three effects, with the index being 0, 1, or 2.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'pet_spell' table for MaNGOSZero

This table holds information on individual pet spells.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

guid int(11) unsigned

The pet GUID. [See character_pet.id].

spell int(11) unsigned

The spell ID.[See (Spell.dbc]

active int(11) unsigned

Boolean 0 or 1 controlling if the spell is active or not.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'pet_spell_cooldown' table for MaNGOSZero

This table holds information on pet spell cooldowns.

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

guid int(11) unsigned

The GUID of the pet. [See character_pet.id]

spell int(11) unsigned

The spell ID to which the cooldown applies.

time bigint(20) unsigned

The time when the cooldown expires, in Unix time.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'petition' table for MaNGOSZero

This table holds information on all ongoing petitions for a guild or for an arena team.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

ownerguid int(10) unsigned

The petition owner's GUID. [See characters.guid]

petitionguid int(10) unsigned

The GUID of the petition item. See (item_instance.guid)

name varchar(255)

The name of the guild or arena team that the player is trying to ask for petitions for.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'petition_sign' table for MaNGOSZero

This table holds information on all the signatures of a petition for either a guild or an arena team.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

ownerguid int(10) unsigned

The GUID of the owner that is trying to make the guild/arena team. [See characters.guid].

petitionguid int(11) unsigned

The GUID of the charter item. [See item_template.guid]

playerguid int(11) unsigned

The GUID of the player that has signed the charter. [See character.guid]

player_account int(11) unsigned

The account ID of the player that has signed the charter [See account.id]. No two players can sign the same charter from the same account.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'pvpstats_battlegrounds' table for MaNGOSZero

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

id bigint(20) unsigned

winner_team tinyint(4)

bracket_id tinyint(3) unsigned

type tinyint(3) unsigned

date datetime

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'pvpstats_players' table for MaNGOSZero

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

battleground_id bigint(20) unsigned

character_guid int(10) unsigned

score_killing_blows mediumint(8) unsigned

score_deaths mediumint(8) unsigned

score_honorable_kills mediumint(8) unsigned

score_bonus_honor mediumint(8) unsigned

score_damage_done mediumint(8) unsigned

score_healing_done mediumint(8) unsigned

attr_1 mediumint(8) unsigned

attr_2 mediumint(8) unsigned

attr_3 mediumint(8) unsigned

attr_4 mediumint(8) unsigned

attr_5 mediumint(8) unsigned

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'saved_variables' table for MaNGOSZero

Stores server required values.
i.e. Character Database cleanup flags and Honor Point / Rank reset date

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

NextMaintenanceDate int(11) unsigned

The Date when the Honor Points / Rank etc. are updated.
The date is then set 7 days in the future.

cleaning_flags int(11) unsigned

The flags controlling character cleanup:

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'warden_action' table for MaNGOSZero

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

wardenId smallint(5) unsigned

action tinyint(3) unsigned

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'world' table for MaNGOSZero

Stores World Status information

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

map int(11) unsigned

The map ID [See Map.dbc]

data longtext

Specific data belonging to the world.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module