Radamanthas Newbie
Joined: 22 Nov 2004 Posts: 9
|
Posted: Mon May 05, 2008 1:49 am
Bogus directions being sent to mud - please help |
Okay...running zmud 7.21, and I'm having a thorny problem...
Intermittently, when a directional macro, direction, or alias is sent to the mud, instead of the proper direction, either 'in' or 'out' is sent, instead...it doesn't happen all the time, but enough to be very annoying. I have the following custom dir commands defined:
#DIR io {in} other
#DIR oi {out} other
#DIR qb {step onto white} other
#DIR bw {step onto black} other
#DIR pp {press button} other
#DIR v {wear tabi} other
#DIR zx {press touchpad;#wait 7000;e} other
#DIR xz {press touchpad;#wait 7000;w} other
#DIR yy {press touchpad} other
Here are examples of when the problem occurs:
#VAR go_home {w;n;n;d}
#EXE @go_home (9 times out of ten, it sends w;n;n;d to the mud - but that tenth time, it will send out;n;n;d to the mud)
#VAR go_home {.gohome}
#EXE @go_home (same thing)
I also have a database set up to hold routes, in some cases...assuming that one of the fields is named 'Gohome'....
#VAR go_gome {&Gohome}
#EXE @go_home OR just #EXE &Gohome (Same results)
Now here is the kicker - just pressing a key on the numeric keypad will usually send the predefined direction to the mud....but occasionally, that too, will get substituted with either 'in' or 'out'
Some other observations:
1.) 99.9% of the time, if the original route is a string of directions, it is the first direction in the string that gets substituted.
2.) All of the cardinal and ordinal directions (n, s, e, w - ne, nw, se, sw) are vulnerable to substitution
3.) Directions are ALWAYS *only* substituted, with either 'in' or 'out - never any other direction
I know this is a bit long, but trying to provide all information needed, for help....anyone have any ideas? I am at the end of my rope, and tired of dying, because these bogus directions are getting put out, instead of the valid directions..
TIA for any help or insight. |
|