referenceThere are numerous reasons a trigger would not fire.
1. Nohassle - Ensure you have nohassle off. Simply toggle it by typing "nohassle" or stat self to see if the PRF flag NO_HASS is set (enabled).
2. %echo% - Make sure the trigger is doing what you expect. Add an "%echo% firing" in the first line to make sure it is working. Also echo any variables you are using in the trigger to make sure they contain what you expect.
3. Mobs - If a mob can not see the player a trigger may not fire. Be wary of blind mobs, dark rooms, invis/sneaking players. Also switch into the mob to test the trigger and you will see the mob try to execute the trigger commands to help you troubleshoo
. If you see a "Huh?" or a "that person is not here" it can help you fix your problem.
4. Command Triggers - Arguments: * means all commands. This is an easy way to freeze yourself (all commands you enter are captured by the trigger). To protect against this and other possibly malicious uses of triggers level 32 and above may not be able t
fully test some triggers (specifically damage and command come to mind). So either create a mortal character or set your level to 31 to fully test all triggers. The return command can be setup to allow you to restore your level back to original, ask you
See also:: TRIGEDIT-MOB-TUTORIAL, TRIGEDIT-ADVANCED-TUTORIAL