Zugg Software :: View topic

Posted: Wed Jun 29, 2005 1:05 am

I don't know if this is actually a bug, but in 7.13a, the following occurs:

I'll set a trigger up using the command line. Something like:

#TRIGGER {You say (%w)} {#IF (%1 = what) {laugh}}

Now, after sending it to the mud, I'll try it out. Nothing happens. So, I go into the Settings editor and check the trigger to see if I did anything wrong. Here is the output:

Pattern: You say (%w)
Action:
{#IF

That's all that it shows. Like I said, I don't know if this is a bug, but something to look into if it is. Thanks.

Charneus

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

It works fine for me? Are you sure you didnt miss a } or ) when you were inputting it into Zmud?

Also as a semi-OT subject, you should always quote "string" returns

#TRIGGER {You say (%w)} {#IF ("%1"="what") {laugh}}

Posted: Wed Jun 29, 2005 3:25 am

Bah.

It's happened on all my triggers with the #IF command. I know I hadn't missed a } or ) because I always check to make sure each one is closed... So, I don't know what the problem is.

Even so, shouldn't the action still be set in full there? It just wouldn't work, and it'd say something like syntax error.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

I've had this same issue happen since the mid 6.xx versions. Back then a single line of code would be deleted, resulting in a syntax error (this was especially happening when I had a quite large batch of code for the Pretty Printer to update or a really large set of code in general). At some intervening version, it stopped deleting the line of code and instead started to duplicate it--resulting in another syntax error. Throughout the 7.xx series thus far, the occurrance of this problem has gotten extremely rare for me.

I'm guessing it's an issue between the Pretty Printer trying to update what you had just typed and you trying to type while it's updating.