MUDBRINGER
Menu

Basic Actions and Aliases

Automation in MudBringer starts with one simple idea: when you see predictable text, you can run predictable commands.

This guide is designed as a practical starting point. You will learn how to:

  1. Detect game text with actions.
  2. Send commands automatically.
  3. Create aliases for faster typing.
  4. Add button macros for one-click actions.

Core Concepts

Actions

An action watches incoming game text. When a pattern matches, MudBringer runs the command list you define.

MudBringer intentionally does not allow user-defined regular expressions in this workflow. Uncompiled regex input can become expensive at runtime, especially in busy combat logs.

Instead, MudBringer uses wildcard captures, which are faster to evaluate and easier to read for most players.

  • Match placeholders: %0 to %9
  • Captured values in commands: $0 to $9

Example:

Pattern: You are knocked to the ground.
Action: stand

Wildcard Captures (Regex-Like, Simpler)

Think of %0 as “capture whatever text appears here.” Later in your command list, $0 reuses that captured value.

This keeps the script style familiar for players coming from MudMaster, zMUD, and similar legacy clients.

Command-line example:

/action {%0 stabs you in the back with a dagger!} {cast heal;cast harm $0} {CombatReaction}

What each block means:

  1. {%0 stabs you in the back with a dagger!} : Match incoming text where %0 captures the attacker name.
  2. {cast heal;cast harm $0} : Run commands in order. First cast heal, then cast harm on the captured target.
  3. {CombatReaction} : Group name for organization, filtering, and bulk script management.

Example match result:

Incoming line: Jeremy stabs you in the back with a dagger!
%0 captures: Jeremy
Commands sent: cast heal; cast harm Jeremy

You can build these with command-line syntax, but most users should use the Action Wizard, which provides form fields for pattern, response, and group without typing /action {...} {...} {...} directly.

Action Wizard

Use the Action Wizard when you want the same power without memorizing command syntax.

Typical wizard flow:

  1. Open the Actions panel.
  2. Click New Action.
  3. Enter match pattern text (with optional %0-%9).
  4. Enter response commands (using $0-$9 where needed).
  5. Set a group name.
  6. Save and enable.

Alias

An alias is a shortcut command you type that expands into a full command or script.

For instance, if you always type the same few commands (or long commands), you can combine them into your own custom command:

command: drinkup
Commands sent: get waterskin pocket;chug waterskin;put waterskin pocket

Typing drinkup now sends all three commands in order.

Command-line example:

/alias {drinkup} {get waterskin pocket;chug waterskin;put waterskin pocket} {FoodAndWater}

What each block means:

  1. {drinkup} : The alias you type and send to the MUD.
  2. {get waterskin pocket;chug waterskin;put waterskin pocket} : Run commands in order.
  3. {FoodAndWater} : Group name for organization, filtering, and bulk script management.

Aliases can also use wildcards:

/alias {assist %0} {target $0;cast 'group heal' $0} {Support}

Typing assist Jeremy will expand $0 to Jeremy.

Macro Button

A macro button is a clickable dashboard action that runs one or more commands.

Your First Action

Start with an exact-text action so you can verify your setup quickly.

  1. Open the Actions panel.
  2. Click New Action.
  3. Name it Auto Stand.
  4. Pattern: enter the exact line from game output.
  5. Action: send stand.
  6. Save and enable the action.

If this message appears often in combat, your character should now stand automatically.

Moving from Exact Text to Wildcards

Once exact-text actions work, replace fixed names with %0 style captures.

Pattern: %0 attacks you!
Action: mark_target $0

Use wildcards when:

  1. The line includes changing names or numbers.
  2. You want one action to match many similar messages.

Building a Useful Alias

Create an alias for repetitive commands.

Alias: cf %1
Action: cast 'fireball' $1

Now typing cf goblin becomes cast 'fireball' goblin.

Turning an Alias into a Button Macro

Button macros are perfect for common movement and combat actions.

  1. Open the Macro Wizard (M button on the toolbar).
  2. Choose a keyboard key to assign a macro to.
  3. Set the commands or actions to take when the key is pressed.

Example:

Macro key: keypad8
Actions: run north

This lets you run north by pressing 8 on your keypad.

Troubleshooting Actions Quickly

If an action does not fire, check these first:

  1. Exact spacing and punctuation in the source line.
  2. Whether the action is enabled.
  3. Whether another higher-priority action consumed the same line.
  4. Whether your %0-%9 placeholders are positioned where variable text actually appears.

Tip: use real terminal scrollback when building match patterns.

Pro tip: use Script Debugger to trace advanced scripts and action chains step-by-step.

Use Hush for Privacy

For sensitive input, use /hush to prevent local echo in the terminal window. This is useful for passwords, demos, streaming, or screen sharing.

  1. See /help hush in client.
  2. See /docs/guides/hush for guide details.

This helps keep private information off your local display and recordings.

Suggested Starter Automation Set

For a solid baseline, create:

  1. Auto Stand action.
  2. One wildcard combat reaction action.
  3. drinkup utility alias.
  4. One combat macro button.

Next Steps

After this guide, continue with:

  1. /docs/guides/triggers for deeper workflows.
  2. /docs/reference/trigger-management for syntax and options.
  3. /docs/reference/scripts-commands--flow for advanced logic.

[Add screenshot placeholders where useful: action editor, alias editor, macro wizard setup.]