Zugg Software :: View topic

Newbie Joined: 22 May 2003 Posts: 7

Okay, I've had several working capture triggers for my channels in Achaea. I wrote them myself and they have been working beautifully. I've enjoyed them a lot and have gotten spoiled with them.

For those of you unfamiliar with Achaea, a channel message looks like this:

(City): Peter says, "Yes, I did it."
(Guild): John says, "Can I get some help?"
(Novice): You say, "Where can I get a tattoo?"

etc.

Here are the scripts that I have been using to capture these channels and output them to different windows.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

<>
Special characters. Treat them the same way you did the ().

Newbie Joined: 22 May 2003 Posts: 7

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

It's not what they do in regular expressions, it's what they do in zMUD. zMUD interprets <> as grouping characters used to force expansion, so it strips at least one set and expands any variables or expressions inside them. You'll need to use the zMUD quote character, ~, to get them ignored (however this will put the ~ in your pattern).

Actually, you'll probably have to make your patterns in the Settings Editor to get them right with #REGEX. With #TRIGGER, this will work:

Newbie Joined: 22 May 2003 Posts: 7

I am still not able to get this to work. I have tried everything that you have suggested and have also tried switching off the <> characters in the parsing settings as well as in the special characters. I have included other things in my trigger like echos to test to see if the trigger runs on a <<Guild>>: Peter says, "HELP!" and the trigger is running.

It just refuses to capture.

Thanks for the help so far!

Wanderer Joined: 17 Aug 2004 Posts: 98 Location: OK, USA

Sorry to chime in since I'm at work and can't test this, but I noticed your original pattern was:

#REGEX "StartCapture" {^\((.*)\): (\w+ says, .*)}

and then you switched to:

#REGEX "StartCaptureSecret" {^<<(\w+)>>: (\w+ says, .*)}

Since quoting the special characters and using .* in the first pattern worked, did you try that for your second pattern also? Such as:

#REGEX "StartCaptureSecret" {^\<\<(.*)\>\>: (\w+ says, .*)}

Newbie Joined: 22 May 2003 Posts: 7

I did Falan. Thanks for the suggestion though.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Since there should only be one channel with this pattern, you don't need a wildcard to match the guild. Try it this way (leave out the things which mess you up)!
#TR "StartCaptureSecret" {^~<~<Guild~>~>: (%a says, *)} {
Channel = Secret
#SUB {~[%time("hh:mm:ss")~] %1}
#T+ CaptureAll
#T+ StopCapture
}
#TR "StartCaptureMeSecret" {^~<~<Guild~>~>: (You say, *)} {
Channel = Secret
#SUB {~[%time("hh:mm:ss")~] %1}
#T+ CaptureMe
#T+ StopCapture
}

Oh, and of course change "Guild" to the actual name of your guild.

Newbie Joined: 22 May 2003 Posts: 7

Still no luck. Thanks guys for trying but I think, I'll just have to get used to not capturing my GTS Channel. Nothing's worked so far and I think it might be a bug in ZMud or something.

Beginner Joined: 03 Sep 2004 Posts: 23

^\<\<&channel\>\>\:
#gag
#cap @channel

I think everyone missed the : (it's small, needs to take vitamins)
I am just used to quoting anything that is not 0 \- 9 a \- Z, it's safer

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Triggers are evaluated in a particular order, usually the order of creation. If you have one trigger (StartCaptureMe) which depends on another trigger (CaptureMe) coming after it, you either have to make the triggers in that order or move them to that order. This can be done in the Settings Editor. Use the 'All Classes' button if necessary to get all the triggers showing, make sure you have 'Sort by None' selected on the View menu, then use the Arrow buttons to move the triggers to the required order.

The CaptureAll and CaptureMe triggers are identical, you don't need both of them. However, they both CAPTURE to Guild and it seems that you intended them to CAPTURE to @Channel.

If you aren't sure the channels will always start at the beginning of the line, remove the ^ at the beginning of the pattern. This means if there's any chance the channels might be on the same line as the prompt, the ^ will need to be removed.

I've tested my triggers, they work.

Newbie Joined: 22 May 2003 Posts: 7

The order was the problem after all! Thanks LighBulb. I wasn't aware of that. Sorry for all the hard thinking I made everyone do over such a simple issue.

As for my triggers and the oddities in them, I actually just posted simply versions of them and the real ones have differences.

Again thanks for all the help! I can't do without my capture scripts.