Packages are similar to inherited settings files in zMUD, but are much more flexible. It's a way to group scripts into a "black box" that you can reuse in other sessions.

Provides access to a remote package library that can be used to share packages with other CMUD users. Only registered users can download packages from the library. People using the CMUD trial version can only browse the library.

Replacing the zMUD Settings Editor is the new Package Editor. The Package Editor has an improved user interface for dealing with all of the complexities of your scripts. You will be using this editor a lot, so it's important to read this topic to learn how to use it effectively.

The new CMUD user interface allows windows to be docked in ways that were never possible in zMUD. Windows can also be set to "AutoHide", creating fly-out windows that open when the cursor is placed over their window tab.

The menu and toolbars in CMUD can be completely customized.

Local variables are temporary variables that can be used in your scripts which provide huge speed benefits

See the #ALIAS and #TRIGGER topics for details on using named arguments and patterns instead of using the old %1..%99 syntax. This makes your scripts more readable.

The standard Windows Help File system was dumped in favor of a custom help system which allows the help files to be updated from the Zuggsoft web site. This makes the latest help files available without having to download a new version of CMUD.

Starting with version 2.0, CMUD contains an integrated copy of the Lua scripting languages. Lua scripts have full access to CMUD scripts such as variables, triggers, aliases, etc. Lua provides very high speed and advanced features for scripts.

Starting with version 2.0, CMUD is multithreaded and supports advanced commands such as #WAITFOR and a properly working #WAIT command.

A Script Debugger was added in v2.0 that allows you to view the low level details of how your triggers and scripts are running without disturbing the main MUD window.