|
|
 There is no route to the up ?
| Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
| Enhancement |
Completed |
Medium |
Mon 15th Aug 2011 |
1 vote
 |
| |
| Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
| 5.0.19 |
Wed 24th Oct 2012 |
5.0.27 |
Wed 24th Oct 2012 |
Log In |
| |
| saabie | | Mon 15th Aug 2011 14:31 |
The Player Movement task in the library uses a restriction to display a default message if you cant move in the selected direction.
This is OK for compass directions, but for in, out, up & down the message "There is no route to the up" sounds very strange and should be "There is no route up".
Could be fixed with 4 extra tasks with restrictions like "Referenced direction must be up".
In/out may sound better as "There is no way in" |
| |
| saabie | | Fri 4th Nov 2011 07:18 |
This could be done quite simply by adding alternate descriptions to the text box of the "Player Caracter must have a route available to referenced Direction" restriction in the "Player Movement" task of the standard library.
The current restriction message is:
"There is no route to the %LCase[%direction%]%, only %ListExits[%Player%]%."
Alternate description for up/down could be:
"There is no route %LCase[%direction%]%, only %ListExits[%Player%]%."
and for in/out:
"There is no way %LCase[%direction%]%, only %ListExits[%Player%]%."
|
| |
| Campbell | | Wed 24th Oct 2012 08:23 |
Fixed. I actually changed the library message to the following:
There is no route <# IF(%direction% = "up" OR %direction% = "down" OR %direction% = "in" OR %direction% = "out", "", "to the ") #>%LCase[%direction%]%, only %ListExits[%Player%]% |
|
