Areatriggers¶
Areatriggers are client-defined trigger volumes (from AreaTrigger.dbc) the server reacts to
when a player enters or exits. The world DB adds behaviour per trigger id through a family of
tables.
The Family¶
| Table | Behaviour on enter |
|---|---|
areatrigger_template |
Base metadata/flags for the trigger. |
areatrigger_teleport |
Teleports the player to target coordinates/map (dungeon entrances, portals). Honors required quest/level via fields; also patch-filtered (patch column). |
areatrigger_tavern |
Marks tavern zones: inside, players get the resting bonus and instant logout. |
areatrigger_bg_entrance |
Registers an entrance portal to a battleground queue (links to battleground_template). |
areatrigger_involvedrelation |
Completes "explore the area" quest objectives (quest explore triggers). |
areatrigger_scripts |
Runs generic DB scripts for fully custom behaviour. |
How It Works¶
- The client detects entry into an
AreaTrigger.dbcvolume and notifies the server. - The server looks up the trigger id in each table above; all matching behaviours apply (a trigger can teleport and run a script).
- Teleports respect level/quest requirements configured on the row and can be blocked by conditions where supported.
Examples¶
- Custom portal: add a row to
areatrigger_teleportwith destination coordinates, or useareatrigger_scripts+ command 6TELEPORT_TOwhen you need conditions (conditions). - Dungeon entrance with ghost entrance: set
ghost_entrance_map/x/y/zso dead players enter at the graveyard side. - Explore quests: reference the areatrigger id from
quest_template.ReqCreatureOrGOId*-style exploration objectives and link it inareatrigger_involvedrelation.
Related Pages¶
- Instances & Resets - dungeon entrances
- Game Events - event-gated content nearby