 |
ennye
Novice
Joined: 17 Dec 2007
Posts: 49
|
 Posted: Sat Apr 24, 2010 8:39 pm
[3.16b] strange #walk behavior
|
I noticed major #walk problem. I dont know if its due to 3.16b update or may be some configuration problem but:
#walk <roomnumber or name>
returns no longer speedwalk path, but number of rooms to walk preceded by "."
It looks like:
#walk roomname
.5
And immediately ".5" dissappears. Mud answers "no known command". |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Apr 26, 2010 4:15 pm
|
Can anybody else reproduce this? #walk still seems to work for me here.
You might check to make sure the #LOC object is set correctly in your main session window and that the mapper is properly tracking that location (indicated in the bottom left corner of the mapper).
You should also make sure your English Directions package is getting properly loaded. Try doing .n to make sure CMUD still knows how to move you to the north. |
|
|
|
|
ennye
Novice
Joined: 17 Dec 2007
Posts: 49
|
Posted: Mon Apr 26, 2010 11:20 pm
|
Directions work ok.
Tracking seems ok:
| Code: |
Locations (* is current, - is disabled):
* Blabla at room 16025 (blue) <Blabla Map> |
All was working fine, until i moved some classes to another package.
Just colouring triggers etc, nothing to do with moving.
Another thing since this moment is : errors by closing cmud. "Pointer error".
Hitting "continue" 1 time in error requester helps. I post error log via requester, user name ennye. |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Tue Apr 27, 2010 2:33 pm
|
How did you move those classes to another package? It sounds like the package got corrupted in the process. If you get errors like that, it indicates that something serious is messed up, and anything could happen. You should not hit "Continue" after an error unless you are *positive* that the error is harmless. If you continue after an error, there is no telling what might happen.
|
|
|
|
|
ennye
Novice
Joined: 17 Dec 2007
Posts: 49
|
Posted: Wed Apr 28, 2010 1:31 pm
|
New package and drag 'n drop :>
|
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Wed Apr 28, 2010 6:27 pm
|
I recall that drag and drop sometimes corrupted scripts in old versions, especially when moving entire classes, but I haven't tried it since early 2.xx.
If it is corrupted, here are the solutions I can think of:
Export the package and import it again, see if that fixed it
Find an old backup and reconstruct your settings from it
Delete the existing package and rewrite it
It may be possible to figure out where in the XML the problem is, but I don't recommend it.
Of course, that may not be the problem. |
|
|
|
|
|
|
|
