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 unles