spell_area

<-Back-to:World

The `spell_area` table

This table is used to apply a specific spell aura to the player within an area in the game. When any player enters this area or somehow interacts with a quest, this aura will be handled accordingly.

Structure

Description of the fields

The spell ID of the spell to be casted on the player. See Spell.dbc.

The area ID. Type “.gps” in-game and find the “Area:” number to use for this cell. Also see AreaTable.dbc.

The entry of the quest which the player must have in the state defined by quest_start_status. See quest_template.id.

The entry of the quest which the player must not have in the state defined by quest_end_status. See quest_template.id. Setting both quest_start and quest_end to the same value is useless.

If set, this value (plus or minus aura spell ID from Spell.dbc) imposes additional condition.

The value has the following effect:

• < 0  (negative values) If the player has aura -aura_spell then the spell will not be activated.
•   0   this column is ignored.
• > 0  (positive values) If the player has no aura aura_spell then the spell will not be activated.

This ID is automatically called from ChrRaces.dbc. The bitmask is entered here.

• 0, 1791 = All Races
• 690 (2 + 16 + 32 + 128 + 512) = Horde Only
• 1101 (1 + 4 + 8 + 64 + 1024 ) = Alliance Only

The gender type this entry applies to. 0 = Male, 1 = Female, 2 = Any.

Note: Spell is allways removed on leaving area, SPELL_AREA_FLAG_AUTOREMOVE does not effect this.

Example:

• flags = 0 : Spell not added on enter (must be added manually), not automatically removed on quest update, but removed on leave.
• flags = 1 : Spell is automatically applied on enter, not automatically removed on quest update, but removed on leave.
• flags = 2 : Spell not added on enter (must be added manually), automatically removed on quest update and removed on leave.
• flags = 3 : (Default) Spell is automatically applied on enter, automatically removed on quest update and removed on leave.

Within quest_start_status, you can define the mask of quest status required for quest_start.

Within quest_end_status,  you can define the mask of quest status required for quest_end. 

Example:

Area 257 is a cavern on Teldrassil. What we want is simple : When the player take the 28725 quest, he have the aura in the cavern. When he finish the 28727 quest, the aura disappear.

You should have the spell 92237 when entering the cavern IF :

• The start quest 28725 is incomplete, complete or rewarded (2 | 8 | 64 = 74)
• The end quest 28727 is not taked (none), incomplete or complete BUT not rewarded (1 | 2 | 8 = 11)

Here is the SQL for this example : 

INSERT INTO `spell_area` (`spell`, `area`, `quest_start`, `quest_end`, `autocast`, `quest_start_status`, `quest_end_status`) VALUES 
(92237, 257, 28725, 28727, 1, 74, 11);

Example for a SQL

 For a `quest_end_status` that should contain QUEST_STATUS_NONE (1), QUEST_STATUS_COMPLETE (2) and QUEST_STATUS_INCOMPLETE (8):

-- equivalent to `quest_end_status`= 11
UPDATE `spell_area` SET `quest_end_status`= (1|2|8) WHERE `spell`=XXXXX AND `area`=YYYY;

Some examples:

• An area could pacify all players (spell 39331)
• Another area could full heal every 1 second (spell 48591)
• Teleport player out of an area (spell 53141)
• Factions-specific buffs, e.g. in Icecrown Citadel:
• “Hellscream's Warsong” (spell 73822) for horde 
• “Strength of Wrynn” (spell 73828) for alliance
• Even region-based buffs, such as area 440 - Tanaris.