Trigger Types

Expression triggers evaluate the expression stored in the Pattern field whenever a is changed and execute the commands if the pattern expression is true.

Alarm triggers use the pattern field to specify a time when to execute the trigger. See the #ALARM command for more information on time pattern values.

Command Input triggers test the command entered on the command line and can change this command before it is sent to the MUD. See #ONINPUT command for more information about changing the text sent.

Skip Lines is used to skip lines then match the pattern specified. The Param field specifies how many lines to skip before matching the pattern. A blank pattern can be used to cause the trigger to fire immediately after last skip line is received.

Wait will delays matching for Param milliseconds after the trigger becomes active. A blank pattern can be used to cause the trigger to fire immediately after the time is up.

Loop Pattern matches the pattern Param times.

Loop Lines matches pattern whenever received for the next Param lines. If used with a multistate trigger it will advance to the next state after Param lines irregardless of number of matches.

Loop Exp uses an expression as pattern. This trigger tests the expression with each line received. If the expression is false it moves on to the next state, otherwise it fires. Param can be used to limit the maximum number of times the trigger will fire before moving on to the next state.

Duration type triggers check for a match of pattern with each line. Every line that matches before Param milliseconds have passed will cause the trigger to fire. Because the time on the trigger is checked after the pattern the first line received after expiration of the duration can still cause the trigger to fire.

Manual fires and advances to the next when the #SET command is used to mark the state triggered. If a pattern is specified the script for the trigger will be executed when a match occurs, but it will not advance to the next state.

Within Lines attempts to match the pattern for Param lines. If a match is made the script is executed and then the next state is activated. Once the maximum lines are received without a match the trigger is reset to state 0.

MXP triggers match on MXP tags of matching pattern. If the Newline option is set the trigger matches on the closing tag, and fills %0 with the text between the opening and closing tags. If the Prompt option is used the trigger will match the opening tag, a NONSECURE tag can then be modified by using the %mxp predefined variable.

Reparse allows you to test another trigger pattern on same line that caused the previous state to fire. Irregardless of match the triggerwill advance to the next state.

GSL triggers use a single character pattern to match codes sent by Simutronics games.

MCP matches MCP messages.