Zugg Software :: View topic - Possible Bug with Triggers and Tick Timer

Newbie Joined: 06 Apr 2007 Posts: 9

I'm not sure if this has already been reported, unfortunately, as I'm not sure how to search the forums for it.

When my tick timer fires, the command echo from it has been causing some of my triggers not to fire, because apparently CMud sees the tick timer text as part of the line (all my triggers end with $ because most of them were copied and pasted). Obviously this is not part of the MUD text, so it is unacceptable behavior that the tick timer disables the trigger.

Anyone else experiencing something similar? Has this been fixed in 1.27?

Posted: Sat Apr 14, 2007 4:57 pm

I'm not sure if it would help, but I usually gag my tick timer.

Or better yet, you can use the #TIMER command to disable the message flag. I hope that helps.

Newbie Joined: 06 Apr 2007 Posts: 9

It isn't the message flag but the command echo of the timeout command, and if it's being picked up as the end of a line, wouldn't I just assume that would gag the pattern of the trigger failing to react, thus making the problem worse?

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Inside the Tick Timer use #send if this is still broken.
I do not know if the error is fixed or not as I have not used the tick timer in a while.
#send {do whatever}

Newbie Joined: 06 Apr 2007 Posts: 9

Actually I have had this problem with more than the tick timer now. I issued a command and it came up at the end of the line, thus negating my @target trigger (which is to #cw a name red).

So it actually isn't anything to do with the $ at the end of the triggers. When a command comes up at the end of the line, that line isn't tested against trigger patterns.

Wizard Joined: 14 Aug 2004 Posts: 1269

Perhaps you should give us an actual example of one of the triggers that has this problem, together with what options you have enabled or disabled on it...