Instance Conditions

Instance conditions are YAML predicates. Put them in an instance rule's conditions array; every condition entry must pass. A table-valued condition is normally an OR-list when written as a YAML sequence, while map-shaped values are passed to the condition as one structured value. The exception is global_value, whose entries are ANDed. Conditions are normalized before evaluation; do not rely on YAML order.

These references document the instance-module format. Static replacement modules use replace_meshes and cannot be combined with instances.

Choose a reference

Need	Reference
Cells, regions, coordinates, files, and identity	Location and identity
Meshes, names, inventory, tags, locks, and object properties	Object properties
Target actors, stats, factions, spells, and disposition	Actors and target state
Player state, quests, globals, time, equipment, and weather	Player and world state
Inverting conditions and exclusions	Logic conditions
Comparison bounds and one-sided ranges	Comparison ranges

Common rule shape

instances:
  - conditions:
      - object_type: Container
      - cell_match: tomb
    actions:
      - disable: true

Conditions do not roll chance. Add chance to an action block when the match should sometimes produce an effect. See action execution order and random action ranges.

Evaluation

SSS may reorder conditions internally for efficient evaluation. Do not rely on YAML condition order.

Unless an entry says otherwise, a false or type-incompatible condition simply prevents the rule from matching; conditions do not persist state. Invalid condition names and invalid OpenMW type names raise errors. YAML shape and value constraints are enforced by the schema; runtime behavior outside schema validation is not a supported authoring contract.

Comparison Ranges The min, max, and threshold semantics used by instance conditions. Location and Identity Conditions Match cells, coordinates, content files, object types, records, and generated objects. Object Property Conditions Match names, meshes, inventory, scripts, tags, enchantments, locks, keys, and traps. Actor and Target-State Conditions Match actor type, death, creature classification, stats, spells, factions, class, and disposition. Player and World-State Conditions Match quest progress, globals, player stats, time, equipment, factions, and weather. Logic Conditions Invert one condition while preserving SSS rule matching semantics.