Beta Update

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

SeymourBETA

Update 2.45

6/9/2026

updateui

Full editor Music Player: all 89 catalog tracks are selectable in the UI. `AudioStudio_Service` now exposes immediate preview (`SetTrack`/`PreviewSelectedMusicTrack`) while preserving `SelectedTrackId` in preferences; the main window gained a `▶ Preview` button, wider ComboBox, and a Music Player card with current track, status, Music/FX toggles, and catalog count. Uses `Assets/Audio/Music/music_catalog.json` + `Catalog/.wav` (89 tracks). This is editor-only music playback; it does not claim in-game music swap, which still depends on the hook/IDA path. Editor builds 0 errors.

Read notes

SeymourBETA

Update 2.44

6/9/2026

updatemonster-ai

Custom Boss Creator: clone + edit any monster → new m###.bin (first step of the custom monster pipeline). New module `Modules/CustomBossCreator` + `FfxLib/Monster/MonsterCloner.cs`. Flow: pick a source monster (m000–m346 or any existing m###), set a new ID (347+ auto-suggested as the first free slot), edit stats (HP/MP/HpOverkill/Str/Def/Mag/MagDef/Agi/Lck/Eva/Acc) and ModelId individually (blank field = inherit from source), type a display name, click ⚔ Create Monster. `MonsterCloner.Clone()` does a Write→Read round-trip for an independent copy, applies a slot-only overlay (stats) or full rebuild (name) on the `Monster_StatSheet`, writes to `battle/mon/_m###/m###.bin` (creates the folder automatically), and registers the name in `Monster_Dictionary` at runtime — Formation Editor immediately sees the new monster by name. AI, loot, and in-game name are inherited from the source (refine later in Monster AI Editor / Monster Editor). Honesty: the clone creates the file; placing the monster in battles still requires Formation Editor (slot swap in an existing .btl). Offline gate: Monster_File writer proven (byte-identical round-trip).

Read notes

SeymourBETA

Update 2.43

6/9/2026

updatemagic-dll

EncounterTable: Save button + per-group Danger editing + global Danger presets (Features 1+4). The `EncounterTableExplorer` is now a full encounter editor, not a read-only viewer. `EncounterTableGroupRow` and `EncounterTableFormationRow` are now partial `ObservableObject`s: `Danger` (per group, 0–255) and `Weight` (per formation, 0–255) are editable via an interactive slider; changing `Danger` immediately writes back to `group.Danger` and updates the friendly label (`No encounters / Rare / Normal / High / Maximum`); changing `Weight` auto-recalculates `group.TotalWeight`. Per-group presets: `No encounters (0) / Normal (50) / Intense (128) / Maximum (255)` buttons. Save: `💾 Save btl.bin` calls `EncounterTable_File.Write()` (slot-only, byte-local patch), creates `btl.bin.bak` on first save; `↩ Restore vanilla` copies the backup back. Global Danger: four preset buttons in the "Edit & Save" card (`⚡ No encounters / Normal / Intense / Maximum`) apply to ALL groups across ALL maps at once, with feedback showing how many groups were affected. The `DataModel` holds `_loadedEncounterFile` and `_encounterFilePath` to reuse the parsed object without re-reading the file. Editor builds 0 errors.

Read notes

SeymourBETA

Update 2.42

6/7/2026

updateaurora

AURORA: battle-camera eye fully IDA-calibrated + gold-eye drag in the MapViewer. Closed `HANDOFF_CAMERA_POLAR_CALIBRATION_CODEX_2026-06-07`: IDA proves `camSetPolar(0x6004)` (`0x6004 -> 0x7B9260 -> 0x7BB550 -> 0x7C4760`, Camera slot `+12`) as `horizontalDeg, elevationDeg, distance`, with `x=refX+cos(h)cos(e)dist`, `y=refY+sin(e)dist`, `z=refZ+sin(h)cos(e)dist`. Aurora's gold camera eye is no longer approximate: `BuildCameraMarker` uses the real formula, and Place mode can now drag the gold eye; the editor inverses to `horizontal/elevation/distance` and writes the three floats via `WithFloat` (byte-local, backup-once), keeping the shared-float-pool warning. `BattleCameraScanLab`: `camSetPolar0x6004=10944`, target-aware variants kept separate `103854`, exact establishing polar `809/855`, eye-editable `802/855`, polar eye round-trip 802/802. `camSetBtlPolar`/`camSetChrPolar2` remain honestly outside the simple inverse. Editor builds 0 errors.

Read notes

SeymourBETA

Update 2.41

6/9/2026

updatemonster-ai

AURORA: DRAG the camera (ref/look-at) right in the MapViewer. Answering "how do I move the camera in the MapViewer?": in Place mode, the cyan sphere (ref = look-at) is now draggable like the monsters — drag it on the scene floor, drop, and 💾 Save positions writes the new `refSetPos(x,y,z)` to chunk0 (byte-local, EXACT, backup-once) — composes with a monster drag in the same save (different regions). The reader exposes the ref's float-pool indices (`Establishing.RefX/Y/Zindex`); `ApplyCameraRefDragToDisk` writes via `BattleCameraSetup_File.WithFloat`; `aurora-overlay.js` tags the cyan sphere as a drag target (`role=camera_ref`) reusing the `/drag` bridge. The gold eye (angle/distance) does NOT drag yet — pending the polar-convention calibration in IDA (next); edit it via the panel knobs for now. (Bonus: fixed the `BattleCameraScanLab` build that another lane had broken with new `AiNames` symbols — unblocks `offline_ci`.) Editor 0 errors, gate PASS (float 855/855).

Read notes

SeymourBETA

Update 2.40

6/9/2026

updatemonster-ai

AI Assembler: a stack corrector (Level 1+2) — warns when an edit empties the stack + says how to fix it. The owner asked for a "mini-AI corrector" that helps fix assembly errors. The validator already caught invalid opcode / dangling jump / index OOB, but not the #1 hand-edit error: stack imbalance. Now it does. RE-grounded (FFXDataParser): new `FfxLib/Ai/AiStackModel.cs` = per-opcode stack effect (from `OPCODE_STACKPOPS`) + arity of 269 functions (`ScriptFuncLib` input counts; accessor = subject?+index+value?). `AiValidator` simulates the stack depth (reset to 0 at entrypoint/jump-target) and reports underflow. Key honest twist: the parser's arities don't always match the real VM (proven: `setSelfFloating 0x7029` parser says 2, the corpus pushes 1) — so instead of the absolute count (which would false-positive on valid code), it diffs the ORIGINAL vs EDITED stack: the arity noise exists in both and cancels, leaving only what YOUR edit broke. The message (Level 2) says in plain language where it emptied + how to fix ("put back the PUSH that was an argument; every statement pushes the args THEN calls"). Auto-surfaces in the Validation panel. Gate `--ai2`: validator clean 346/346 (zero false positives on the corpus) + stack-break caught 1/1 (proves it catches a removed arg-push); `--ai3` PASS; RT0 byte-identical (analysis only, zero bytes). Editor builds 0 errors. Honest: it detects what the edit introduces; fine arity of some functions = public RE (corpus calibration = future).

Read notes

SeymourBETA

Update 2.39

6/7/2026

updatemonster-ai

AURORA: 3D camera MARKER in the MapViewer (see where the camera is / looks, in the scene render). The #2 of "how do I see it": the Aurora 3D render now draws the establishing camera — a gold sphere = eye (camera position), a cyan sphere = ref (the framed point, exact), an eye→ref line + a ground stem. Computed from chunk0: `refSetPos(x,y,z)` (exact, scene frame = proven IDENTITY) + `camSetPolar(angle,distance)` → `eye = ref + polar`. Reader `BattleCameraSetup_File.Establishing` (first refPos + first polar; gate: ref 855/855, polar 846/855), overlay model `AuroraCameraMarker`, render in `aurora-overlay.js` (same group as the anchors, inherits the Y-up flip). Honest: the ref is exact; the eye is APPROXIMATE — the polar convention (which arg is angle vs distance, elevation) is not byte-confirmed yet, so the marker is labeled "câmera (aprox)" and elevation is a visual guess; confirm/refine on screen (and via probe/in-game). Editor 0 errors. Doc `docs/reverse/FFX_BATTLE_CAMERA_SHOT_TABLE_IDA_2026-06-07.md`.

Read notes

SeymourBETA

Update 2.38

6/7/2026

updatemonster-ai

AURORA: EDIT the REAL battle camera parameters (angle · distance · position · roll) in the panel. Answering "and how do I see/edit this?": the 🎥 Camera card gained "🎚 Camera parameters (EDITABLE)". RE (IDA + FFXDataParser cross-check, on the owner's hint): the battle camera is SCRIPT-COMPUTED in chunk0 — Camera-namespace calls (`camSetPolar(angle,distance)`, `refSetPos(x,y,z)`, `camSetRoll`, `camSetScrDpt`) whose params are FLOAT constants in the pool. New reader `FfxLib/BattleMap/BattleCameraSetup_File.cs` extracts every call + resolves the floats + the distinct editable knobs; `WithFloat` edits the float pool byte-local (same length, reuses `AiScript_File.EditFloatConst`), preserving the other chunks. The panel lists the knobs grouped by type (polar/refPos/roll/screenDepth) with filter + search (the camera is a ~730-cut-per-battle cinematic script, so you navigate by group/search, not a raw list), each editable; "💾 Save camera parameters" applies the changed floats (backup-once + reload). Gate `BattleCameraScanLab` extended: 855 bins with camera, 623,981 calls, float-edit round-trip 855/855 (byte-local + reversible). Honest: editing a float changes ALL cuts that share it; a custom angle IS in-file (overturns the earlier "= scene authoring"); in-game effect = RT2. Doc `docs/reverse/FFX_BATTLE_CAMERA_SHOT_TABLE_IDA_2026-06-07.md` §6. Build 0 errors.

Read notes