Conditions

Controls the order in which the plugin evaluates an objective’s conditions on each qualifying action. This is a performance setting: it does not change which actions count, only the order checks run in. Cheaper checks run first so the plugin can short-circuit and skip the expensive ones.

{
  "Conditions": {
    "Condition Ordering": "Optimized"
  }
}

Fields

Field	Type	Default	Description
Condition Ordering	enum: None | Optimized | RootOptimized	"Optimized"	How the plugin orders condition checks at load. Optimized sorts all conditions by cost so cheap checks run first, including inside And/Or groups. RootOptimized sorts only the top level and keeps nested order. None keeps the order from the data files.

Values

Value	What it does
None	Preserve the order conditions are written in. Use this if you ever need evaluation order to match the file exactly.
Optimized	Reorder by estimated cost, including conditions nested inside And/Or, so the cheapest checks run first. Best throughput, and the default.
RootOptimized	Reorder only the top-level conditions by cost, leaving conditions nested inside And/Or in their written order.

Caution

Unless you have a specific reason to change it, you really should leave this on Optimized. Some conditions are much more expensive to check than others. For example, TimeOfDay is very cheap: it just checks the in-game time. PlayerWear is expensive: it has to check the player’s entire wear slots. This may not seem like much, but imagine a Damage objective with a PlayerWear condition that runs on every hit of a minigun.