-
Notifications
You must be signed in to change notification settings - Fork 52
Ignore Rules
Ignore Rules allow you to hide specific conflicts from the Conflict Solver based on path patterns, mod names, or filtering conditions.
They are useful when you want Irony to skip certain folders, definitions, or entire mods that you know are safe to ignore.
Ignore Rules are different from simply clicking Ignore on a single conflict.
- Ignore (button) hides one specific conflict until the underlying files change.
- Ignore Rules define persistent patterns that automatically hide all matching conflicts every time the Conflict Solver runs.
Use Ignore Rules when you consistently want Irony to exclude certain files or mods from the conflict list.
Read more about the Conflict Solver here:
→ Conflicted Objects
→ Conflict Filter
In the Conflict Solver window, the Ignore Rules button is located next to the Ignore button.
Clicking it opens a text editor where you can define rules using a simple syntax.
After saving, the Conflict Solver automatically refreshes with your updated rules applied.
Ignore Rules support several syntax types.
Each rule must be on its own line. A line is either a rule or a comment, but never both.
Start a line with # to write a comment:
### This is a comment explaining why a rule was added.
Comments are ignored by Irony but useful for documenting your rules.
A rule matches conflicts if the file path starts with the text you provide:
events
This hides all conflicts under the events folder.
You can specify full or partial folder paths:
common\defines
Forward slashes are also supported:
common/defines
Both styles are equivalent.
You can allow exceptions using the ! prefix:
!common\defines\subfolder
This tells Irony to include that subfolder, even if the main rule hides everything else under common\defines.
You can exclude all conflicts coming from a specific mod:
modname:Some Mod Name
This hides conflicts where the contributing definition originates from that mod.
As of Irony 1.25, you can combine mod exclusion rules with a count condition:
modname:Some Mod Name--count:3
This means:
- If the conflict involves fewer than 3 definitions, the mod is excluded.
- If the conflict involves 3 or more definitions, it is not excluded.
This interacts with the Conflict Filter’s “count settings.”
Irony 1.28 adds Exact Mod Set rules for conflicts that should be hidden only when the complete set of participating mods matches the rule.
For example:
modSet:"Mod A","Mod B"
This rule matches conflicts involving exactly Mod A + Mod B. Participant order does not matter, so Mod B + Mod A also matches.
It does not match:
- Mod A only
- Mod B only
- Mod A + Mod B + Mod C
- Mod A + Mod C
An Exact Mod Set rule uses set equality: every named mod must participate, and no additional mod may participate. It is not a count threshold, mod priority, winner/loser rule, or automatic conflict resolution.
Every mod name must be quoted. Inside a quoted name, use \" for a literal double quote and \\ for a literal backslash:
modSet:"Some \"Quoted\" Mod","Other Mod"
modSet:"Some \\ Strange Mod","Other Mod"
Commas, spaces, Unicode characters, %, and -- may appear inside quoted names. Exact Mod Set rules use canonical mod names; local aliases are for presentation only and do not change persisted rule identity.
Open Ignore Exact Mod Set in the Conflict Solver to view valid persisted rules as readable mod-name combinations.
- Add opens a list of active collection mods. Select every mod that belongs to the exact set, then choose Save. Cancel returns without making a change.
- Delete removes the selected Exact Mod Set rule without changing unrelated Ignore Rules.
- In Analysis/read-only mode, the manager shows Preview only. Existing rules remain visible, but Add and Delete are unavailable.
The raw Ignore Rules editor remains available for direct manual editing. Exact Mod Set rules work alongside path, modName, count, comment, Ignore Game Mods, and self-conflict settings. Malformed modSet: text is preserved in the editor but does not match conflicts.
Exact Mod Set rules are new in Irony 1.28. Irony v1.27.199 does not understand modSet: semantics and interprets these lines as ordinary path/wildcard rules. Normal round-trips preserve the text, so returning the preserved state to 1.28 restores its meaning, but deleting or replacing Conflict Solver state in an older version can permanently remove the rule. Do not rely on older releases to evaluate or manage Exact Mod Set rules.
Wildcards allow matching file name patterns:
localisation\*l_german.yml
This hides all German localisation files, regardless of subfolder depth.
Irony processes rules as follows:
- Paths are matched using starts-with logic.
- Rules apply before conflicts are displayed.
- Exceptions (
!path) override earlier path rules. - Mod exclusions always apply (subject to count rules).
- Exact Mod Set rules apply only when the complete participating mod set is equal to the configured set.
- Wildcards allow simple pattern matching for filenames.
- Ignore Rules work alongside the Conflict Filter.
If multiple rules overlap, the most specific rule applies.
Click Save in the Ignore Rules editor and Irony will immediately:
- Re-run the conflict evaluation
- Apply all matching rules
- Refresh the Conflict Solver interface
No restart is required.
To remove a rule, simply delete its line and save again. Exact Mod Set rules can also be added and deleted through the Ignore Exact Mod Set manager.
You can share your Ignore Rules configurations or see examples from other users in the community discussion:
https://github.com/bcssov/IronyModManager/discussions/156
- Use comments to document why a rule exists.
- Prefer folder-level ignores to long lists of specific files.
- Avoid ignoring definitions unless you're sure they are harmless.
- Use negation rules (
!) to fine-tune large folder ignores. - Use count-based rules for reducing noise in complex modlists.
Ignore Rules give you full control over how Irony filters conflicts, allowing a cleaner and more focused conflict-solving workflow.