Updated Rules (markdown)

Michael Ingraham 2019-05-07 14:09:30 -04:00
parent c81863e2b6
commit bc426157b9
1 changed files with 2 additions and 2 deletions

@ -29,13 +29,13 @@ Every rule needs to follow this syntax:
**`endon`** marks the end of that rule. It can be followed by another rule.
Alternatively you can end the rule with `break`.<br>
**`break`** will stop the execution for all the triggers that follow this rule inside the rule set. If a trigger that ends with `break` occurs, the following triggers of that rule set will not be executed. This allows the rules to somewhat simulate an "IF THEN" statement.
**`break`** will stop the execution for all the triggers that follow this rule inside the rule set. If a trigger that ends with `break` occurs, the following triggers of that rule set will not be executed. This allows the rules to somewhat simulate an "IF THEN ELSE" statement.
Rule sets are defined by using the [`Rule<x>`](Commands#rule) command. After defining one you have to activate the rule set (turn it on) using `Rule<x> 1`. Similarly you can deactivate the rule set using `Rule<x> 0`.
> See [Commands](Commands#Rules) for a complete list of rules related commands.
There are 3 separate rule sets called `Rule1`, `Rule2` and `Rule3`. Each rule set can contain as many rules as can fit within the 511 character limit. Whenever a rule set is active all the rules in it will execute.
There are 3 separate rule sets called `Rule1`, `Rule2` and `Rule3`. Each rule set can contain as many rules as can fit within the 511 character limit. Whenever a rule set is enabled all the rules in it will be active.
Rules inside a rule set can be concatenated and have to be in one line: