ACTIONS ACTIONS let you create simple server-side triggers for your character. When the game sends you a line of text matching one of your action patterns, your character may automatically attempt the saved command. This is useful for screen reader users, approved multibox crews, and players who want a few simple quality-of-life reactions handled by the game itself. Basic Syntax action actions action add <text pattern> = <command> action add <text pattern> = <command> | <command> action addgroup <group> <text pattern> = <command> action show <number> action pattern <number> <new pattern> action command <number> <new command> action cooldown <number> <seconds> action group <number> <group> action group <group> on action group <group> off action on action off action enable <number> action disable <number> action priority <number> <priority> action test <text> unaction <number> Typing action or actions by itself will list your current actions. Adding an Action Use this format: action add <text pattern> = <command> Examples: action add You are hungry. = eat ration action add Thrain is in awful condition. = sli 'heal' thrain action add Thorin is in awful condition. = sli 'heal' thorin The text before the = is what the game looks for. The text after the = is the command your character will attempt. Multiple Commands An action may queue more than one command by separating commands with the | symbol. Examples: action add You are hungry. = get ration bag | eat ration action add You are thirsty. = get canteen bag | drink canteen action add Your combo is ready = combo bash kick kick | report Each command is placed into your normal command queue in order. This does not make the commands instant. If the first command gives you normal delay, the next command waits in your queue like anything else you typed. For safety, only a small number of commands may be placed in one action. Keep them simple. Action Cooldowns Cooldowns keep an action from firing too often. Use: action cooldown <number> <seconds> Example: action cooldown 3 10 This means action 3 may only fire once every 10 seconds. Use a cooldown of 0 to remove the cooldown. Example: action cooldown 3 0 Cooldowns are useful for healing, rescue, bash, battleorder, and other actions that should not repeat every time a common line appears. Action Groups Groups let you organize actions into sets. To add an action directly to a group: action addgroup healing Thrain is in awful condition. = sli 'heal' thrain action addgroup boss The boss begins charging = battleorder all bash action addgroup travel You are hungry. = eat ration To move an existing action into a group: action group <number> <group> Example: action group 3 healing To turn a whole group on or off: action group healing on action group healing off action group boss on action group boss off Groups are simple one-word labels. Actions without a special group belong to general. Editing Actions You can edit an action without deleting and recreating it. To see one action in detail: action show <number> To change the text pattern: action pattern <number> <new pattern> Example: action pattern 3 Thrain is bleeding awfully To change the command: action command <number> <new command> Example: action command 3 battleorder thorin sli 'heal' thrain To change the priority: action priority <number> <priority> Example: action priority 3 20 To change the cooldown: action cooldown <number> <seconds> Example: action cooldown 3 8 To change the group: action group <number> <group> Example: action group 3 healing Battleorder Examples ACTIONS can also work well with approved BATTLEORDER crews. Examples: action addgroup healing Thrain is in awful condition. = battleorder thorin firstaid thrain action addgroup healing Thorin is in awful condition. = battleorder thrain rescue thorin action addgroup boss The mob snarls = battleorder all bash You can also use multiple BATTLEORDER commands in one action: action addgroup boss The boss begins charging = battleorder all stand | battleorder all bash action addgroup healing Thrain is in awful condition. = battleorder thorin firstaid thrain | battleorder wind rescue thrain These still use the normal BATTLEORDER rules. The ordered characters must be approved, online, nearby, grouped, and able to act normally. Listing Actions Use: actions or: action to see your saved actions. Each action has a number. Use that number to enable, disable, change, or remove the action. Removing an Action Use: unaction <number> Example: unaction 3 This removes action number 3. You may also use: action delete <number> action remove <number> Turning Actions On and Off Use: action on action off action off disables all of your actions without deleting them. action on turns your action system back on. Enabling and Disabling One Action Use: action enable <number> action disable <number> Examples: action disable 2 action enable 2 This is useful when you want to keep an action saved but do not want it to fire right now. Priority Use: action priority <number> <priority> Example: action priority 2 10 Higher priority actions are checked before lower priority actions. If more than one action could match the same line, the higher priority action gets the first chance to fire. Testing Use: action test <text> Example: action test Thrain is in awful condition. This lets you test whether your saved actions would match a line of text, without waiting for that line to happen in combat. Important Rules ACTIONS do not give free attacks. ACTIONS do not bypass skill delay. ACTIONS do not bypass mana, move, position, combat, room, class, level, remort, or command restrictions. When an action fires, the saved command is placed into your normal command queue. Your character still performs it like any other command. If you are delayed, stunned, dead, sitting, missing resources, or otherwise unable to use the command, the normal game rules still apply. Safety Limits For safety, actions are simple. Actions may queue a few commands with |. Actions may not contain semicolons. Actions may not contain extra command lines. Actions may not directly create, delete, or modify other actions. Only a small number of actions may fire in a short time. Cooldowns can be used to make repeated lines safer. These limits help prevent loops and accidental command spam. Good Uses Good action uses include: action add You are hungry. = eat ration action add You are thirsty. = drink canteen action addgroup healing Thrain is in awful condition. = firstaid thrain action addgroup combat The guard blocks your path = bash guard action add No combo set. Usage: combo <skill1> [skill2] [skill3] = combo bash kick kick Keep actions simple and specific. The best actions respond to clear lines that do not appear constantly. Bad Uses Avoid vague patterns like: action add You = bash action add is = firstaid me action add the = battleorder all bash Very common words can make actions fire too often. Use a specific phrase from the game output whenever possible. Short Summary ACTIONS watch for text you see. When a saved pattern matches, your saved command is queued. You may queue more than one command with |. Use cooldowns to prevent repeated firing. Use groups to organize actions. Use edit commands to fix actions without deleting them. The command still obeys normal game rules. Use actions to list them. Use action add <pattern> = <command> to create one. Use unaction <number> to remove one. Watch the wasteland. React with discipline. Let the line fire.