Zugg Software :: Search

Hi,

I just heard about CMud from a friend earlier today, downloaded and installed the trial (version 3.34) and connected to my MUD of choice. Less than 1 hour after installation CMud froze and now ...

Oh, I didn't realize the export saves the settings in a .txt file. Great, thanks!

.atr.

Hmm, I must've accidentally pressed "back" when I edited the post, sorry for double-posting.

.atr.

Hey there,

I got this rather annoying little problem. I have several spell duration counter triggers and apparently there is something wrong with them since when the triggers activate they create a ...

Hey there,

I got this rather annoying little problem. I have several spell duration counter triggers and apparently there is something wrong with them since when the triggers activate they create a ...

so %w matches only one word but when its used with and %s it will match words seperated with spaces.

Any amount of words, separated by any amount of whitespace (well, at least as long as it's all ...

it matches a single word not any amount :(

No, it matches any amount of words, when used with %s like Maelstrom did. Try it yourself if you don't believe me. I've successfully used that format on a ...

%w just matches one word

Not really. %w matches any amount of words just like [a-zA-Z] matches any amount of letters, with any amount of whitespace in between when used with %s the way Maelstrom di ...

Should probably be;
#TRIGGER {^You shift into the aspect of (%w).$} {party say Aspect change to %1 complete}

While this would work, I can't use it, as the value has to be stored in @Aspect for sta ...

From zMud help file:

"To restrict the trigger to just match numbers, change the trigger to:

#TRIGGER {You get &%dGold coins}

Now the "You get many coins" will not match the trigger. You ...

So remember:
#wa 250 - 1/4 of a second, or .25
#wa 500 - 1/5 of a second, of .5

Umm, I believe #wa 500 equals 1/2 of a second, not 1/5 (which would be 200ms or #wa 200).

Just a sidenote.

.a ...

Here's what I finally ended up with and it works beautifully (it's a different trigger, but the principle is the same):

Pattern:

^You just got ([%w%s]) better in ([%w ...

My original post was as much meant to get advice on how to prevent such situations as it was to try to wake people up to the potential dangers of poorly made triggers.

I tried your exact example an ...

Okay, consider this:

You make a trigger to highlight and catch part of a line from mud input to inform your party of what's happening. Let's say you have a skill that has a special effect of stunni ...

Ok, thanks both for your input. I changed the triggers to correspond with the strict syntax so there's no room for errors or confusion.

.atr.

yes, the curly brackets seemed to clear the error messages (and the triggers still actually work Mr. Green

). Thanks.

Hey peeps.

Can someone spot why this (perfectly working!) trigger is considered to have a syntax error in it and what I could do to fix the situation.

It's a spell timer and here's what it does ...

I was waiting for that reply to come. Laughing

.atr.

Yeah, you're on the right track there. If one is so badly visually impaired (s)he can't even read that humongous code there... how in the world is (s)he supposed to read that tiny little help text abo ...

Not to offend anyone or anything, but I burst out laughing when I saw this on the forum registration page:

http://epidi.com/tmp/text.gif

Anyone else notice anything... uh... slightly comical abo ...

I'm having a little bit of trouble here as well. What I have so far:

#TR {^Your default pack tactic is ~'*~'.} {#CW {%1} {$cccc00}}

Works fine, whenever I get something like: "Your default pack ...