SeymourBETA

Update 2.39

6/7/2026

v2.39.0BETA

Seymour

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

v2.38.1

v2.39.1BETA

Seymour

Executed docs/ai/MISSION_NAME_AUDIT_WITH_PARSERS_2026-06-07.md with the "coherence before naming" rule: ScriptFuncLib + ScriptConstants + corpus through AiScriptLab --names, without changing bytes. Added AiMotionPropertyNames, AiMovePropertyNames, and AiSaveDataVariableNames; disassembly glossing now resolves the field-space by function (btlActorProperty for 700F/7018/70AA/70AB, motionProperty for 70AC/70B2, moveProperty for 701A/7078), and saveData variables show parser-backed names when present. Corrected 0x701A to readMoveProperty and added the corpus-used call ids that still fell back to hex (7009, 7029, 7032, 7050, 7078, 70A8). --names gate: 160 used call ids, 0 unnamed; 285 fields in named spaces; 5 literals intentionally left hex (0x0156, 0x0157, 0xFFFB, 0xFFEF, 0xFFDF) because parser/corpus/IDA did not close them. --ai2/--ai3 PASS; editor 0 errors. Doc docs/reverse/FFX_AI_NAME_AUDIT_WITH_PARSERS_2026-06-07.md

v2.39.0

v2.39.2BETA

Seymour

Started the repo-wide plan to burn down campo 0xNN, stat 0xNN, comando 0xNN, raw, Unknown/Unk, and generic ids without a blind rename pass. New tool RuntimeTools/NameAuditLab inventories .cs/.axaml/.md/.ps1, separates EditorUi, CoreDisplay, CoreInternal, LabTool, Documentation, and Other, and marks only the small review now subset; current result: 2445 findings, 497 editor/display, 11 review now, with labs/docs/offsets intentionally keeping raw hex. Applied the first safe alias: Monster AI technical automation rows now show writeChrProperty StatusDurationHaste (0x0038) / setStatField stat_round (0x00DA) when AiChrPropertyNames closes the id; unknowns remain campo 0xNNNN. Docs: docs/ai/MISSION_PROJECT_WIDE_NAME_BURN_DOWN_2026-06-07.md, docs/reverse/FFX_PROJECT_NAME_BURN_DOWN_SCAN_2026-06-07.md; no AI byte changes

v2.39.1

SeymourBETA

6/7/2026

v2.39.0BETA

Seymour

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

v2.38.1

v2.39.1BETA

Seymour

Executed docs/ai/MISSION_NAME_AUDIT_WITH_PARSERS_2026-06-07.md with the "coherence before naming" rule: ScriptFuncLib + ScriptConstants + corpus through AiScriptLab --names, without changing bytes. Added AiMotionPropertyNames, AiMovePropertyNames, and AiSaveDataVariableNames; disassembly glossing now resolves the field-space by function (btlActorProperty for 700F/7018/70AA/70AB, motionProperty for 70AC/70B2, moveProperty for 701A/7078), and saveData variables show parser-backed names when present. Corrected 0x701A to readMoveProperty and added the corpus-used call ids that still fell back to hex (7009, 7029, 7032, 7050, 7078, 70A8). --names gate: 160 used call ids, 0 unnamed; 285 fields in named spaces; 5 literals intentionally left hex (0x0156, 0x0157, 0xFFFB, 0xFFEF, 0xFFDF) because parser/corpus/IDA did not close them. --ai2/--ai3 PASS; editor 0 errors. Doc docs/reverse/FFX_AI_NAME_AUDIT_WITH_PARSERS_2026-06-07.md

v2.39.0

v2.39.2BETA

Seymour

Started the repo-wide plan to burn down campo 0xNN, stat 0xNN, comando 0xNN, raw, Unknown/Unk, and generic ids without a blind rename pass. New tool RuntimeTools/NameAuditLab inventories .cs/.axaml/.md/.ps1, separates EditorUi, CoreDisplay, CoreInternal, LabTool, Documentation, and Other, and marks only the small review now subset; current result: 2445 findings, 497 editor/display, 11 review now, with labs/docs/offsets intentionally keeping raw hex. Applied the first safe alias: Monster AI technical automation rows now show writeChrProperty StatusDurationHaste (0x0038) / setStatField stat_round (0x00DA) when AiChrPropertyNames closes the id; unknowns remain campo 0xNNNN. Docs: docs/ai/MISSION_PROJECT_WIDE_NAME_BURN_DOWN_2026-06-07.md, docs/reverse/FFX_PROJECT_NAME_BURN_DOWN_SCAN_2026-06-07.md; no AI byte changes

v2.39.1