beta123.03

New: automatic game engine identification

Game Information now tells you what the game is built with and which Breeze tools are likely to work.

It can identify engines such as Unity, Unreal, GameMaker, Godot, RE Engine, KEX, and others, plus useful details such as:

• Unity version and IL2CPP or Mono
• Scripting languages such as Lua or Squirrel
• Middleware such as FMOD, PhysX, Wwise, or CRIWARE
• Renderer imports such as NVN or Vulkan
• Nintendo SDK version
• Loaded code modules
• Matching Breeze tools, such as Unity, Unreal, GameMaker, or native class tools

The report is saved as engine_scan.txt in the game's folder. Game Information opens faster after the first scan.

Faster first-time setup

When Breeze attaches to a game, it now performs two setup tasks automatically:

• Scans the game engine and saves the result for later
• Measures available ASM code-cave space, including space occupied by loaded cheats even when those cheats are disabled

The code-cave measurement is saved in cave_floor.txt. A fresh game start is still needed to measure space that was used by an old cheat but is no longer loaded.

Fixed: Unity tools in fresh sessions

• Small Unity classes with only one or two fields can now open correctly the first time
• Class field errors now explain which Unity class was found and why its view could not open
• Array and dictionary views now retain their pointer chain, so Make cheat can work after opening them from Memory Explorer
• Make cheat refusal reasons now appear in a message box instead of being overwritten immediately by the view

Fixed: cheat names containing brackets

Cheat names such as Dictionary item[0].key no longer stop the cheat file from loading. Existing names are supported, and new saves safely replace bracket characters when needed.