Zugg Software :: View topic

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I've got three triggers to capture my score in three different formats. My triggers weren't firing when I checked my score, and by investigation I found that I could select the first state in each multi-state trigger, go through the compiled pattern, compiled code, and script text tabs to force it each to compile and work. So, I thought something was off in my score triggers. But, separating these three multi-state triggers out and testing them in the untitled session showed that they fired just fine.

When I select the trigger and look at the compiled pattern tab, I see "Error compiling script: illegal character in expression:" (and no character given after that, which seems to be what you'd expect). The bizarre thing is that if I switch to the compiled code tab and then back to the compiled pattern tab, it's compiled successfully!

What I know:

The issues being reported:

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I think I've narrowed this down to my patterns that have (?:@variable) in them. If I remove the (?:) from the pattern (in the case of single variable patterns), it works. If I leave that in there and just force the pattern/code to compile to switching tabs, it works.

It only happens when combined with variables, as far as I can tell. I've got plenty of triggers that match things like (?:[hH]is|[hH]er) and they work fine.

Posted: Wed Mar 19, 2008 8:07 pm

Does the @variable have a value in your settings? If so, does it only cause a problem if @variable has a particular value? If @variable has a null value, then I can see where the PCRE engine might complain about it.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

The variable has a value before I even define the trigger, assuming the settings are compiled in the order I create them from my script. Would the pattern need to be re-compiled by CMUD when the variable changes?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

From what I am seeing switching to the Compiled Pattern tab from another trigger tab causes the regex for the trigger to be compiled after it parses through the pattern for any variable references. This particular recompile does not occur if you are examining one trigger after another looking at the compiled pattern tab.

I also tested using an invalid variable reference in a pattern of "(?:@var)" and the PCRE didn't complain with the pattern compiled by CMud correctly. In fact it matched everything as a null pattern should. Creating and changing the variable properly adjusted the matching as well.

The error your mentioning would be before it even tries to compile the regex. I would have to guess this has something to do with your import method, and would suggest you try to put together a procedure that demonstrates it using a smaller snippet of your settings.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I tried reproducing it with a small script and couldn't make it happen. I imported my one (3,000+ line) script in a blank session, however, and it did happen. I sent the script with instructions to Zugg (support e-mail) hoping he'd be able to reproduce it and figure out the root cause.