Custom Patches - bcssov/IronyModManager GitHub Wiki

Custom Patches allow you to add your own manual fixes directly into the Irony Patch Mod.
They are intended for small, targeted corrections that you want Irony to respect during conflict analysis without creating a separate standalone mod.

This feature is ideal when you want to override or repair a definition quickly and locally.

See also:
→ Conflict Solver
→ Invalid Objects

1. What Custom Patches Are For

Custom Patches let you:

  • Inject your own code overrides into the Irony Patch Mod
  • Apply quick fixes without building a separate mod
  • Override definitions that Irony would not normally merge
  • Fix invalid definitions detected by CWTools
  • Adjust or correct problematic lines in a mod author’s file
  • Make temporary or experimental adjustments

They give you full control when you need a small fix now, without waiting for a mod update.

2. Recommended Use Cases

Use Custom Patches when:

  • A mod contains a broken or malformed definition
  • Irony marks something as Invalid but you know how to fix it
  • You want to override a small piece of data for your own playthrough
  • The change is too minor to justify creating a separate mod
  • You want Irony to treat your custom override as part of the analysis

For larger edits or long-term maintenance, it is recommended to create a dedicated external mod instead.

3. Custom Patches and Invalid Definitions

Custom Patches fully support overriding Invalid definitions.

Steps:

  1. Locate the invalid definition in the “mod folder” selector
  2. Write your corrected version in the Custom Patch editor
  3. Save the patch
  4. Rerun the Conflict Solver

Irony will then:

  • Prefer your custom override over the broken definition
  • Treat your patched version as the active definition during conflict analysis

4. How Custom Patches Integrate With Irony Patch Mod

When you save a Custom Patch:

  • Irony writes your override into the Irony Patch Mod
  • The custom file is treated like any other resolved definition
  • During analysis, Irony uses your version instead of the original
  • The patch persists until manually edited or removed

Custom patches do not get auto-resolved or auto-reset like normal conflicts — they exist only because you created them.

5. Important Notes

  • After creating or editing a Custom Patch, you must rerun the Conflict Solver
  • Custom Patches override the original mod’s data during analysis and merging
  • They are intended for small-scale adjustments, not full modding
  • If the underlying mod updates, your patch may need revisiting
  • Custom Patches are stored inside Irony’s patch mod, not as a separate mod

Summary

Custom Patches provide a lightweight way to fix or override definitions directly inside the Irony Patch Mod.
They are perfect for quick corrections, invalid definition fixes, and small personal tweaks — without needing to build a standalone mod.

Use them for precision fixes, and use external mods for large-scale changes.