 |
RockguyRy
Newbie
Joined: 16 Nov 2021
Posts: 4
|
 Posted: Fri Nov 19, 2021 9:28 am
Automapper No Longer Adding Rooms
|
Hello,
So I'm on an LPMud. Before the automapper had its quirks to work through and I had it working but the exits for new rooms where off when a room description would have one of the cardinal directions in the room description.
So I managed to make a trigger that would capture multiline exits and then tag the line with the exit directions as exit.
Example of a room description:
| Code: |
The trees around you grow at a distance from one another. Between the trees,
the underbrush consists of coarse grass and some bushes. Sunlight easily
pierces the roof of the forest. Dry grasslands lie to the east. To the south
and west you see a dark but inviting forest.
Obvious directions are:
north, east, south, west.
|
Not sure how to display nested tags here but
Parent:
| Code: |
| Pattern:^\sObvious directions are: |
Type: Pattern
Regular expression, trigger on newline, and trigger on trigger are all checked
Child:
| Code: |
Pattern:^\s\s(.*)\.
Script: #TAG exit {%1}
|
Type: Within Lines 1
Regular expression, trigger on newline, trigger on trigger are all checked.
I also setup another trigger for when it is a single line exit. (i.e. The only obvious exit is north.)
Pattern: ^\sThe only obvious exit is (.*)\.
| Code: |
| Script: #TAG exit {%1} |
I have reran the reconfigure mapper option multiple times with no luck.
When the triggers are disabled, the automapper functions like before with adding new rooms to the map as I discover them. However when I enable the triggers, it no longer adds new rooms and I noticed that the command #LOOK no longer works. Same with trying to find myself on a map.
Any ideas how to get the automapper to work while handling multiline exits? LPMuds are a pain for this stuff. 
Thanks |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4689
Location: Pensacola, FL, USA
|
Posted: Fri Nov 19, 2021 10:30 am
|
You can put a carriage return into the pattern to make a multiline trigger like so:
| Code: |
| #TR { Obvious directions are:$ (*)} {#TAG exit {%1}} |
P.S. if triggers were off when you reconfigured, they aren't taken into consideration. |
|
_________________
Discord: Shalimarwildcat |
 |
|
|
RockguyRy
Newbie
Joined: 16 Nov 2021
Posts: 4
|
Posted: Fri Nov 19, 2021 11:02 am
|
Thanks for getting back to me so quickly!
So, with this tweak it now captures the line "Obvious directions are:" as part of the room description.
Is there a way to get it to not add this to the room description? |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4689
Location: Pensacola, FL, USA
|
Posted: Fri Nov 19, 2021 2:55 pm
|
Maybe add a #NOMAP to it.
|
|
_________________
Discord: Shalimarwildcat |
|
|
|
RockguyRy
Newbie
Joined: 16 Nov 2021
Posts: 4
|
Posted: Sun Nov 21, 2021 10:09 am
|
Tried that now the automapper won't parse the line with the exits on it at all.
|
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4689
Location: Pensacola, FL, USA
|
Posted: Sun Nov 21, 2021 2:50 pm
|
I was worried about that...
Okay, delete that trigger and try it like this:
| Code: |
#TR { Obvious directions are:$} {#NOMAP}
#COND {^ (*)} {#TAG exit {%1}} {within|param=1} |
|
|
_________________
Discord: Shalimarwildcat |
|
|
|
RockguyRy
Newbie
Joined: 16 Nov 2021
Posts: 4
|
Posted: Thu Nov 25, 2021 12:57 pm
|
Okay! That works. (Sorry on the delayed response.)
New wrinkle: Using #LOOK to update/fix room descriptions is not working. Any ideas how to rectify? I all ready tried reconfiguring the mapper. |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4689
Location: Pensacola, FL, USA
|
Posted: Thu Nov 25, 2021 1:40 pm
|
You still have to be in mapping mode for #LOOK to work
|
|
_________________
Discord: Shalimarwildcat |
|
|
|
|
|
|
