Question More Trigger Help

I should write a helpfile on this. Here goes.

TRIGGER-TESTING TRIGEDIT-TESTING

There are numerous reasons a trigger may 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
troubleshoot. If you see a "Huh?" or a "that person is not here" it can help 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 to 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 your coder to add your ID.

See Also: TRIGEDIT-ADVANCED

That is all for now, other suggestions appreciated.

Rumble wrote: 4. Command Triggers - Numeric Arg * 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 to 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 your coder to add your ID.

That's arg, not numeric arg, numeric arg is only used by object command scripts and is only used to determine where the object must be for the command to trigger the script (ie. worn, inventory, or ob the ground).

Parna pointed out trigger 338 still wasn't working. I changed it from: to:
Sorry we missed this earlier.