Breeze becomes easier once you adapt to its differences. Try the latest Beta 99 prerelease—I’ve made the UI more user-friendly for newcomers. Let me know your thoughts!
https://github.com/tomvita/Breeze-Beta/releases/tag/beta99
Breeze Search Process and File Management
Breeze creates files that store
address-value pairs, which represent the search criteria. These files help track changes in game memory across different states. To simplify the process:
- The first file is automatically named File 1 if it doesn’t already exist.
- Subsequent files are named sequentially, such as File 1(00), File 1(01), File 1(02), etc., to maintain an organized structure.
Game States and Operations
- A, B, C: These represent different game states during the search process.
- Dump: Captures a full memory dump of the game at a specific state.
- Diff: Compares the addresses stored in a file with the current game memory from the previous search. It stores the addresses that have changed, along with their corresponding values.
Key Behavior of Diff:
- When performed on a dump result, the Diff operation stores data from the dump (not the current memory).
- To capture the current memory state, a second dump must be performed sequentially.
Breeze Search Steps
The Breeze search process involves the following steps:
- Dump to File 1: Capture a full memory dump of Game State A (data for every address in game memory).
- Play the game and make changes: Transition from Game State A to Game State B.
- Diff from File 1 to File 1(00): Identify addresses with values that changed between Game State A and Game State B. Store the values from Game State A in File 1(00).
- Diff from File 1(00) to File 1(01): Identify the same addresses but store the values from Game State B in File 1(01).
- Play the game and make further changes: Transition from Game State B to Game State C.
- Diff from File 1(01) to File 1(02): Identify addresses with values that changed between Game State B and Game State C. Store the values from Game State C in File 1(02).
In summary, the Breeze search process follows this sequence:
Dump → Play → Diff → Diff → Play → Diff
Comparison with EdiZon
- EdiZon uses a single file, and each operation overwrites the previous result. Its process is:
Dump → Play → Diff → Play → Diff
- Breeze requires one additional search step when starting with a dump:
Dump → Play → Diff → Diff → Play → Diff
This extra step in Breeze ensures that changes are tracked more comprehensively, with separate files for each state and diff operation.
Why This Matters
Breeze’s approach provides a more detailed and organized way to track memory changes across game states. By creating separate files for each step and storing values from both the dump and current memory, Breeze offers greater flexibility and accuracy in analyzing game memory.
