... | ... | @@ -10,6 +10,10 @@ Method 2: Only one rule needs to apply to the item for it to be taken action on. |
|
|
|
|
|
Further these two methods can be combined so that first all [Rules](Manual/Rules) from method 1 need to apply and then any one [Rule](Manual/Rules) of method 2 needs to also apply for the item to be taken action on.
|
|
|
|
|
|
Be M1-0 to M1-n rules from Method 1, be M2-0 to M2-m rules from method 2 with n, m as integers.
|
|
|
So is the combined RuleSet evaluation executed as:
|
|
|
`(M1-0 and M1-1 and ... and M1-n) and (M2-0 or M2-1 or ... or M2-m)`
|
|
|
|
|
|
With this one or multiple general [Rules](Manual/Rules) can be defined in method 1, excluding items from the group of rules defined in method 2. For example excluding all locked items from deconstruction. Of cause this can also be done in a single rule (as it had to be done in RbI Version below 2.0.0), but I noticed that I often defined the same "header" for every rule and had to change it in all rules if I found it to be unsound or not far-reaching enough.
|
|
|
|
|
|
Deleting a RuleSet will also delete it from all [Profiles](Manual/Profiles) using it, but the underlying [Rules](Manual/Rules) may still be stored and executed in these [Profiles](Manual/Profiles) as unsaved RuleSet.
|
... | ... | |