Zugg Software :: View topic

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

I'm wanting to create a variable that will capture a long string of exits:
"Path: ne, ne, nw, ne, nw, w, nw, nw, w, w, sw, sw, s, s, w, nw, sw, s, se,
w, w, nw, nw, ne, n, ne, n, ne, n, nw, n, n, n"
and then when I use an alias like "caravanstart" it will send the command "lead caravan (next direction in string)"

I've seen a script that does this, but I couldn't make any sense of it at all, and it was for Zmud anyway.
Please help me out! :)

Posted: Fri Jul 17, 2009 2:48 pm

If it was for zMUD there's a high likelihood it would work in CMUD unchanged (or with few modifications).

You basically need to put the path into a string list and look on the string list.

Off the top of my head the code would look something like

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

How do I exclude certain things from this? With:

Posted: Wed Jul 22, 2009 5:19 pm

The reason for this is that there is no '.' in your path statement. This trigger pattern should work better.

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

Yeah.. Didn't work. Maybe if I gave you the whole script? Someone who knows what they're doing might be able to understand it and change it to work the text I pasted from the game?

Wizard Joined: 22 Mar 2007 Posts: 2320

Your triggers seem to suggest that there are brackets around the "Path: ..." line, but you did not include any brackets like that in the mud output you quoted. Are there actually brackets in the mud output?

It looks to me like you've made this much too hard. The mud output you showed us has the entire path on a single line. If that's the case, you don't need a prompt trigger to initiate a second trigger to capture the path. You just need a single trigger, like Tech showed you. You're doing a bunch of replacements that don't seem necessary, like a period at the end, and doubled pipes. You have a trigger for "Path calculated in: %d microseconds", but you didn't present anything like that in your example output. If it is really that complicated, then you'll have to show us some examples of text from the mud demonstrating the complications. I started to write a much simpler script that would work with the mud text you presented, but I don't think it's worth working out until you clarify exactly what the mud output looks like.

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

This was a script made by someone else to use text based mapper and the game recently added a new feature that works in a similar way.. so I was hoping to change the script so I could use the game based feature instead of needing to use the old mapper where you need to connect to the game through a proxy.

The text I used what is given by the game, but I haven't been able to change the settings to work with it :(

Wizard Joined: 22 Mar 2007 Posts: 2320

If the mud output is changed that much, you should scrap your old stuff and start over. Your new triggers will be much much simpler than the old. Here's my quick attempt at it, in XML format:

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

Awesome! Works great. Though it only picks up a single line of exits.
How do I get it to pick up a second (or third) line?

Wizard Joined: 22 Mar 2007 Posts: 2320

Ah, your example did not have exits extending onto a second line. Is it possible to change a setting on the mud to not wrap lines? You can let Cmud do your line wrapping for you. If so, that would probably solve the problem. If not, we'll have to do something a bit more complicated.

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

I'm afraid not. All IRE games wrap for you.. At least I can't find a way to change it.

Wizard Joined: 22 Mar 2007 Posts: 2320

All right, here's a new version which, I think, will handle multiple lines. If the line ends in ", " it turns on another trigger which continues capturing lines until it gets a line that does not end in ", ", at which point it replaces the commas to make it a stringlist.

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

Hmm.. I used that and changed some tiny things (and added a button, a trigger and alias to stop the walker) so now I looks like

Wizard Joined: 22 Mar 2007 Posts: 2320

Hm. That trigger, exactly as you have it, seems to compile for me. Look around to see if you have any other old triggers with the pattern "^Path: (*)$"

Beginner Joined: 26 Mar 2007 Posts: 16 Location: Australia

Nope, only the one trigger with that pattern. Hmm.

Newbie Joined: 15 Jul 2011 Posts: 2

So I've been literally breathing and eating this script for days. I found why the error message keeps popping up.

The pattern "^Path: (*)$"

needs to be:

"^Path: (.*)$

I'm by no means a expert. I'm actually FAR from it. But this seems to take away the message.

However, in fixing that. I hit, 'cargo' but it gives me an empty variable, it doesn't move in a direction. Please help?

This is what I'm currently working with. It's the same script just with the added '.' above.

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

I notice that the Path: (*) trigger has an #IF command that uses the %ends() function for the condition. This #IF condition does not have a closing ), which is probably why the trigger doesn' compile.