Skip to content
Calpheon Labs Binary Schemas
Esc
↑↓navigate↵open⌘Jpreview
On this page

detail_dialogoffset.dbss

Binary layout, byte coverage, field semantics, and validation evidence for the intrinsic BSD detail_dialogoffset decoder.

Investigation status

Status Value
Coverage 100%
Iteration BSD migration
Review state BSD migration reconciled
Last reviewed 2026-08-03
Captures examined Steam capture ads_version 856; PAZ 5075; file hash 1291284868; 702,620 extracted bytes; 58,550 rows; normalized SHA-256 85fc584d50cd338972817ae10d4a69897e27ecd21af790ad78952bf4d5205629
Decoder packages/scraper/src/tables/detail_dialogoffset.dbss.ts
Remaining blockers None

See Decoder methodology for the confidence scale and evidence rules.

Field ledger

Field/path Offset and width Representation Claimed meaning Physical confidence Representation confidence Semantic confidence Evidence Status
magic file +0, 4 bytes Exact ASCII PABR; validated and retained PABR table signature Certain Certain Certain The shared BSS envelope validates and exposes the signature. Closed
Row count (omitted) file +4, 4 bytes count consumed by the enclosing BSD array row-count framing Certain Certain Certain The current value 58,537 gives the exact file equation 8 + 58,537 × 12 + 12 = 702,464; the prior build’s 58,535 rows use the same grammar. Closed
rows file +8, rowCount × 12 bytes Count-framed array retained in physical file order; count omitted Detailed-dialogue payload directory Certain Certain Certain All 58,550 current rows decode to the independently verified key/span inventory and land exactly on the footer. Closed
rows[].key pointer +0, 4 bytes Little-endian u32, retained Full-width packed detailed-dialogue lookup key Certain Certain Certain Keys are unique; every key equals both the outer companion prefix at offset - 4 and repeated payload key at offset, then equals the intrinsic decoded dialogKey. Closed
rows[].offset pointer +4, 4 bytes Little-endian u32, retained without rebasing Absolute start of the inner repeated-key payload Certain Certain Certain Every pointer starts four bytes after its owned outer prefix and directly on the repeated payload key. An offset + 1 audit mutation is rejected. Closed
rows[].byteLength pointer +8, 4 bytes Little-endian u32, retained Exact inner-payload length, excluding the four-byte outer key prefix Certain Certain Certain Each owned physical row is [offset - 4, offset + byteLength); these regions exactly partition the companion after its count. A byteLength + 1 audit mutation is rejected. Closed
footer bytes final 12 bytes consumed with rows.pad(12) and omitted neutral PABR footer framing Certain Certain Neutral The counted fixed-width rows land exactly 12 bytes before EOF. Closed neutral
detail_dialog.dbss count companion file +0, 4 bytes Independent raw-DBSS u32 row count Frames the data rows addressed by this directory Certain Certain Certain Its current value is also 58,537; the data decoder consumes the count and every intrinsically framed row without consulting the offset table. Closed
Outer-key prefix ownership companion offset - 4, 4 bytes per row Little-endian u32, owned by the physical row but excluded from pointer byteLength Lookup prefix for the addressed payload Certain Certain Certain For every pointer, the prefix equals key; sorted regions begin at offset - 4, and a targeted outer-key mutation is rejected by the row’s key-mirror check. Closed
Repeated payload key ownership companion offset +0, 4 bytes per payload Little-endian u32, included in pointer byteLength Intrinsic detailed-dialogue dialogKey Certain Certain Certain All 58,537 payloads begin with the pointer key; the data decoder independently requires equality with the outer prefix and returns this repeated value. Closed
Pointer-to-row span relationship companion [4, 28,878,745) in client 2923 Unique sorted [offset - 4, offset + byteLength) regions Exact ownership of every byte after the companion count Certain Certain Certain The 58,537 owned regions are contiguous, nonoverlapping, in bounds, and end at EOF; key, offset, and length mutations independently fail the aggregate audit. Closed
Pointer/data key identity pointer key; prefix at offset - 4; payload at offset; decoded dialogKey Four independently checked u32 views of one identity Directory key selects exactly one detailed-dialogue row Certain Certain Certain Every current and prior-build row agrees across all four views; keys are unique and no competing row can satisfy the relationship. Closed
Detail/base ordered-key identity complete pointer arrays and decoded data arrays Exact sequence comparison, not a runtime join Detail and base tables share the same character/dialog identity inventory Certain Certain Certain All 58,537 current pointer keys match base_dialogoffset.dbss in order, and all current decoded detail/base dialogKey values also match in order; the prior 58,535-row build agreed likewise. Closed
Reserved ranges schema-local fixed widths consumed with .pad() and omitted framing or semantically neutral capacity Certain Certain Neutral Adjacent fields, strict EOF, and exact snapshot parity establish each width Closed neutral

Active assumptions

Findings

ID Finding Evidence Schema/documentation impact Status
F-01 The intrinsic decoder reproduces the transformed reference output exactly. Full snapshot comparison; 58,550 rows; normalized SHA-256 85fc584d50cd338972817ae10d4a69897e27ecd21af790ad78952bf4d5205629 The BSD schema is the production source of truth. Closed
F-02 Row and section boundaries are intrinsic. Strict decoding reaches exact EOF on the installed capture. No companion offset table is loaded by this decoder. Closed
F-03 Reserved byte ranges are representation details. Their widths are fixed by adjacent fields and full-snapshot parity. .pad() keeps the schema readable and omits redundant output properties. Closed

Reconciled source findings

ID Finding Evidence Schema/documentation impact Status
F-01 The offset file is canonical PABR, not raw count-only DBSS. Client 2923 is exactly 702,464 bytes: four-byte magic, four-byte count, 58,537 twelve-byte pointers, and a twelve-byte footer. The prior 58,535-row capture has the same envelope. The destination validates and retains the PABR magic, consumes the row count through the BSD array, and skips the footer with .pad(12). Closed
F-02 Each pointer excludes exactly one owned four-byte outer key prefix. Across the 28,878,745-byte companion, every prefix at offset - 4 and repeated key at offset equals the pointer key; [offset - 4, offset + byteLength) regions exactly partition bytes 4 through EOF. offset is documented as the inner payload start and byteLength as the payload length, rather than being mislabeled as a complete-row span. Closed
F-03 Corruption coverage distinguishes envelope enforcement from aggregate relationship enforcement. Magic, count + 1, and nonzero mutations of each of the three PABR footer words fail schema decoding; separate unused-key, offset + 1, and byteLength + 1 pointer mutations fail the complete-capture partition/key audit. Companion outer-key corruption also fails intrinsic mirror validation. Header/footer checks and the row key mirror remain rejecting schema checks; pointer semantics remain explicitly verified by the aggregate test. Closed
F-04 Captured totals are observations, not format invariants. Pointer count grew from 58,535 to 58,537 while the 12-byte row, prefix ownership, and PABR grammar remained unchanged. Neither count, current file size, nor individual observed span length is frozen in the production decoder. Closed
F-05 Archived semantic sources have no physical offset-table representation. Archived Dialog_Table and targeted BDOCodex NPC/dialogue pages expose logical dialogue identities or content, but no PABR header, pointer offset, byte length, prefix ownership, or footer. Physical confidence comes exclusively from local binaries; neither external source is a decoder, fixture, mapping, cache, or runtime dependency. Closed
F-06 detail_dialog.dbss remains intrinsically framed. Its own row count, mirrored keys, nested byte/string lengths, section counts, and trailer union decode the complete 28,878,745-byte file independently; the companion audit reaches the same boundaries. Production data decoding does not require offset-directed slicing or a join to this directory. Closed

Was this page helpful?