Skip to content

creature_equip_template

Structure ​

FieldTypeAttributesKeyNullDefaultExtraComment
CreatureIDintunsignedPRINO0
IDtinyintunsignedPRINO1
ItemID1intunsignedNO0
AppearanceModID1smallintunsignedNO0
ItemVisual1smallintunsignedNO0
ItemID2intunsignedNO0
AppearanceModID2smallintunsignedNO0
ItemVisual2smallintunsignedNO0
ItemID3intunsignedNO0
AppearanceModID3smallintunsignedNO0
ItemVisual3smallintunsignedNO0
VerifiedBuildintsignedNO0
 

Description of fields ​

CreatureID ​

The direct corresponding id in creature table or entry in creature_template table.  

ID ​

An additional identifier for each individual entry, enabling multiple equipment for one creature entry. Counter must start with 1 and grow accordingly.  

ItemID1 ​

This is the item number of the equipment used in the right hand from ItemSparse.db2 or Item.db2.  

AppearanceModID1 ​

ItemID + AppearanceModID together form a key to get DisplayID. Check: ItemModifiedAppearance.db2  

ItemVisual1 ​

ItemVisual is ID for ItemVisuals.db2, for e.g. enchant visuals.  

ItemID2 ​

This is the item number of the equipment used in the left hand from ItemSparse.db2 or Item.db2.  

AppearanceModID2 ​

ItemID + AppearanceModID together form a key to get DisplayID. Check: ItemModifiedAppearance.db2  

ItemVisual2 ​

ItemVisual is ID for ItemVisuals.db2, for e.g. enchant visuals.  

ItemID3 ​

This is the item number of the equipment used in the ranged slot from ItemSparse.db2 or Item.db2.  

AppearanceModID3 ​

ItemID + AppearanceModID together form a key to get DisplayID. Check: ItemModifiedAppearance.db2  

ItemVisual3 ​

ItemVisual is ID for ItemVisuals.db2, for e.g. enchant visuals.  

VerifiedBuild ​

This field is used by the TrinityDB Team to determine whether a template has been verified from WDB files.

If value is 0 then it has not been parsed yet.

If value is above 0 then it has been parsed with WDB files from that specific client build.

If value is -1 then it is just a place holder until proper data are found on WDBs.

If value is -Client Build then it was parsed with WDB files from that specific client build and manually edited later for some special necessity.