|
8bits Newbie
Joined: 08 Jun 2003 Posts: 9 Location: Sweden
|
Posted: Sun Jun 08, 2003 11:27 am
Can't get mapper to work |
I'm playing a mud where the rooms looks like this (while using brief mode):
By the Fireplace Exits are: N E S W
A large bulletin board is here, for everyone to write on.
A wood elf ranger sits here, warming himself at the fire.
And I can't get the mapper to work with this.
Any suggestions/help would be appreciated.
Regards
--
8bits |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Sun Jun 08, 2003 12:56 pm |
Try with a couple of #TAG's:
#TRIGGER {^(*) Exits are: (*)$} {#TAG name,exit {%1} {%2}}
#TRIGGER {pattern for your prompt} {#TAG prompt} "" {prompt}
Reconfigure the mapper after creating these triggers.
Kjata |
|
|
|
8bits Newbie
Joined: 08 Jun 2003 Posts: 9 Location: Sweden
|
Posted: Sun Jun 08, 2003 7:31 pm |
Thanks for the response, I can't check it now cause I'm at my so very much firewalled job. I'm wondering exactly what you mean by {pattern for your prompt}. The only static part of the mud's prompt is the >. The rest differs ie. >Wounded:Depleted:Weary or Scratched:Powered etc. Or a blank > if your health etc is on top.
Will it work to replace {pattern for your prompt} with just the {>} then?`
Regards
--
8bits |
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Sun Jun 08, 2003 11:07 pm |
quote:
Thanks for the response, I can't check it now cause I'm at my so very much firewalled job. I'm wondering exactly what you mean by {pattern for your prompt}. The only static part of the mud's prompt is the >. The rest differs ie. >Wounded:Depleted:Weary or Scratched:Powered etc. Or a blank > if your health etc is on top.
Will it work to replace {pattern for your prompt} with just the {>} then?`
Regards
--
8bits
Yeah, a blank > will suffice as your prompt.
If you want to catch the rest, simply tack on a (*) to it. The trigger should still fire on ">" and ">wounded:weary:etc".
li'l shmoe of Dragon's Gate MUD |
|
|
|
8bits Newbie
Joined: 08 Jun 2003 Posts: 9 Location: Sweden
|
Posted: Sun Jun 08, 2003 11:44 pm |
I realized the prompt looked like this, ie:
HP:Scratched S:Surging>
So I tried this:
#TRIGGER {^(*) Exits are: (*)$} {#TAG name,exit {%1} {%2}}
#TRIGGER {^(*)>} {#TAG prompt} "" {prompt}
But it doesnt do anything I can see.
But thanks for the answers. Any other idea? |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Mon Jun 09, 2003 11:46 am |
The triggers by themselves don't do anything. Did you reconfigure? Also, try putting a
#SH test
or something like that in the prompt trigger to make sure it is firing.
Kjata |
|
|
|
8bits Newbie
Joined: 08 Jun 2003 Posts: 9 Location: Sweden
|
Posted: Mon Jun 09, 2003 5:40 pm |
Ok, the #TRIGGER {^(*)>} {#TAG prompt} "" {prompt} action works but there're weird things going on. First, if I put a #SH test line to the value field, it puts 2 tests on my screen instead of one. Second thing is that if I reconfigure the mapper after I add these triggers, the captured field becomes blank so the mapper has nothing to work with.
I then removed the triggers and tried reconfigure again. This time it could pick out the exits but not the room name.
I'll put an exact output of the mud here again:
>n
Noisy Barn Exits are: N S
A horse is here, gazing at you.
A horse is here, gazing at you.
>
Guess I could always map it manually ;) |
|
|
|
|
|