Tabelle: 'npc_spellclick_spells'
The `npc_spellclick_spells` tableThis table holds information about spells to be cast upon receivingCMSG_SPELLCLICK. That opcode is sent for quests in which you have to loot creatures, who are already dead at spawning. Examples arePlanning for the FutureandRifle the bodies.
StructureField | Type | Attributes | KeyNull | Default | Extra | Comment' | |
---|
npc_entry | int(10) | vorzeichenlos | | nein | NULL | | Reference to the creature_template table | spell_id | int(10) | vorzeichenlos | | nein | NULL | | The ID of the spell to be cast | cast_flags | tinyint(3) | vorzeichenlos | | NO | NULL | | Who casts the spell on who, creature <=> player (values: 0-3) | user_type | smallint(3) | vorzeichenlos | | nein | 0 | | Relation with summoner: 0-no 1-friendly 2-raid 3-party player can click |
Description of the fieldsnpc_entryReference to creature_template.entry spell_idThe spell which should be cast. Note that for several quests there are more than one spell per click. Planing for the Futurefor example hasPlanning for the Future: Create Snowfall Glade Pupwhich will create the item in the playerâs inventory andPlanning for the Future: Create Snowfall Glade Pup Coverwhich despawns the creature. This creates the illusion that the creature has been looted. cast_flagsOn every spellclick event, a player and a creature "participate". This field defines who casts the spell on who. Lower bit defines caster: 1=player, 0=creature; higher bit defines target, same mapping as caster bit. You can use that table for the actual value: Caster | Target | cast_flags value |
---|
Creature | Creature | 0 | Player | Creature | 1 | Creature | Player | 2 | Player | Player | 3 |
user_typeRelation with summoner: defines who is able to use this spellclick. Value | Description |
---|
0 | Only self | 1 | Friendly | 2 | Raid | 3 | Party |
|