Add Multi-Line Triggers and Multi-Condition Triggers

[icewolfz]

Add a multi system like mudlet offers to match multiple lines some how

• [x] Core mulitstate trigger support
  • [x] Execute
  • [x] Temp states
  • [x] Types
  • [x] Regular
  • [x] CommandInputRegular
  • [x] Event
  • [x] Alarm
  • [x] Pattern
  • [x] CommandInputPattern
• [x] Sub state only types https://www.zuggsoft.com/library/trigadv.htm, http://forums.zuggsoft.com/modules/mx_kb/kb.php?page=3&mode=doc&k=2891
  • [x] Expression: the Pattern field is an Expression. When this Expression evaluates to True, then the trigger fires. The trigger is only tested when variables used in the expression change their values. This should be a main type as well
  • [x] Skip: ignore the next N lines from the MUD. Then fire when the pattern matches the MUD text.
  • [x] Wait: wait for a given interval, then fire when the pattern matches the MUD text.
  • [x] Loop Pattern: fire trigger the next N times the pattern matches the MUD text.
  • [x] Loop Lines: fire trigger when pattern matches text within the next N lines from the MUD.
  • [x] Loop Exp: fire trigger for each line from the MUD where the expression pattern is true.
  • [x] Duration: fire trigger for each line from MUD that matches pattern within the time interval.
  • [x] Within Lines: Fire trigger if pattern matches MUD line within N lines of previous state.
  • [x] Manual: Fire trigger when state is activated with the #SET script command.
  • [x] ReParse : The current line from the MUD is re-tested against a new Pattern. If the pattern matches, the script is executed and the state changes as normal. If the current line doesn't match the reparse pattern, the state moves on but no script is run.
• [x] Profile manager editing support
  • [x] Select state
  • [x] Add state
  • [x] Delete state
  • [x] Reorder state
• [x] #commands and %functions
  • [x] #COND/#CONDITION id {pattern} {commands} options profile- same as #trigger just instead of adding to profile it adds to matching id (pattern or name) or is added to the last trigger in current profile/profiled profile
  • [x] #SET pattern|name state value - set the state of the pattern/name if no id/pattern set the state of the last executed trigger, may only fire if manual trigger? not sure still researching
  • state the state to set
  • true or false if the state has been fired, when true the state will fire and then be skipped in the normal trigger state and reset for next usage
  • [x] %state(id, profile) - return current state of pattern/name
  • [x] #STATE id state profile - Set the state of the pattern/name, it state omitted set to 0, if id omitted sets the state of the last executed trigger
  • [x] #FIRE text - send text to trigger system with out displaying to screen, thus effecting the last line of text
  • [x] %alarm(pattern|id, setTime, profile) Set or returns the time in milliseconds left until an existing alarm trigger fires.

https://wiki.mudlet.org/w/Manual:Trigger_Engine#.22multiline_.2F_AND.22_and_.22OR.22_Condition_Triggers

[icewolfz]

Multistate-triggers branch is the work on multi state triggers

[icewolfz]

Due to the complexity of trigger alarms they will not support multi state triggering and will not be allowed as a sub type

[icewolfz]

Temp multistate triggers will not be removed until all states have been successfully triggerd, sub states can not be temp

[icewolfz]

Profile manger editing, do it like how context menus work and have the sub states as child nodes off main trigger and hide alarm type for sub triggers and show sub type only types when supported

[icewolfz]

Alarms now support sub states, by caching any trigger that as a sub state that is an alarm

[icewolfz]

went with a drop down navigation and buttons in profile manger editor as easier then trying to use tree view due to trigger vs tigger sub states being same type

[icewolfz]

Merged with, officially supported, will add remaining missing features as time allows

[icewolfz]

Expression system needs profile variables or converting the variable[name] to use function wrappers like profile variable to properly trigger when something changes, even so still not 100% reliable due to expressions could change a variable multiple times before completed but can only trigger after expression is over when the scope is set, while not perfect only way to do expression triggers, will wait until i merge profile variables to add expression type

Expression triggers should only fire if a variable in the expression changes, meaning have to parse valid possible varibales in expression and test against those if changed

//get all ids not in quotes, cache to improve performancelater on
//it first removes all quoted strings to ensure not false matches, then it looks for any valid matching words
_cachedIds = [...(EXPRESISONSTRING.replace(/"(.*)"/, "").matchAll(/\b([a-zA-Z_$][a-zA-Z_$0-9]*)\b/gm))].map(v => v[0]);
//to test if var is in exprssion or not
_cacheIds.indexOf('VAR') !== -1
//multiids
['var1', 'var2'].every(i => _cacheIds.indexOf(i) !== -1)

[icewolfz]

The parse variable branch has fully working expression types, once merged all trigger types will be supported