Zugg Software :: View topic - [SOLVED] Path command (".e") not working

Beginner Joined: 27 Jan 2005 Posts: 11

Did searches, but I did not find the answer to this. Please forgive me and post a link if this has been answered. Also, if the command above isn't called a 'path command' let me know -- I might be searching for the wrong thing.

Cmud Pro version 3.33a after a recent reinstall.

Entering path commands (for example ".nswe" without the quotes) sends the command to the MUD. It doesn't send 'north' then 'south', etc. It sends the string ".nswe"

Attempts to Diagnose:

I've checked my settings (aliases and triggers) and do not see anything that starts with a period.
I've checked the settings for paths in Pref/Scripting/Special Characters. It is still the default period. I have changed it a few times, no change in functionality - it still sends the (now slightly different) string
Parsing is on for the commandline (turning it off has no better change with respect to this issue).

The one thing different from a fresh reinstall is that I copy/pasted triggers and such. I do recall that I was having this difficulty but sadly cannot remember what fixed it.

Thanks for any insight you might have.

Novice Joined: 10 Jul 2007 Posts: 47

I don't have pro and nor do I use paths as I string (n;s;e;w) together in macros or mudside. But as a thought - could this be related to the mapper at all? Need to have speedwalking enabled?

Beginner Joined: 27 Jan 2005 Posts: 11

Posted: Wed Apr 20, 2011 4:29 pm

Make sure you have the "English Directions" package loaded with your session. This is the default with CMUD but maybe you are just trying it in a blank session where this package isn't loaded.

Beginner Joined: 27 Jan 2005 Posts: 11

I just checked and it was installed. I also downloaded the most recent version (this turned out to be the exact same file, but worth the install just to eliminate the possibility).

Still no luck.

I'll look and see if there is a linkage where I need to associate the window with the package.

EDIT: There is, but it is indeed checked.

Posted: Wed Apr 20, 2011 11:19 pm

Not sure what else to suggest. I can't get it to fail here and nobody else has reported this since 3.33 came out.

All I can think of is to go into the Settings Editor and use the File/Export All to export your scripts. Then delete your *.PKG file and start CMUD to let it create a new file and go into the Settings Editor and Import the XML file that you saved above. Just be sure to make a backup of your files.

Beginner Joined: 27 Jan 2005 Posts: 11

I attempted a new session with no additional settings, and ".n" still failed.

In the coming days, I will attempt your export suggestion, followed by a copy to a safe directory and a complete uninstall and reinstall. It occurs to me there might be a permissions thing going on.

I'll post again when that test is done.

Beginner Joined: 27 Jan 2005 Posts: 11

While I was getting the time to test this, 3.34 came out, so after I uninstalled I installed the new version. Didn't try to copy the settings from the old folder, but did use the XML. I had to play a bit with the Windows (I named it something different).

To make an epic story only long, it now works.

For the benefit of anyone searching in the future, I really do think this was due to my attempt to copy files from a backup -- and thus Windows 7 thinking it wasn't really me accessing those files.

My sequence:

Take note of any preferences (colors, toolbar layout) you will need to reset later.
Go to CMUD Tabs/Triggers, then "File/Export". Save it as something memorable
Go to My Documents/My Games/CMUD and rename it something memorable.
Go to control panel, and uninstall CMUD
Get a new version, and reinstall CMUD. When it prompts, start CMUD
Create a new session
Once in new session, go to CMUDD Tabs/Triggers then "File/Import" and Import the file from (2)
You may need to tell windows (the CMUD windows, not the MS kind ) not to use the Network connection
You may also need to reset any preferences (toolbar layout, colors, etc) -- that you noted from (1)

Assuming your problem is/was similar to mine, your pathing (ie, ".nsw2e") should work now, and you won't need to rewrite too many triggers.

Thanks Zugg for the attention -- especially pointing me to where the import/export stuff was. I kept looking in the main menubar.