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 'creature_battleground' table for MaNGOSZero
This table contains the description of creatures spawned on battlegrounds.
This table uses the 'MyISAM' DB Engine
The Field definitions follow:
|Field Name||Field Type||Nullable||Key||Default Value||Attributes||Notes|
|guid||int(10) unsigned||NO||PRI||NULL||A unique identifier given to each creature to distinguish them from each other.|
|event1||tinyint(3) unsigned||NO||NULL||Main Event.|
|event2||tinyint(3) unsigned||NO||NULL||Sub Event.|
Description of the fields
guid int(10) unsigned
A unique identifier given to each creature to distinguish one creature from another. Two creatures can NOT have same GUID. This GUID is linked to the creature-table.
event1 tinyint(3) unsigned
The identifier for the event node in the battleground. Event nodes usually are defined in the battleground's script.
Nodes are locations in a battleground where characters of each faction can perform actions, such as capturing a tower in Alterac Valley, or taking control over the stables in Arathi Basin.
event2 tinyint(3) unsigned
The state of the event node. Node status is defined differently in every battleground script.
Node events can occur for every node and usually describe changes due to character interaction. E.g. if stables in Arathi Basin are taken over by Alliance, the stables note state would become Alliance controlled. Similar node states exist for every battleground note.
If you update battleground scripts and make changes to node status values ensure that you provide database update scripts which update the battleground events accordingly.
auto-generated by the getMaNGOS.eu MAGNET dbdocs module
Edited by Antz