Beta Update

This is the archive of earlier beta notes. New notes are on the main updates page.

SeymourBETA

Update 2.37

6/7/2026

updatemonster-ai

Monster AI Editor: a PROVEN "If HP below X%" condition (IDA+corpus) + 222 named property fields (end of "campo 0xNN"). Halyson said to use IDA and guessed "it must be a config file where the line = a number" — both spot on. RE in `FFX_recon.i64`: the ATEL native dispatch = `handler = (FuncspaceTables[funcId>>12] + 16(funcId&0xFFF))` (slot +0 CALLPOPA / +12 CALL); `readChrProperty` (0x700F) = `0x7A4D70` → a `field→property` switch (`sub_7B2DD0`). Cross-referenced with FFXDataParser/ScriptConstants.putBattleActorProperty (the "config" the owner intuited) + the corpus: field 0x00 = HP (stat_hp, the corpus' most-read property — 306×), 0x02 = maxHP (137×), 0x119 = NearDeath (= IDA case 281 `current<max/2`). Arithmetic opcodes proven (` 0x16` etc.). #11 REAL shipped: a guarded snippet "If HP below X% → force command" = the `HP100 < maxHPX` idiom (corpus-proven fields 0/2) — the real boss-enrage, no longer a guess (the earlier v2.35.0 version was generic because the HP field wasn't proven; now it is). Naming: new `FfxLib/Ai/AiChrPropertyNames.cs` (222 named fields, same public provenance as the codec's func-name table) wired into the buff/stat detector → status actions now show "Haste/Protect/StatusPoison/HP/maxHP…" instead of "campo 0xNN". Gate `--ai2`: HP%-enrage 346/346 + conditional 346/346; `--ai3` PASS. Docs: `docs/reverse/FFX_AI_NATIVE_DISPATCH_AND_CHRPROPERTY_FIELDMAP_2026-06-07.md` (+ rename-queue for the `.i64`). Honest: structure proven offline, in-game effect = RT2; the 0xDA/218=HP%×256 gauge exists in IDA but the corpus doesn't use it (I used the path the AI actually uses, 0/2). Editor build red due to the Sphere Grid lane's WIP (unrelated); all my files are FfxLib, gate-validated.

Read notes

SeymourBETA

Update 2.36

6/9/2026

updateaurora

AURORA: CAMERA panel in the Aurora Chamber (edit the battle's `camReq` cuts: angle/shot + target). On top of the proven camera reader/gate (doc-only: chunk0 is an ATEL AiFile, RT0 863/863, `camReq` 100% byte-local editable), now the UI: a "🎥 Câmera" card lists the selected battle's `camReq` (`0x703F`) cuts with editable SHOT (angle, 1-based) and TARGET (framed actor, -1=none); 💾 Salvar câmera applies same-length byte-local operand patches (preserving the other chunk offsets), backup-once, and reloads. Reads/writes via `FfxLib/BattleMap/BattleCameraScript_File` (the AI codec). Files: `Modules/AuroraChamber/{AuroraChamber_DataModel.cs (CameraShots/PopulateCameraRows/SaveCameraShots), _Control.axaml (card + editable list), _Control.axaml.cs}` (code already in `c211a5f2`). Build 0 errors (editor running = `.exe` locked; separate-output build confirms). Honest: swaps between the angles/targets the script ALREADY references; a 100% custom angle (new position/FOV) = RE of the shot table `sub_797D60` (pending, IDA). In-game effect = RT2 (byte-safe + reversible, gate `BattleCameraScanLab`).

Read notes

SeymourBETA

Update 2.35

6/9/2026

updatemonster-ai

Monster AI Editor: behaviour Presets (#10) + a proven "below N" condition (#11) + documented #12/#13 frontiers. Closes what can be closed honestly from the "do it all" backlog. #10 — 🎭 1-click Presets (compose the ALREADY-proven automations, auto-pick the combat worker + validated grow): 🛡 Defensive (Protect+Haste on self), ⚔ Aggressive (force the picker's ability, always), 🔥 Enrage (picker's ability + Haste on self), 🎲 Alternate (picker's ability 1-in-2). #11 — "below N" condition: a new guarded Behavior-Library snippet `If chr property (self) BELOW N → force command` = the corpus' #1 condition idiom (`readChrProperty` 0x700F feeds 980 branches; `LT 0x0B` comparison proven in the census), with `field`+`threshold`+`command` user-supplied — honest: the exact HP field-id is NOT byte-proven (use the proven status fields 0x38/0x31/0x32; HP = an RE frontier), so it's generic, not an "HP%" button that guesses. #12 (turn N) and #13 (test live) = documented as frontier (there is no native turn getter — it's a per-monster priv-var counter, and the RNG 1-in-K proxy already ships; live only covers length-preserving edits, a grow needs a game reload) in the v2.33.0 doc. Logic: `AiSnippetLibrary` (snippet `guard-chrprop-lt-force-cmd`) + presets in the DataModel (`ApplyPreset`, composing `AddAbility`/`AddSelfBuff`). Gate `--ai2`: conditional snippet 346/346 (expands, grows the jump-table, re-parses, validates); `--ai3` PASS. Build 0 errors. Honest: structure proven offline; readChrProperty's arity + in-game effect = RT2.

Read notes

SeymourBETA

Update 2.34

6/7/2026

updatearena

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).

Read notes

SeymourBETA

Update 2.33

6/7/2026

updatemonster-ai

Monster AI Editor: Change target (#8) + Multi-cast / 2nd ability (#9), grounded in corpus mining. Two more from the list, done RE/corpus-first, no guessing. New `AiScriptLab` scanners (`--targets`, `--cond`) mined 1645 command sites and 10520 branches (doc `docs/reverse/FFX_AI_TARGET_ENCODING_AND_CONDITION_GETTERS_2026-06-07.md`). #8 — 🎯 Change target: the target is the push before the command id; 54% are computed (PUSHV findMatchingChr) and 46% literal sentinels (PUSHII) — only the literals are swappable by one operand (length-preserving = the RT2-proven edit). Honest: only self (-13/0xFFF3) is byte-proven; the other negative sentinels are target modes whose exact meaning is an RE frontier. So the editor offers "Self" + "copy a target from another action of THIS monster" (a sentinel that already works in-game for it), without asserting semantics. #9 — ⧉+ Multi-cast: inserts the picker's ability right after the selected action, cloning its target+mode (Seymour-style 2 actions in sequence; grows via Rebuild). Pure logic `AiAutomation.{ChangeTargetInstructions,InsertSecondCommand}` + `AiDetectedAction` gained `TargetPushOffset/TargetOperand/TargetIsLiteral`. Gate `--ai3`: change target 195/195 (757 literal targets), insert 2nd cmd 294/294; all others still PASS; `--ai2` PASS. Build 0 errors. Honest: structure proven offline; in-game effect = RT2 (multi-cast: confirm both resolve in one turn). Mapping each sentinel→mode + HP%/turn = frontier (see doc).

Read notes

SeymourBETA

Update 2.32

6/9/2026

updatemonster-ai

Monster AI Editor: list ALL actions (⚔ command · 🛡 buff/status · 📊 stat) with a type filter + rename a nameless command (#6 and #7). Two more from the owner's list. #6 — list everything, not just commands: the "Monster actions" list now detects and edits buffs/status (`writeChrProperty 0x7018`) and stats (`setStatField 0x70AB`) too, with a type-filter dropdown (All / ⚔ Commands / 🛡 Buffs / 📊 Stats). Each action shows an icon + friendly name (known status = "Haste/Protect/Reflect", else "campo 0xNN"; "(em si)" when the target is the self-ref; "= value" or "tirar" when 0). Move / Duplicate / Remove now work for ANY kind (generic stack-neutral removal of the `[pushes…][call]` run); Change / Force↔Queue stay command-only (guarded + a message). #7 — rename a nameless command: when a `performCommand` id has no dictionary label (e.g. `comando 0x60AB`), an ✏ Rename field gives it a friendly name that is persisted (`%LocalAppData%\FFXProjectEditor\ai-command-labels.json`) and used across the whole editor, for any monster. New pure logic: `FfxLib/Ai/AiAutomation.DetectActions` (command+buff+stat; `DetectCommandActions` is now a filtered view) + `FfxLib/Ai/AiCommandLabels.cs` (a store loaded on boot, saved on each edit; empty in the gate ⇒ no effect). Gate `--ai3` extended: detect buff/stat = 4020 buffs (3698 removable) + 4156 stats (4156), remove buff/stat 30/30 (generic removal shrinks by the exact run and re-parses), reorder 325/325 (now moves past a neighbour of any kind); add/rng/change/duplicate/toggle/self-buff/copy still PASS; `--ai2` PASS. Build 0 errors. Honest: structure proven offline; in-game effect = RT2. Only the 3 byte-proven status field-ids get a name (the rest = "campo 0xNN", honest).

Read notes

SeymourBETA

Update 2.31

6/9/2026

updatemonster-ai

Monster AI Editor: Copy AI from another monster · Restore original AI. Two more from the list: 📋 Copy AI — takes the entire AiFile from ANY other monster (dropdown of the 294 with a script) and pastes it into this one, keeping this monster's stats/loot (only the AiFile region changes, grow-aware splice + validation); a fast way to give a monster the behaviour of one that already does what you want. ♻️ Restore original AI — re-copies the vanilla AI from the monster in the extracted reference (`<ffx_ps2>\ffx\master\jppc\battle\mon\_mNNN\mNNN.bin`, e.g. `FFX Extracted`) — undoes any AI edit (even from old sessions, unlike the one-level `.prev.bak`). Both write a `.prev.bak` first. Reuses `SaveNewAi` (ValidateRebuilt + grow-splice + backup + reload). Gate `--ai3`: copy ai 346/346 (splice AiFile into the monster → slice back → re-parses, same instruction count); all others (add/rng/detect/remove/reorder/change/duplicate/toggle/buff) still PASS. Build 0 errors. Honest: structure proven offline; in-game effect = RT2. (Restore needs the reference ffx_ps2 root configured.)

Read notes

SeymourBETA

Update 2.30

6/7/2026

updatemonster-ai

Monster AI Editor: more 1-click action ops (Duplicate · Force↔Queue · Self-buff · Undo). Continuing the requested capability list: ⧉ Duplicate (cast 2x) — copies the selected action's triplet right after it (multi-cast by repetition; grows + re-parses); ⚡ Force↔Queue — flips the call between `forcePerformCommand` (force) and `performCommand` (queue), a length-preserving 1-operand edit; 🛡 Self-buff (Haste/Protect/Reflect via `writeChrProperty`, uses the same Always/Sometimes "when"; auto-picks the combat worker, guarded grow); ↶ Undo (backup) — every save now writes a `.prev.bak` before overwriting (one-level undo). New logic in `FfxLib/Ai/AiAutomation.cs` (`DuplicateActionInstructions`/`ToggleForceInstructions`/`AddSelfBuff` + buff presets); saves centralized in `WriteMonsterWithBackup`/`SaveNewAi`. Gate `--ai3` extended: duplicate 294/294, toggle 294/294, self-buff 346/346 (add/rng/detect/remove/reorder/change still PASS). Build 0 errors. Honest: all proven offline (structure/length); in-game effect = RT2. The buff field-ids (0x38/0x31/0x32) are the ones documented in the snippet — more statuses once more ids are mined.

Read notes