Organize and troubleshoot automations

The Automations sidebar mixes saved user items, modules, installed packages, and the automations those scripts create. The owner shown beside an item tells you where to make the lasting change.

Create folders for a real purpose: combat, travel, character class, or a particular game system. Moving an alias, trigger, or hotkey into a folder keeps related items together. Turning a folder off disables its contents without deleting them.

An item's own switch and every parent folder must be enabled. A green item inside a disabled folder is still effectively disabled.

The dashboard and sidebar distinguish working, disabled, warning, and error states. Select an item to see its pattern and body. Module- and package-created items are useful evidence, but their source module or package remains the authority.

1. Paste the exact command into Test against a command.
2. Anchor the pattern with ^ and $ when the whole command must match.
3. Check capitalization, spaces, punctuation, and whether the pattern itself compiles.
4. Confirm the item and its parent folders are enabled.
5. Disable other aliases briefly to detect an earlier replacement.

1. Copy the displayed MUD line into Test against a line. Do not retype it if spacing or punctuation matters.
2. Escape punctuation that has a regular-expression meaning, such as ., [, ], (, and ).
3. Use a normal Match row unless you specifically need unprocessed input.
4. Check every Anti-match row; one matching exclusion prevents the trigger.
5. If the text is a prompt without a newline, use a script-created trigger with prompt matching enabled; the saved trigger editor is for completed lines.

Confirm the session is connected. With Send as text, make sure the Script body contains a command. With JavaScript, look for an error status and reduce the body to one known operation. If the code is more than a few lines, move it to a module where an editor can type-check it.

An error in a top-level module can prevent the rest of that module from registering. Work offline, select the module, and inspect its error. Packages may also be held back by missing consent, an incompatible smudgy version, a dependency failure, or an integrity check; open the package's detail page rather than editing its generated runtime items.

1. Disconnect the session.
2. Reopen the same profile with Offline.
3. Disable the trigger, folder, module, or package responsible.
4. Narrow its pattern and test against a copied line.
5. Reconnect only after the action cannot cause the matching line again.

Keep a backup before editing the JSON files directly. The UI validates names and patterns that a text editor will let you break; see Data files and backups.