Pause and Recovery

Stop Lua stops the current Lua run, clears waiting Lua work and timers, and pauses Lua triggers, Lua aliases, and Scripts in this tab. Ordinary triggers, aliases, and hotkeys remain active unless you also choose Pause automation. Resume automation resumes enabled automation; discarded jobs and timers are not replayed.

Pausing preserves your saved scripts and enabled checkboxes. You can keep editing while paused. The pause applies to this tab and survives reloads; it does not pause automation running in another open tab.

If a tab freezes, open desktop recovery or mobile recovery in a new tab. These links start with automation paused, so you can fix or disable a troublesome item before resuming. The login page also has recovery links. A frozen tab may need to be closed before using the recovered client.

Regex syntax is unchanged. Stop controls need a responsive page; recovery mode is the escape route when matching has frozen the original tab.

Lua Workload

Lua runs execute in order. If incoming events arrive faster than Lua can handle them, the client limits waiting work and shows a notice when it skips events. Events waiting more than ten seconds are discarded so old commands do not run much later.

Switching MUDs, reloading settings, connection changes, or editing automation definitions cancels earlier Lua work. Results from an old context cannot update the newly selected MUD. Changing ordinary saved variables alone does not cancel the queue. Pausing and resuming clears the backlog; add trigger cooldowns or narrow event handlers if overload returns.

What Lives Here

• Triggers watch MUD output and can send a command or highlight a line.
• Lua Triggers run Lua after a matching MUD line arrives.
• Aliases turn short typed commands into longer commands.
• Lua Aliases run Lua after a typed command matches.
• Scripts hold shared Lua helper functions and lifecycle setup.
• Hotkeys send commands from captured browser key combinations.

Folders

Click Add folder, name it, then move automation items into it. Folders can contain any mix of item types and other folders.

Turning off a folder makes everything inside it effectively disabled. The child items keep their own checked state, so when the folder is turned back on, the items that were individually enabled start working again.

Deleting a folder asks for confirmation and deletes every folder and automation item inside it. Export settings first if you want a backup before a large cleanup.

Moving Items

Drag a row onto a folder to move it inside that folder. Drag above or below a row to reorder at the same level. Folders cannot be dropped into themselves or into their own children.

The editor also has Move to, Up, and Down controls. Move to shows full folder paths such as Combat/Healing/Defenses, which helps when different branches contain folders with the same name.

Search

Search checks names, item types, trigger patterns, alias commands, and Lua source. Tree rows still show only the item or folder name. If a row matched because of a hidden field, a small chip such as pattern, command, or script explains why it appeared.

Run Order

The tree controls order within each automation type. Simple triggers run before Lua triggers. Lua aliases get first chance to handle typed commands before simple aliases. Enabled scripts load as shared Lua helpers.

Disabled folders always count: a disabled parent prevents its children from firing triggers, expanding aliases, loading scripts, creating widgets, running timers, or sending hotkey commands.

Quota Limits

If your settings or revision quota is full, Automation shows a red warning. You cannot add new folders or automation items, and content fields such as names, patterns, commands, and Lua source are locked.

Recovery actions stay available. You can disable items, move them, delete unneeded automation, or ask an administrator to move your account to a group with a larger quota.