Zugg Software :: View topic

Newbie Joined: 27 May 2020 Posts: 1 Location: Boston, MA

I skimmed the forums, didn't see this listed (admittedly, I didn't read in detail).. minor thing, but I installed cmud into it's own directory, with zMUD still on my HD (c:\apps\internet\zmud and \cmud dirs). It didn't know zmud was on the comp at all (that I can see) aol mail login -- to be expected. Tried to hit "help" in the "sessions" window to see how to import, and it just gave an error that the help file didn't exist.

Posted: Sun May 31, 2020 1:01 pm

There are several ways to import your zMUD files into CMUD:

Recommended: If you install CMUD to it's own directory (which is actually the recommended approach for the cleanest installation), then the first time you run CMUD, it should detect that zMUD is installed on your computer and it will ask if you wish to import your zMUD files. It will ask you to locate your zMUD installation directory, and will then show a list of all characters defined in zMUD. Select the characters you wish to import and CMUD will copy those files and convert them for CMUD. Once again, your zMUD files are not altered.

You can also run this zMUD Import Wizard at any time by selecting Import from the File menu in the initial Sessions window.

If you install CMUD into the same directory as zMUD, then CMUD will automatically convert your zMUD files and make all of your characters available. CMUD will not overwrite or change any of your zMUD files. Both programs can be run at the same time and they will not interfere with each other.

If you just have a *.MUD settings file from zMUD that you wish to use, create a new session icon in CMUD, then select the Edit Session action and go to the Files tab. Use the Browse button to locate your zMUD *.MUD file. It will be entered into the Filename field. When you connect to this session, or open it offline, the *.MUD zMUD settings will be automatically converted to a CMUD *.pkg package file.

The problem with this method is that the CMUD package file will be created in the same directory that contains the zMUD MUD file. This can end up scattering your CMUD packages across multiple directories on your disk and is not a good way to keep your CMUD data organized. If you use this method, you should probably create a subdirectory for the MUD session within your CMUD directory and copy the zMUD *.MUD file into this CMUD directory before using it in CMUD.

You can also open a *.MUD zMUD settings file directly from the CMUD Package Editor. However, as in the above situation, the converted package file will end up stored in the same location as the zMUD MUD file. Also, since this method doesn't create a proper session file, some default preferences and packages will not be set correctly.

CMUD cannot import any text files exported from zMUD. CMUD can only read the zMUD *.MUD settings files. However, if you only have a zMUD text file available, open the CMUD Editor (Window/Editor command) and then use the File/Open menu command to open the text file into this editor window. Make sure the Parse option is enabled in the Options menu and then use the Send or Send Selected or Send Line options to send the text directly into the CMUD command line.

The problem with this method is that there will likely be some syntax differences between the CMUD commands and the zMUD scripts. So some of the scripts that you execute might not work properly. Since there is no way to use the Compatibility Report with this method, it can be very tedious to fix the scripts so that they can be imported.

Once your zMUD settings have been imported into CMUD, you can use the Compatibility Report in the Package Editor to scan your scripts for potential problems or syntax errors. That is the easiest way to track down problems with your scripts.