 |
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
 Posted: Mon Jul 13, 2009 5:18 pm
[Fixed] [3.09] 'in' and 'out' directions getting screwed up 'Name' in the mapper
|
I have 'in' and 'out' defined like this:
<dir name="i" reverse="o" dir="other" id="2265">in| in|swim in|leap in|tumble in|crash in|burrow in</dir>
<dir name="o" reverse="i" dir="other" id="2266">out| out|swim out|leap out|tumble out|crash out|burrow out</dir>
When I'm in a room with an 'in' or 'out' exit and I take that unlinked exit so that the mapper will create the new room it uses the whole "in| in|swim in|leap in|tumble in|crash in|burrow in" in the exit link 'Name' field instead of just 'in'.
This is inconsistent because when I take an exit to the 'se' direction it doesn't put "se| se|southeast|swim se|leap se|tumble se|crash se|burrow se", and it shouldn't. When the 'in' direction is defined it should just put 'in' in the 'Name' field, instead of the or'd list of all possible uses of the direction. |
|
Last edited by ReedN on Tue Jul 28, 2009 4:01 am; edited 2 times in total |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Jul 14, 2009 4:20 pm
|
I have no idea what would cause this. Try playing around with your definition of "in" and see if changing the string list makes any difference. Maybe the multiple occurrences of the word "in" in each command is causing some sort of problem.
Or, maybe it's a difference between a direction with "dir=se" vs the "dir=other". You might try changing your out dir to use something like dir="n" and see if that makes a difference. Any additional info you can give on this would make it easier for me to fix. |
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Sat Jul 18, 2009 10:42 pm
|
Here's the procedure for seeing this:
| Code: |
-- Testing procedure done in 3.09 Pro --
1) Create a new session, enter it off-line
2) Import the two xml directories for the session. They define the 'other' exits and the alias/trigger to use in the testing.
3) Open the mapper with the map button
4) Change to edit mode and create a room. Set that room as your current location.
5) Change the mapper to Slow Walk
6) Type 'test' to execute code that simulates walking 'in' and entering a room with the following properties:
Name of the Room: testroom
Exits of the Room: {south|west|east|out}
7) The newly created room will have the correct 'out' marked for the Name field. However the original room has an incorrect 'in|swim in' in the Name field.
Incidentally, since you asked, if you define the directions simply as 'in' and 'out' this doesn't happen.
|
| Code: |
<class name="directions" id="1">
<dir name="i" reverse="o" dir="other" id="2">in|swim in</dir>
<dir name="o" reverse="i" dir="other" id="3">out|swim out</dir>
</class>
|
| Code: |
<class name="TestCode" id="4">
<alias name="test" id="5">
<value>#map in
#tag name testroom
#tag exit {south|west|east|out}
#ok
#show prompt
#say Executed</value>
</alias>
<trigger priority="70" id="6">
<pattern>prompt</pattern>
<value>#tag prompt</value>
</trigger>
</class>
|
|
|
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Sun Jul 19, 2009 7:53 pm
|
Confirmed.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Jul 20, 2009 5:12 pm
|
Confirmed. Thanks for the detailed procedure...that's just what I needed.
|
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Tue Jul 28, 2009 3:59 am
|
This is fixed in 3.10
Incidentally (and perhaps unrelated) it seems I no longer need to pad my directions with spaces, like:
| Code: |
| "n| n|leap north|burrow north" |
It seems to be correctly taking 'n' for movement and such. So I don't know if you've touched that code, but it's nice that it doesn't require that work-around anymore. |
|
|
|
|
|
|
|
