Zugg Software :: View topic

Beginner Joined: 01 Nov 2006 Posts: 14

Hey guys,
I recently wrote a script for my mud, but it was really rough since I don't understand programming very well, so I had someone fine tune it for me. He got all the kinks out and it ran very well in Zmud. Recently I've made the switch to Cmud, but he isn't here to back me up on this change, so I was wondering if you guys could help me out.

This is the original script.

Posted: Fri Jan 05, 2007 12:32 am

I take it that this is a representation of what's in the settings editor and you're not running this from the command line, right?

First, let me ask you what the output is. I assume it's something like this:

There are some tracks of a ridden mount leaving south.
There are some bloody traces of a trolloc leaving east.

I'm going to assume in my example that the line always begins "There are some something something of a" rather than "There are some something something of" - please correct me if I'm wrong.

And what you then want the trigger to do is simply highlight with different options - the whole line red if it's a trolloc or a human, green if it's not, with whatever it was that did the leaving in brighter red (or blue if the line is green) and the arrows in yellow. If that's the case, try this:

Trigger:
Pattern: There are some ($mode:{tracks|bloody traces}) of a ($leaver:*) leaving ($dir:%w).
Script:

Beginner Joined: 01 Nov 2006 Posts: 14

Hey, thanks alot, I really appreciate the help. I didn't know you could use #if to add both scripts into one. I think I understand how it works, and I think I can replicate it on other scripts. One question I have though.

Pattern: There are some ($mode:{tracks|bloody traces}) of a ($leaver:*) leaving ($dir:%w).

You didn't make a local: $mode or $dir, so i'm assuming that when the trigger fires, it automatically creates a $mode? and also, would #switch ($dir) create a local: $dir whenever the trigger fires and it registers a direction?

PS. Sorry I left so many things to be assumed in my post. You were correct on all behalfs and your script runs very nicely. :)

EDIT: I was originally running the script by creating a package, and then creating the triggers inside the package. I tried doing this with your script, and it would not run, which is one reason that I think my other script wouldn't run either (among other possible reasons). I then created it as a normal trigger (not in any packages) and it ran correctly. I'm not really sure why it would matter, but it seems like it did. I have also had problems with a few packages that I have installed (I.E. they stop working correctly after a bit). Has anyone else noticed this?

Posted: Fri Jan 05, 2007 2:35 am

Yep, the trigger creates them for you. $localvar=value creates them implicitly too, but not inside #if statements. The #switch doesn't create it, it compares the value with the other expressions. See the help file on #switch, the alternate syntax is in one of the comments.

In answer to your edit, a normal user shouldn't need to do a thing with packages, just create the triggers and such under the session window - that is, when you open the package editor you'll see a tree view with a window in it with the same name as your session. That's the session window. If they're in a package outside the one containing the session window, you'll need to make sure the module that they're in is set to global and that they're not referring to any settings in other packages that aren't also global.

Beginner Joined: 01 Nov 2006 Posts: 14

Ah, I was referring to where you used %ansi(%if($IsRed,red,blue),bold) which was neat. I would have used two triggers when I wanted different colors like that. Also, I thought I read in the file that they removed the (Item1|Item2) option.

Posted: Fri Jan 05, 2007 3:13 am

It's because it's trigger pattern syntax, yes. That's still the same as it was in zMUD, apart from the ($localvar:wildcard) bit.