Actually, while it still stands true that you should add "beginning of the line" anchor to most of your triggers if you've using my prompt hack just to make them faster and more precise there is simplier solution:

Just check the box "stop further processing" for the prompt trigger itself. I have very high priority for the prompt trigger, so it should cure any double firing. Basically it will disable any further trigger processing for the joint line (prompt+text) itself, so your triggers will normally fire only on the "text" when it will be printed after the prompt.
I need to add that feature to the prompt trigger itself (but I can't update the xml file I posted here, so do it on your own). It hasn't worked before, but CMUD changed #PRINT command recently, so it's the way to go now. Keep in mind, if you have other triggers that should fire on prompt, you have to make them higher priority than this one.



Edited 5 time(s). Last edit at 09/24/2008 07:06PM by Dwoggurd.