The command is a block structure like mrandom, with the format for adding 
one: "mtrigadd <trigger> {reactions}"
 
A trigger can't have new lines, but you can use * to seperate them and use 
the # for substring, like #blah takes any command with the word blah in it,
the same as reactors. Now, the block { reactions } must follow mtrigadd and 
can be any amount of reactions, but if its more than say, 5, I would 
recommend using an mgoto to a different part of the mobproc, a subroutine 
if you will.  Also, if you "mtrigadd <existing trigger> { reactions }", 
it'll replace the existing one, so you can change them on the fly.
 
"mtrigdelete <trigger>" will remove a certain trigger from mobs list of 
triggers. "mtrigwax" wipes the whole list.  "mtrigwait": if the mob has a 
list of triggers and you mtrigwait, the mob will halt its mobproc until a 
trigger goes off.  If you mtrigwait on a mob who has no mobprocs, it'll 
be ignored.  The only way a mob can build its trigger list is by using 
mobproc commands, so youll never see a nonmobproc mob with a trig list.
 
"mdoubletime" sets DTIME flag from within a mobproc, and "mnormaltime" 
unsets DTIME flag.