Zugg Software :: View topic - Any ideas on working out why a trigger stops firing?

Novice Joined: 26 Jan 2009 Posts: 32

I have a standard Trigger except for it being Prompt enabled

^(%d)h, (%d)m([ exbc])-

now it does start off some complex stuff:

<trigger name="TrigPrompt" priority="15990" newline="false" prompt="true" id="1633">
<pattern>^(%d)h, (%d)m([ exbc])-</pattern>
<value>_Debug "TrigPrompt: Hit"
HeartBeats = 0
Personal.Health = %1
Personal.Mana = %2
#NEWVAR PromptFlags %3
#IF (@Mud.IgnoreNextPrompt) {Mud.IgnoreNextPrompt = 0} {
#IF (not %class(TrigReadBal)) {
Personal.EQ = %eval(%pos(e,%3) = 0)
Personal.Balance = %eval(%pos(x,%3) = 0)
}
}
#IF (%trigger(TrigReadBal)=-1) {
Personal.EQ = %eval(%pos(e,@PromptFlags > 0))
Personal.Balance = %eval(%pos(x,@PromptFlags) > 0)
}
Personal.Blind = %eval(%pos(b,%3) > 0)
Personal.Cloak = %eval(%pos(c,%3) > 0)
Mud.CommandWaiting = ""
Mud.PromptWaiting = 1
;#IF (%class(IntHeartbeat)) {_Main}
_Main
#IF (not %null(@Mud.SendOnPrompt) and @Mud.PromptWaiting) {
_SendCommand %item(@Mud.SendOnPrompt,1)
Mud.SendOnPrompt = %delnitem(@Mud.SendOnPrompt,1)
}
;_Debug "TrigPrompt: Finished"</value>
</trigger>

Now it seems that just after maybe 5 minutes it will stop firing. I can see no option to suggest it has been disabled. I get no error, seemingly no problems with other triggers, it is not multi state. I can "cut" it and "paste" it back and it will continue working. I'm asking for some suggestions in tracking down where the fault could be. The debug window shows it it is no longer firing. Any suggestions?

Posted: Tue Jan 27, 2009 4:40 pm

I used to have an issue with that on Zmud where I'd see those exact symptoms. In Zmud the solution was to select the "Trigger on Trigger" option for all my triggers. I never figured out why that worked, but it seemed to solve the problem.

Novice Joined: 26 Jan 2009 Posts: 32

Hey thanks that seemed to work, but with the completely opposite solution.

It seems that all my triggers have trigger on trigger selected from my import from ZMud latest that seemed to be the default. Un-selecting trigger on trigger seemed to fixt the problem.

Trigger on Trigger is tooltiped as Allow other trigger to fire while this trigger is running.

Novice Joined: 26 Jan 2009 Posts: 32

Hmm, but actually does have other side effects. Sadly my prompt trigger sends commands from my personal command queue. Those commands sent need to fire other triggers and with this option off those triggers will not fire.

This is the situation:

You see a rat
---> "ih" goes into my command queue to be send on prompt.
3180h, 2942m ex-
--> Prompt Arrives, Command Que checked to see if there is anything to send. "Ih" is found and Sent

If the prompt trigger is not set to Trigger on Trigger then....
The ^ih$ trigger on command input never fires and so the data collected from the mud never collected and processed.

Looks like I need to work out why my prompt trigger stops firing after an arbitrary amount of time when Trigger in Trigger is selected.

Posted: Wed Jan 28, 2009 3:41 pm

It seems like the "trigger on trigger" is interacting in some way that can possibly permanently disable triggers. It's been this way for me since Zmud and I had no idea why I was the only one seeing it for a long time. Perhaps if you are able to get this down to a repeatable set of instructions Zugg can address this in a bug fix.