Created page with "The `ai_queue` trigger has 20 different queues available to use. The trigger’s subject is the NPC type. There are a few conventions used globally: [ai_queue1,type] runs on retaliate - this means something has hit them and the NPC may react. [ai_queue2,type] runs on damage - this means something has hit them and the NPC may apply that damage. [ai_queue3,type] runs on death - this means something has dropped their health to 0 and the NPC may drop items or advance a pl..."
 
No edit summary
Line 1: Line 1:
The `ai_queue` trigger has 20 different queues available to use. The trigger’s subject is the NPC type.
The <code>ai_queue</code> trigger has 20 different queues available to use. The trigger’s subject is the NPC type.


There are a few conventions used globally:
There are a few conventions used globally:
[ai_queue1,type] runs on retaliate - this means something has hit them and the NPC may react.


[ai_queue2,type] runs on damage - this means something has hit them and the NPC may apply that damage.
<code>[ai_queue1,type]</code> runs on '''retaliate''' - this means something has hit them and the NPC may react.


[ai_queue3,type] runs on death - this means something has dropped their health to 0 and the NPC may drop items or advance a player’s quest state.
<code>[ai_queue2,type]</code> runs on '''damage''' - this means something has hit them and the NPC may apply that damage.


[ai_queue8,type] runs on bind spells - this means something has hit them with a bind spell and movement should be blocked for a period of time.
<code>[ai_queue3,type]</code> runs on '''death''' - this means something has dropped their health to 0 and the NPC may drop items or advance a player’s quest state.
 
<code>[ai_queue8,type]</code> runs on '''bind spells''' - this means something has hit them with a bind spell and movement should be blocked for a period of time.


Outside of these conventions, developers may use any queue “ID” to handle special logic.
Outside of these conventions, developers may use any queue “ID” to handle special logic.


Hunts may be configured to run queues when they find a target.
Hunts may be configured to run queues when they find a target.

Revision as of 18:42, 12 January 2025

The ai_queue trigger has 20 different queues available to use. The trigger’s subject is the NPC type.

There are a few conventions used globally:

[ai_queue1,type] runs on retaliate - this means something has hit them and the NPC may react.

[ai_queue2,type] runs on damage - this means something has hit them and the NPC may apply that damage.

[ai_queue3,type] runs on death - this means something has dropped their health to 0 and the NPC may drop items or advance a player’s quest state.

[ai_queue8,type] runs on bind spells - this means something has hit them with a bind spell and movement should be blocked for a period of time.

Outside of these conventions, developers may use any queue “ID” to handle special logic.

Hunts may be configured to run queues when they find a target.