item_effect

Back-to:Hotfixes

The `item_effect` table

This table contains some of the item effect data regarding item hotfixes. This table is primarily used to hotfix spells on items.

Structure

Field	Type	Attributes	Key	Null
ID	INT	UNSIGNED	PRI	NO
ItemID	INT	UNSIGNED		NO
OrderIndex	INT	UNSIGNED		NO
SpellID	INT	UNSIGNED		NO
Trigger	INT	UNSIGNED		NO
Charges	INT	UNSIGNED		NO
Cooldown	INT	SIGNED		NO
Category	INT	UNSIGNED		NO
CategoryCooldown	INT	SIGNED		NO
VerifiedBuild	SMALLINT	SIGNED		NO

Description of the fields

This is the unique ID for the item_effect table and has no relation whatsoever to the item ID that is being hotfixed. This value links to hotfix_data.RecordID with the proper TableHash accompanied.

This is the unique ID for the item that has received a hotfix. This value links to hotfix_data.RecordID with the proper TableHash accompanied, item.ID and item_sparse.ID.

The order in which the spells are displayed on the item tooltip and are placed upon the item. Starts at 0.

The spell ID of the spell that the item can cast or trigger.

The type of trigger for the spell.

ID	Trigger Type
0	Use
1	On Equip
2	Chance on Hit
4	Soulstone
5	Use with no delay
6	Learn Spell ID

The number of times that the item can cast the spell:

If 0, then infinite charges are possible.
If negative, after the number of charges is depleted the item is deleted as well.
If positive, the item is not deleted after all the charges are spent.

The cooldown in milliseconds for the specific spell controlling how often the spell can be used. Use -1 to use the default spell cooldown.

Note: this is not the “internal cooldown” of procs commonly found on items such as trinkets with “Chance on hit” effects.

The category that the spell is in.

The cooldown time in milliseconds that is applied to all other spells in the category that the triggered spell is also in. Use -1 to use the default spell cooldown.

This field was used 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.