Troubleshooting

Nothing happens

1. Check that Static Switching System.esp is enabled and SSS's data directory is active.
2. Check that the module is below scripts/staticSwitcher/data/ and ends in .yaml or .yml.
3. Check the OpenMW log for an SSS “Loaded module” line.
4. Confirm the object becomes active in the cell you are testing. SSS processes active objects in batches; it does not pre-patch every unloaded cell.
5. For instance modules, verify every condition. Conditions in one rule are ANDed; array values for most conditions are OR-lists.

The VFS and package boundaries page covers the most common installation mistake.

The module loads but a replacement is missing

For a static module, confirm both mesh values are VFS-visible. SSS logs a missing replacement mesh with the requested model, source model, object, and module name, then skips that swap. A source mesh path copied from another mod is not evidence that the replacement asset is installed.

For an instance replace, confirm the replacement record ID exists in enabled content. For teleport, confirm the destination cell name/ID or exterior coordinates resolve. For add, equip, and create, confirm the item or object record is available.

A condition never matches

• record_id uses Lua pattern matching; use ^ and $ when a substring match is too broad. Escape a literal pattern character where needed.
• cell_match is a case-insensitive substring match. cell is an exact name or ID comparison.
• replace_regions on a static module uses exact, case-insensitive region matching, while region is an instance condition.
• has_journal checks the player's quest stage when the object is processed. It is not a general event subscription.
• content_file_target requires both the content filename and the local reference number.
• cell_tag and has_tag require FlexTag; see FlexTag compatibility.

A random value errors or behaves unexpectedly

Condition ranges and action ranges are not interchangeable. Condition tables can provide min, max, or both. A table-form sampled action value requires max; this includes transform components, create position/rotation/scale values, lock levels, and teleport position/rotation components.

transform.scale is relative by default. A repeated rule can multiply an already changed scale. Use transform_type: absolute when the number should replace the reference scale.

A disabled object does not change again

This is expected for SSS's activation path. Disabled objects do not produce a later onObjectActive event for SSS to re-enable them. Use once: true for a one-time disable, and do not use a disable-and-reroll design when the object must toggle on later visits.

An update or removal made the save stranger

Instance actions are not generally reversible by changing a YAML file. Restore a backup save or author a carefully scoped follow-up rule. Existing static replacement chains are historical; see save updates and persistence.

Read the log first

When reporting a problem, include:

• OpenMW version and enabled content files;
• the exact VFS/data-directory layout for SSS and the module;
• the smallest YAML rule that reproduces the issue;
• the first SSS warning/error from the log;
• whether the save is new or already contains earlier SSS changes.

Do not diagnose a missing VFS resource from a filesystem search alone. If the issue remains unclear, reduce the rule to one condition and one action, test a fresh save or a backup copy, and reintroduce the other conditions one at a time.