/lem¶

Script-provided

Registered by lem. Start it with /lua run lem.

Syntax¶

/lem show | hide | list | status
/lem event <name> [on|off]
/lem cond  <name> [on|off]
/lem test  <text>
/lem reload

Description¶

Lua Event Manager — a port of MacroQuest's LEM. It watches your chat for text patterns and evaluates condition checks, running a bit of Lua whenever one fires. Events are managed in an ImGui window and through /lem, and both the event definitions and which are enabled persist per character.

Subcommands¶

Command	What
`show` / `hide`	Open or hide the LEM window. Hiding only hides the UI — events keep firing.
`list`	List every text and condition event with its on/off state.
`status`	Version, poll frequency, event counts, and whether safemode is active.
`event <name> [on\\|off]`	Toggle (or explicitly set) a text event.
`cond <name> [on\\|off]`	Toggle (or explicitly set) a condition event.
`test <text>`	Feed a fake line to the text events — test a pattern without waiting for it in game.
`reload`	Reload event definitions and their code from disk.

Bare /lem (or /lem help) prints the command list.

Two kinds of event¶

Text events match a pattern against incoming chat lines and run their action when it hits. /lem test <text> lets you fire one on demand.
Condition events run a Lua predicate on a timer (the poll frequency shown by /lem status) and act when it becomes true.

Definitions live under config/lem/, and the enabled/disabled state is stored per character. Edit a definition on disk and pick it up with /lem reload.

Relationship to Triggers¶

LEM overlaps jidou's built-in triggers module — both react to chat lines (triggers also watches HP and detriments). LEM is the familiar MacroQuest workflow (named events, an editor window, import/export); pick whichever fits how you already work.

Differences from MacroQuest's LEM

There is no macro layer, so the ${LEM} TLO is dropped — use /lem list and /lem status instead. Event enable/disable is local; peer relay is a later hook.