Ignore Rules - bcssov/IronyModManager GitHub Wiki
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.
1. Overview
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
2. Opening Ignore Rules
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.
3. Syntax
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.
3.1 Comments
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.
3.2 Basic Path Prefix Matching
A rule matches conflicts if the file path starts with the text you provide:
events
This hides all conflicts under the events folder.
3.3 Subfolder Rules (Backslashes)
You can specify full or partial folder paths:
common\defines
3.4 Linux-Style Paths (Forward Slashes)
Forward slashes are also supported:
common/defines
Both styles are equivalent.
3.5 Negation (Allowing Subfolders)
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.
3.6 Excluding Mods by Name
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.
3.7 Count-Based Exclusion (Advanced)
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.”
3.8 Wildcards
Wildcards allow matching file name patterns:
localisation\*l_german.yml
This hides all German localisation files, regardless of subfolder depth.
4. How Irony Applies Ignore Rules
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).
- Wildcards allow simple pattern matching for filenames.
- Ignore Rules work alongside the Conflict Filter.
If multiple rules overlap, the most specific rule applies.
5. Saving & Refreshing
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.
6. Sharing Ignore Rules
You can share your Ignore Rules configurations or see examples from other users in the community discussion:
https://github.com/bcssov/IronyModManager/discussions/156
7. Best Practices
- 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.