Zugg Software :: View topic - Mapper directions with arguments (feature request?)

Wizard Joined: 22 Mar 2007 Posts: 2320

I'm trying a mud which allows arguments to the basic directions, which change how the movement appears to others. For instance, you can send the command: north sauntering casually. This would cause viewers to see something like: Sauntering casually, so-and-so arrives from the north. The problem is that cmud does not appear to recognize this as a movement command, and does not move the location object. I could create aliases that execute the #move command, but this would force movement even if the movement fails. Can anyone think of another way to get the mapper to recognize movements like this? Or does this need to be a feature request?

Posted: Mon Jul 06, 2009 2:13 pm

Unless I'm missing something, sounds like you'd really want a trigger on "so-and-so arrives from the north" and use that the #MOVE command to update the location object for that person.

That's the approach I used to take for pets and familiars, or in the case where I was following a party leader.

Posted: Mon Jul 06, 2009 4:26 pm

I think the issue is not other people moving but his own movement.

From the command line I entered "north blah blah blah". The result was I moved north, but the map location object stayed in same location, and the map queue remained empty.

You might try an oninput trigger and #queue to manualy detect the new dirrection, and add it to the mapper queue.

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, the problem is as Wrym says, 'north blah blah blah' is not recognized as a movement command by the mapper.

Ah, #queue. That might do it. I'll check later. Thanks.

Posted: Mon Jul 06, 2009 7:43 pm

Could use an oninput trigger to check and see if the first word of a command is a valid direction....

Wizard Joined: 22 Mar 2007 Posts: 2320

#queue is actually giving me an error message. But checking the documentation, I don't think it will help anyway. If I did a #queue n, it will simply send another north command, after the mud gets "north blah blah blah".

Posted: Mon Jul 06, 2009 8:31 pm

If the command sends you a first person echo similar to the third person echo that others see... trigger and move based off of that.

#TR {You saunter to the (%w).} {#MO %1}

Wizard Joined: 22 Mar 2007 Posts: 2320

That's a good idea. I do have triggers like that for following, and some other types of movement. Unfortunately, it apparently doesn't make that echo to the mover, it just gives you the new room name and description. I wish it gave an echo like that--it's hard to experiment with it when I can't see what it looks like to others. I may make a suggestion to the mud admins on that.

Posted: Mon Jul 06, 2009 8:47 pm

Hmmm, I THOUGH I was using #queue in a somewhat similar situation, and I THOUGHT it was working but I was just kludging it all up, and it sorta worked.

I think that it'ld be fairly easy to allow additional arguments to direction commands, I assume it's just and end anchor on a regex.

But having the ability to read & write to the mapper queue would be nice. Perhaps a system variable that references back to the map queue, then %pop %item %push and what not could be used on the map queue fairly easily?

Posted: Mon Jul 06, 2009 8:51 pm

What about an Oninput trigger to detect that you have entered a direction, add it to a custom map que, then when you detect a new room, check if the room name the desired directional matches what you captured, pop the value from the queue and move that direction?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

#QUEUE shouldn't send any commands to the mud. A simple input trigger should handle what you want:
#ONINPUT {^(%t)} {#QUEUE %1}

You say #QUEUE is giving an error, please provide some details.