beta120.00

New: Rebase cheats after a game update

When a Unity (IL2CPP) game updates, pointer addresses and ASM hook locations can move even though the cheat still targets the same field or method. Rebase rebuilds cheats from their meaning — class names, field names, and method names

How to use it

Before updating the game

1. Load your cheats and start the game.
2. Open Extended Cheat → Rebase with Down+ZR.
3. Press ZL+X (Build record).
4. Wait for Breeze to create <build id>.rebase in the game's Breeze folder. The first run may take time while it searches classes and builds the IL2CPP function map.

After updating the game

1. Start the updated game.
2. Open Extended Cheat → Rebase again.
3. Press X to create <build id>_rebased.txt from the newest record belonging to the previous build.
4. Press Y to add the rebased cheats to the cheat list. They are added disabled so you can check them first. You can also load the file using any cheats from Breeze's Game directory.

Each cheat is marked OK or FAIL, with the reason shown. rebase.log contains the details for every line.

What it protects

• Pointer chains are rebuilt using class and field names, even when the starting slot and offsets moved
• Hooks are found using both the AOB and the method name; if they disagree, Breeze refuses the cheat instead of guessing
• Code caves are placed again using the normal cave rules, and branches are updated for the new locations
• If a field is temporarily unavailable, names from an earlier record can be kept and marked KEPT

Important limits

• Unity (IL2CPP) games only for now
• Cheats with unresolved parts are refused rather than copied with possibly wrong addresses
• Cave code using ADR, ADRP, or literal loads is not moved
• Cheats with multiple caves or unsupported opcodes such as C0 conditionals are not currently supported