Zugg Software :: View topic

Adept Joined: 24 Aug 2004 Posts: 277

Is there a way to store a random path into an alias?

What I want to do, is store a path from my current room number, to another room number, in an alias.

I'm in room A, and want to run to room B, I can just #walk %roomvnum, but my problem is that it prevents my killswitch from working properly, so if I can store it in an alias, and then just fire the alias, that would solve my problem, however I don't know how to do this.

Please and thank you very much, you guys are awesome!

Adept Joined: 24 Aug 2004 Posts: 277

I figured out how to get the path stored into a variable (#var pathStored = {%walk(%1)} .. But I don't know how to use the variable to send the commands to the mud to make me move.

Adept Joined: 24 Aug 2004 Posts: 277

I apparently figured out my own problem, I was using the wrong () to set the alias, it's now working. Thanks for looking :)

#var pathStored {%walk(%1)}
#al pathWalk @pathStored

Posted: Wed Feb 10, 2016 4:50 pm

#PATH is the intended way to save a speedwalk, but you can store it in a variable if you prefer.

Adept Joined: 24 Aug 2004 Posts: 277

Hrm. I think I misunderstood the use of a path, I've only used them as a stepper. However, I don't know if that would work, because when CMud sends paths to the game, CMud interprets that as user-inputted commands, whereas aliases do not.

This only matters because I use a deadman switch in my game, and user-inputted commands interrupt the idle time, causing me to never go idle. Using an alias instead of a path prevents this from happening, so if I idle too long, my character stops moving, and prevents me from suffering wizard punishments. Bots are legal, unattended bots are not, hence the deadman switch as a backup precaution.

Adept Joined: 24 Aug 2004 Posts: 277

Alright, so my experiment failed. Anytime I have to use a path, whether it's in an alias (I assume because it's using .directions, that it's using the path feature) .. So instead of it sending the commands, it's pathing the commands.

So, I'm at a loss again of how to do this.

Posted: Wed Feb 10, 2016 6:24 pm

var=%pathexpand(%walk(%1))
then you can %pop(var) to get the next direction, and delete it at the same time

Adept Joined: 24 Aug 2004 Posts: 277

Thank you very much Shalimar. I will test this when I get home later. I have a few ideas on how I think I can get this to work! It's still using h,j etc directions, which require a . which is a path.. but if I convert those to nw/se, etc, that would bypass the pathing problem...

Appreciate the help!

Posted: Thu Feb 11, 2016 1:32 am

%pathexpand should take care of that for you... but if not:
#HELP %replace

Adept Joined: 24 Aug 2004 Posts: 277

Well so far I haven't got to test it yet, I just finished implementing it. I created a wild script to change it all over.

In theory, it's working.. But, I'll know in about 10 minutes if it works properly :)

It looks like this.

Posted: Thu Feb 11, 2016 1:40 am

looks good, i would probably use a #SWITCH instead of all those #IFs, but whatever works.

Adept Joined: 24 Aug 2004 Posts: 277

I've never been able to grasp the use of #switch. A few friends have tried to show me, but it just doesn't make sense in my brain for some reason. I've read the help files, had a friend send me a script and I've tried adapting it to my use, but ... It just doesn't click. I've wanted to use #switch SO MANY TIMES because I think it would have more practical use.... But... Nada...

I'd be excited to see an example though if you're willing :)

Posted: Thu Feb 11, 2016 1:44 am

Using the example you have there:

Adept Joined: 24 Aug 2004 Posts: 277

Thank you shalimar. I see what you did.. I am pretty sure I've tried that in the past but with no success... Maybe I've made some typos, I don't know.... Thanks so much for the input.

One question, are you missing {} brackets around the h/j/k/l/etc switches? How does it know when to stop switching?

Maybe that's why I couldn't get it to work.. It looks funny to me...

For the record, I've never taken a programming course, all the code I know I've taught myself, learned from other scripts, or had others assist me. So I truly truly appreciate all your help, this is fantastic!

Posted: Thu Feb 11, 2016 2:35 am

It knows via context (the parser), technically you can have that all on one line, but i spaced it out for legibility.
Excess white space outside of quote marks is irrelevant.

Posted: Thu Feb 11, 2016 5:21 am

#SWITCH (@testVariable) ("possible value one") {do something} ("passible value 2") {do something else} {default action if no match}

Apprentice Joined: 17 May 2005 Posts: 108

Keep in mind, #SWITCH is particular about your indent style. You have to make sure that you indent the "(expression)". If you try to start a line with it, the parser won't understand it.

As for how it knows when to stop: a switch will stop the first time a condition is met. That makes it a fair bit more efficient than using a series of #IFs, though it would probably (or so I imagine) be comparable to a NESTED series of #IFs (where the next if is only checked if the previous one failed). Adding in a local variable so I don't have to type out quite so much, that would look something like:

Adept Joined: 24 Aug 2004 Posts: 277

Thank you very much guys. That's a wealth of knowledge and I appreciate your help!

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I am doing this off the top of my head since my CMud machine is down.