Zugg Software :: View topic - ERROR: Operator CONCAT requires two arguments

Beginner Joined: 05 Jul 2007 Posts: 21

could use a hand here... i get this error anytime i hit enter or text is sent to the mud... and at the beginning of every block of text received FROM the mud:

ERROR: Operator CONCAT requires two arguments

i used find in the setting editor and replaced all instances of %concat in my entire script. here is what the debugger reads.. hate to say i don't know quite how to read it yet though. i noticed also that turning off singular sub packages in the debugger disables logging for the entire main package as well. anyway here's the printout:

Posted: Thu Dec 27, 2007 1:10 pm

Unfortunately, your problem is far too broad for us to really help with it. As it is, we'd need to sift through the XML for all your oninput and normal triggers, with all their related variables and stuff. Saying it's related to those alarms isn't helpful without seeing the aliases as well.

So, try disabling things until you get to a point where it stops happening. Hopefully that'll help you narrow down what's causing the error. Once you know the setting(s) that're causing it, and if you can't fix them yourself, then post their XML, and the XML for everything they call (custom functions, aliases, variables, etc) and we'll see what we can do.

Beginner Joined: 05 Jul 2007 Posts: 21

ok so to more precisely describe the problem i've narrowed it down to this trigger:

Pattern: {^³(*)³$}

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

Cmud no longer likes the var.key = syntax very much. Try doing this instead and see if the problem goes away.

#addkey prompt room {%1}

Posted: Sat Dec 29, 2007 3:21 pm

You also don't need the braces around %1 in CMUD, since they're expanded after parsing and not before, as in zMUD, and you don't need the empty set of braces for the optional else-command of the #if.

Beginner Joined: 05 Jul 2007 Posts: 21

in my experience the braces are needed for scenarios involving spaces. i just tested it with a variable involving spaces and confirmed this.

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

Did the error go away?

Beginner Joined: 05 Jul 2007 Posts: 21

err sorry. i ended up scrapping the entire script and pasting it in bit by bit, correcting errors along the way. no errors thus far.. just tedious. i want to say it involved some nested script that lead back to a trigger with a special ascii character not parsing correctly upon import. if i come across this again i'll repost.