Triggers in Icesus

Web client triggers

The web client at play.icesus.org has triggers built in: when a piece of text appears in the game, it sends a command for you. Your triggers are saved on your character, so they follow you to any browser. In other clients (Mudlet, Mushclient, TinTin++ and so on) use the client's own triggers.

Click Triggers in the hotkey bar to open the editor and write one trigger per line, pattern first:

You decide to try a combat maneuver => battle -m kick

Lines starting with # are comments. You can also type these on the command line:

#trigger opens the editor
#trigger <pattern> => <command> adds one trigger
#trigger list shows your triggers
#trigger remove <n> removes trigger number n
#trigger clear removes them all (it asks first)
#trigger off and #trigger on pause and resume them

Several commands in one trigger

Set a command delimiter first with set delim ;;. Then a trigger whose command is wear all;;keep all sends both. Without a delimiter the whole line goes out as one command and fails. A single ; works too, but it also splits any say or tell that has one in it.

One trigger per line of text

A line of game text fires only the first trigger in your list that matches it. Two triggers with the same pattern don't both run, so put both commands in one trigger instead.

Limits

Up to 25 triggers per character.
Pattern 3-200 characters, command 1-200 characters.
A pattern matches plain text anywhere in the line, ignoring case. No wildcards or regular expressions.
Each trigger fires at most twice a second, and all triggers together at most four times a second.
After any trigger fires, none fires for 0.2 seconds, which stops runaway loops.

Every command a trigger sends follows the rules below.

Rules for all clients

Triggers are done with a client, TinyFugue or ZMud for example.

You are NOT allowed to have triggers that:

Control your character if a monster/item/whatever is found, or something happens, e.g.:
- You move until you find x, and then automatically stop.
- Moving through areas performing actions like "search x" automatically.
- Kill/target monsters based on input from the game itself (e.g. you move in a room, there is Idles there, you "kill/target idles" automatically. This also goes for assigning a target to your client and performing actions based on that, or moving to a room and automatically using spells/skills that get you in combat).
Automatically read what combat momentum or other similar proc you get, and assign that value to anything other than visual things. (Clicking a button your client puts on the screen is fine: a click is you, present at the keyboard, deciding to act. The rule is about the client reading the momentum text and firing the action without you. The web client's momentum buttons are click-shortcuts in this sense, not triggers.)
Loot.

You CAN have triggers for:

highlighting things like critical hits/spell success
repeat skills/spells while in combat when they go off/fail
repeat crafting skills/spells
party placement/reporting (as long as you are present)
object handling in YOUR inventory (bags/sacks)
capturing information to your client from the game, however it must only be used inside your client, e.g. changing data in your UI.

The following can be repeated even while not in combat: Preaching, flagellation and vicissitude.

Everything else is strictly forbidden.

(Please note that current crafting-trigger rules apply, and they are excluded from these clarifications UNTIL bulk crafting is added to the game. Just remember that you are still required to be present when using them!)

Tips:

Casters, look into cast <spell> next (help cast).
Non-casters, use battle -m <maneuver> in your combat loops to avoid accidentally using momentums automatically.

Note that your triggers may not run any commands while you are not controlling them. Also running any actions triggered by someone else saying or doing something is absolutely illegal.

To make this clear for everyone, using triggers to re-use fishing, hunting, etc. and combat momentums is strictly forbidden.

Crafting triggers: You are allowed to "do" crafting with triggers as it is very repetitious work, as mentioned above. However, you are NOT allowed to do so whilst being idle or not paying any attention to the game. This means that while you are allowed to craft via triggers/macros, you need to be there yourself, e.g. react to things happening in game, such as a wizard poking you to prove that you are around. You don't need to react at that very same second something happens; within 1-2 minutes is fine. This reaction grace period is only applicable in crafting!

These rules are here to prevent slow decline into robotting, but still allow some QoL things. If you don't like the game enough to actually play it yourself, why are you even here?

Updated in the Month of Growth, season of Living, year 523.