ERBM - Easy regulation bin Merger

Merge two modded regulation.bin files into one. Per-row conflict resolution. Author: G0110.

✨ What it does

• []Pick two modded regulation.bin files.[/]

  []ERBM computes BASE→File#1 and BASE→File#2 deltas against the embedded vanilla regulation, then applies both.[/]

  []Output: regulation_merged\regulation.bin.[/]

  []On row conflicts: pick a winner per row, keep both, or skip.[/]

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  🆕 Conflict handling (new in v2. 1)

  After both files are validated, ERBM scans for conflicts in three categories:

  • []Both modify existing — both mods patch overlapping bytes of the same row.[/]

    []Both add same id — both mods add a new row at the same id but with different bytes (the most common reason "two mods don't work together").[/]

    []Name conflict — 3-way row-name disagreement.[/]

    If no conflicts are detected, merge runs in one click. If conflicts exist, the inline status banner shows the count and a Review button. The Review modal lets you pick per row:

    • []Use priority — fall back to the global File #1/#2 setting (default).[/]

      []Use File #1 / Use File #2 — force a specific side for this row, regardless of the global priority.[/]

      []Keep both (relocate loser) — only valid for Both add same id. ERBM moves the priority-loser's row to the next free id within the same PARAM and rewrites cross-PARAM uint32 references inside the loser's delta to point at the new id. Both mods' custom rows survive in the merged output.[/]

      []Skip — drop both deltas for this row; keep the BASE row.[/]

      The Review modal supports filters (by PARAM type, conflict kind, row id/name) and bulk actions on the visible subset.

      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

      🔧 Keep both — heuristic scope

      The cross-PARAM uint32 ref rewrite is paramdef-free, so it has explicit limits:

      • []Rewritten: every 4-byte uint32 inside the loser's delta (added rows + patch segments) that matches the old row id.[/]

        []Not rewritten: refs in BASE rows the loser didn't touch. Mods that add a custom row usually also add/modify the rows that reference it, but it's not guaranteed.[/]

        Every relocation is logged in Logs\merge_report.txt (Relocations section) with old/new id, side, and every rewrite site. Open the relocated row in Smithbox if anything looks off.

        ━━━━━━━━━━━━━━━━━━