SeymourBETA

Update 2.34

6/7/2026

v2.34.0BETA

Seymour

Battle Tracker: it WORKS (reads the live battle) — auto initial read, honest status + an RT2 write lock

The Battle Tracker opened empty (two blank panels, "Load Ingame" inert). The cause was NOT the addresses — I proved against live RAM (FFX.exe PID 24716, battle azit03_01) that the whole chain is correct: ADDR_BATTLE_ACTIVE(rva 0xD2A8E0)=1, ENEMY_LIST/PLAYER_LIST(rva 0xD34460/0xD334CC) resolve, stride 0xF90, MemoryChr offsets (Id@0xE, Max_hp@0x594, Hp@0x5D0, In_battle@0xDC8) match, formation slots [0,4,6] == the 3 players with In_battle=1. The backend (Binarysharp.MSharp x64 reading the x86 FFX) also works — new MemorySharp + Read<byte>(rva, isRelative:true) returns the right value. The cause was UX: the DataModel never fired the first read (the ArenaTracker reads in its ctor; the Battle Tracker didn't), and the timer only read with Auto-Refresh on. Fix: (1) initial read in the constructor; (2) the timer keeps the honest status every tick and auto-populates the first snapshot when a battle starts (no need to toggle Auto-Refresh) and clears on battle exit; (3) ReadInfo wrapped in try/catch that surfaces the error + guards (null pointer / null bytes / out-of-range slot); (4) MemSharp_Service.IsAvailable() no longer throws on attach + IsAttached; (5) the UI gained a status banner ("FFX not found" / "attached, no battle" / "In battle: name · N enemies, M allies") and an RT2 write lock (checkbox, default OFF = read-only) gating the renamed "⚠ Write to game" button. New verification tool: RuntimeTools/BattleTrackerProbe (proves the live read path with the same DLL). Files: Modules/BattleTracker/{BattleTracker_DataModel.cs, BattleTracker_Control.axaml}, Services/MemSharp_Service.cs, RuntimeTools/BattleTrackerProbe/*, doc docs/reverse/FFX_BATTLE_TRACKER_LIVE_READ_PROVEN_2026-06-07.md. Module build OK (validated in a clean HEAD worktree; the full editor build is broken by another lane's AiTargetOption WIP, unrelated to this change). Honest: READ proven on screen/RAM; writes (Load Ingame → WriteProcessMemory) stay RT2 (game open + lock on)

v2.33.0

Back to updates

SeymourBETA

Update 2.34

6/7/2026

v2.34.0BETA

Seymour

Battle Tracker: it WORKS (reads the live battle) — auto initial read, honest status + an RT2 write lock

The Battle Tracker opened empty (two blank panels, "Load Ingame" inert). The cause was NOT the addresses — I proved against live RAM (FFX.exe PID 24716, battle azit03_01) that the whole chain is correct: ADDR_BATTLE_ACTIVE(rva 0xD2A8E0)=1, ENEMY_LIST/PLAYER_LIST(rva 0xD34460/0xD334CC) resolve, stride 0xF90, MemoryChr offsets (Id@0xE, Max_hp@0x594, Hp@0x5D0, In_battle@0xDC8) match, formation slots [0,4,6] == the 3 players with In_battle=1. The backend (Binarysharp.MSharp x64 reading the x86 FFX) also works — new MemorySharp + Read<byte>(rva, isRelative:true) returns the right value. The cause was UX: the DataModel never fired the first read (the ArenaTracker reads in its ctor; the Battle Tracker didn't), and the timer only read with Auto-Refresh on. Fix: (1) initial read in the constructor; (2) the timer keeps the honest status every tick and auto-populates the first snapshot when a battle starts (no need to toggle Auto-Refresh) and clears on battle exit; (3) ReadInfo wrapped in try/catch that surfaces the error + guards (null pointer / null bytes / out-of-range slot); (4) MemSharp_Service.IsAvailable() no longer throws on attach + IsAttached; (5) the UI gained a status banner ("FFX not found" / "attached, no battle" / "In battle: name · N enemies, M allies") and an RT2 write lock (checkbox, default OFF = read-only) gating the renamed "⚠ Write to game" button. New verification tool: RuntimeTools/BattleTrackerProbe (proves the live read path with the same DLL). Files: Modules/BattleTracker/{BattleTracker_DataModel.cs, BattleTracker_Control.axaml}, Services/MemSharp_Service.cs, RuntimeTools/BattleTrackerProbe/*, doc docs/reverse/FFX_BATTLE_TRACKER_LIVE_READ_PROVEN_2026-06-07.md. Module build OK (validated in a clean HEAD worktree; the full editor build is broken by another lane's AiTargetOption WIP, unrelated to this change). Honest: READ proven on screen/RAM; writes (Load Ingame → WriteProcessMemory) stay RT2 (game open + lock on)

v2.33.0