Zugg Software :: View topic - [1.30] 'invalid local variable' in trigger pattern

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

#TRIGGER {^Test1$Test2$} {whatever}

(When trying to match a line following another)
Throws an error saying $Test2 isn't valid. There was another post Zugg commented on saying we should escape $, but that would affect the trigger pattern in this case

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

Hmm, I write triggers in both regex and zscript as the need\whim arises.

A work around for this would be to use regex. In regex \n is the same as $ in zscript.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Or you can use conditions, or just edit the trigger in the settings editor after it's been created.
Just reporting it anyway ;)

Posted: Tue May 01, 2007 12:27 am

Doesn't putting a ~ in front of the first $ work?

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

But then it looks for the $ symbol, rather than an end of line. You can put ~$ to make CMUD create a trigger, but then you need to go into the editor and remove the ~

Posted: Tue May 01, 2007 2:01 am

Ahh, ok, I see what you mean. Yes, this is a bit weird. Putting a ~ before the $ *should* tell it to match a $ character verbatim, so that's working as it should. I'll add this to the bug list, but it probably won't get fixed for a few versions...I'll have to give more thought to how this should work.

Posted: Tue May 01, 2007 2:45 am

Well, if it really comes to it, multistate triggers with the within=1 set will do the same job. I personally haven't used $ in the middle of a pattern for a long, long time.