 |
Nibbles
Beginner
Joined: 01 Aug 2004
Posts: 15
|
 Posted: Fri Jun 17, 2005 4:38 am
Automapper Problem
|
I am using the automapper to capture exits only, because I've had so much trouble trying to get it to reliably capture other information.
A room description looks like thus:
| Code: |
Randall's Sundry Goods
You enter the shop to find out that the general adventuring supplies store
has a well thought out layout and a good range of quality items. Neatly
arranged upon shelves and in cupboards are canteens, maps, backpacks and light
sources. There is a sign here with instructions on buying and selling sundry
goods. Type 'look sign' to read it.
[Exits:e]
The sundry goods merchant Randall proudly looks about his shop.
< 178/178Hp 200/200Mn 3070Xp >
|
I set up a custom trigger to capture the exit information, because the automapper was often simply refusing to parse exits for certain rooms(which as far as I can tell looked no different than any other rooms). Here's the trigger:
| Code: |
#TRIGGER {~[Exits~:(*)~]} {
#TAG exit %1
#SHOW Found %1
#OK
}
|
Automatic capture of Name, Description, and Exits are all turned off. The only two options enabled for Exits are "Multiline Exits" and "Single character exits".
Now, I'm having two problems. The trigger isn't the problem, because it ALWAYS shows the correct directions with the #SHOW command. First of all, if I turn "Multiline Exits" off no matter what other options I use, the mapper stops working, despite the fact that all the exits are on a single line. That alone seems to be a bug. Secondly, a lot of times mobiles descriptions are preceeded with an E! and this comes right after the exits, and for some reason the mapper is capturing this as the direction east.
| Code: |
[Exits:ns]
E!A desperate woman has resorted to anything to get money.
Found ns
|
So... despite the fact that automatic exit parsing is turned off, and despite the fact that my trigger is only capturing north and south, an exit east still appears on the mapper. Why? How do I fix this? |
|
|
|
|
Private
Adept
Joined: 10 Jan 2002
Posts: 264
Location: USA
|
Posted: Fri Jun 17, 2005 5:10 am
|
are the exits always ns, news, ie. a word?
use %w instead of * and try anchoring the trigger....
| Code: |
#TRIGGER {^~[Exits~:(%w)~]$} {
#TAG exit %1
#SHOW Found %1
#OK
}
|
dunno if it will help, but cant hurt. |
|
|
|
|
Nibbles
Beginner
Joined: 01 Aug 2004
Posts: 15
|
Posted: Sat Jun 18, 2005 9:59 am
|
Nope, didn't work. The problem seems to be either with A. How I have the automapper configured or B. The automapper itself. As long as I've spent changing configurations trying to solve such a simple problem, I'm leaning towards B.
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
