Zugg Software :: View topic

Newbie Joined: 29 Nov 2005 Posts: 9

okay I have a prompt trigger for Achaea and sometimes it simply just stops -working-, it's still on but it refuses to fire, ctrl+x and then ctrl+v makes it work again, but so far I have simply been unable to figure out why it stop firing, it seems like if I send too many things to the mud it stops, but anyone know why? Confused

and better yet anyone have any idea on how to make it stop doing it?

basicly it's like this

#REGEX {^(\d+)h\, (\d+)m, (\d+)e, (\d+)w ([cexkdb]*)\-} {#PRIORITY {a lot of IF's that shouldn't mean anything in this regard, since they work perfectly normally}}

another one has the same trigger and with him it's doing the exact same thing

Novice Joined: 23 Jun 2005 Posts: 32

Don't use priority in prompt triggers. There is this weird bug in Zmud where the trigger shuts down. I dunno why other than FORALL, WHILE, LOOP and PRIORITY make it barf and die. If it's for like... turning on and off classes, use something like this.

#untrigger realCureReset
#temp {^\d+h\, \d+m} {#t- realCureReset} "" {nocr|prompt|regex}

The untrigger is needed in case THAT one locks up too.