 |
Loftaris
Adept
Joined: 24 Aug 2004
Posts: 277
|
 Posted: Thu Sep 11, 2014 2:47 am
What just happened to my mapper?
|
All of a sudden out of the blue for no reason I can determine, my #walk / automapper has suddenly gone haywire.
When I try to #walk somewhere, it'll give me a random amount of n e ne e e e /etc directions, then suddenly spew out 2j4nl3e etc instead. Does it on any/all areas, it's never the same pattern, sometimes it'll just work, 99% of the time now it's not working at all?? The only change I've made in the last month was I added a single button (which I've since removed).
Anyone have any ideas/suggestions how to fix this? This seriously breaks CMud for me into complete uselessness and it's most frustrating! PLEASE HELP!
Edit: I should add, this is the latest version of CMud and Windows 8.1, however these also haven't been updated in a few days (Win) |
|
|
|
|
Loftaris
Adept
Joined: 24 Aug 2004
Posts: 277
|
Posted: Thu Sep 11, 2014 12:51 pm
|
So, I believe I may have figured it out (It woke me up this morning.)
I added the following line to an already existing trigger:
| Code: |
| :Commands:#sayprompt {%cr%ansi( bold, blue)""%ansi( bold, yellow)%lastinput %ansi( bold, grey)%2} |
When I commented this out, it all worked again, when I added it back in, it failed again. Any idea why? I run a deadman trigger and was trying to find out which commands from the mapper were messing it up, cause apparently commands coming from the mapper count as user input :( |
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
