A Reply Trigger consists of two important parts:
1) The Trigger Command: the action that triggers the mob.
2) The Response Command: the action the mob performs when triggered.
Mob switches to whoever is casting at it.
MOB: 96807 TRIGGER ;; a magedoomMob consents when PC bow's to them.
MOB: 57031 TRIGGERNow we get a little fancier - in this next example of a multi-response trigger, the old drunk first rubs his belly, then he burps at the initiator, then says "That's some good ale!" 25% of the time, complete with ANSI colors.
Note the delays - it's important to set subsequent actions at a higher delay, otherwise they'll all go off at the same time. The delay in the subsequent commands is based from the moment the mob was triggered, NOT the time since the last command. In this case, the mob performs the chained commands two seconds apart. Also note that the TRIGGER field is left off of the chained commands - it only belongs on the first one. Also, DONE is not stated until the end of the whole chain. The "\n" at the end of the room echo signifies a line break...see Section 6 for details about those special commands.
MOB: 91404 TRIGGER
FLAG: 33 ;; NOT_IN_COMBAT + DIRECTED
CHANCE: 0 ;; 100% Chance
DELAY: 8 ;; Delay of 2 seconds (8 ticks)
TRIGGER: 94 ;; Poke
ACTION: 1003 ;; Room Echo
&+gThe drunk rubs his belly.&N\n
~
FLAG: 37 ;; NOT_IN_COMBAT + DIRECTED + USE_INITIATOR
CHANCE: 0 ;; 100% Chance
DELAY: 16 ;; Delay of 4 seconds (16 ticks)
ACTION: 106 ;; Burp
~
FLAG: 33 ;; NOT_IN_COMBAT + DIRECTED
CHANCE: 3 ;; 25% Chance
DELAY: 24 ;; Delay of 6 seconds (24 ticks)
ACTION: 17 ;; Say
&+GThat's some good ale!&N
~
DONE