conco/OpenMaidEngine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Recover signed INIT data semantics

Browse Source
This commit is contained in:
gamer147
2026-07-22 21:05:48 -04:00
parent 5f743275bf
commit 7f2a81885a
8 changed files with 371 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/script-inventory.md
View File

@@ -61,9 +61,11 @@ and counts are indexed in `build/data/README.md`; field semantics are curated in
described by the workflow in `docs/name-resolution.md`.
The same audit found that linked row-major writes must not be normalized as independent parallel arrays.
Corpus `lookup-array-2d` bases and strides assign every such ITINIT write unambiguously to six tables (43
populated columns), while SKINIT and EBINIT expose 17 and 83 linked columns respectively. Generated records
now keep these under `record_fields[base/stride/column]`; `fields` contains only genuine parallel arrays.
Corpus `lookup-array-2d` bases and strides assign every such ITINIT write unambiguously to six tables (44
populated columns), while SKINIT and EBINIT expose 18 and 84 linked columns respectively. The extractor also
preserves the scripts' zero-minus-immediate negative writes, which carry item penalties, condition cures, and
skill SP costs. Generated records keep linked cells under `record_fields[base/stride/column]`; `fields`
contains only genuine parallel arrays.
### Message/string tables (`*MES`)
`ITMES` (64 KB — item text), `VIMES` (43 KB), `EIMES` (37 KB), `SKMES` (31 KB — skill