Zugg Software :: View topic

Novice Joined: 26 Apr 2007 Posts: 44

So, here's what I made:

Pattern:

^(&currentHealth)h, (&currentMana)m, (&currentEgo)e, (&currentPower)p, (&currentEndurance)en, (&currentWillpower)w ($promptCharacters:%w)-$

Some curious issues with this pattern. #SHOW $promptCharacters shows what is currently in &currentPower. I isolated them by using traditional %1, %2 characters, and it turns out that each of these seems to have created two %xs - %1 and %2 both refer to the number in &currentHealth, %3 and %4 refer to the number in &currentMana, etc. %7 should be what $promptCharacters is. Instead, $promptCharacters is %13!

Am I doing something wrong, or is this a bug?

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

As I said on the Lusternia forums, you're missing wildcards in your first six matches. It may still be uncovering parsing problems in CMUD (should probably throw a scripting exception, unless there is a default wildcard of which I'm unaware). Try adding the %d to your first six pattern matches and see if it makes a difference.

Posted: Thu Apr 26, 2007 6:35 pm

CMUD doesn't currently allow mixing of both the &varname and ($local:pattern) syntax in the same trigger. So yes, it's going to get confused. When you don't specify a wildcard, CMUD defaults to using * for the wildcard, so I don't think the missing patterns will matter.

I've added this to the bug list.

Novice Joined: 26 Apr 2007 Posts: 44

This should not be necessary according to the #HELP:

Novice Joined: 26 Apr 2007 Posts: 44

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

I admit I was too lazy to check the help file, but I suspected it would assume * if no wildcard was provided. Still, using %d would be a good idea, on the wildly off chance that you'd match something else you didn't want.

I'm still sticking with no variable names in trigger patterns for now, assigning them to local or non-local variables inside the trigger code as necessary.