Ignore Rules

Ignore rules can be accessed by pressing the Ignore Rules button in the Conflict Solver (it can be found next to the Ignore button).

Supported syntax is as follows:

# This is a comment it is indicated by placing the # in front of the text. This is not used by the ignore rules. It can be useful to remind you why you placed an ignore rule there in the first place.
# Comments cannot be used inline with a rule, so a single line is either a comment or a rule
# Entries will be parsed by checking if a path starts with the following string below
events
# You can also specify more refined paths by slashes
common\defines
# If you're a linux user you might be used to this, which is also fine and is valid
common/defines
# If you'd like to allow a subfolder you can use the following syntax to negate a subfolder
!common\defines\subfolder
# And Irony will include this subfolder regardless of the main rule telling Irony to ignore anything
# Mods can also be excluded by name
modName:Name of the mod you'd like to exclude
# As of 1.25 you mod filter behavior changed, excluded mods are excluded always provided they match the count setting. IE. Irony if it finds a conflict which has 2 definitions from 2 different mods will not show a specified conflict if the count setting was set to 3. The new syntax:
modname:Name of the mod you'd like to exclude--count:3
# However there is also a more user friendly Mod Filter which you can use and just toggle on\off mods.
# With 1.6 Irony also supports wildcards as well, for example
localisation\*l_german.yml
# Will tell Irony to ignore all German localisation files.

You can find more information on the Mod Filter/excluding mods by name here

Once you are done hit save and the conflict resolver will be refreshed and will ignore the matching rules.

You can share you ignore rule configurations here