Skip to content
Calpheon Labs Binary Schemas
Esc
navigateopen⌘Jpreview
On this page

repairmaxendurance.dbss

Binary layout, byte coverage, field semantics, and validation evidence for the intrinsic BSD repairmaxendurance 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 3600; file hash 230515402; 108,380 extracted bytes; 1,458 rows; normalized SHA-256 b268205df3ac43568a8b66cc6361582574547edcc73609ac71a1a3586844eab9
Decoder packages/scraper/src/tables/repairmaxendurance.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
DBSS row count file +0, 4 decoder-only u32 frames all target rows Certain Certain Certain intrinsic count reaches EOF exactly Closed
rows[].itemId row +0, 4 positive u32 outer repair-target item key Certain Certain High equals repeated key and companion key exhaustively Closed
rows[].repeatedItemId row +4, 4 positive u32 repeated repair-target item key Certain Certain High exact equality in all rows; companion payload begins here Closed
rows[].unknown08 row +8, 10 zero-copy bytes unresolved header controls Certain Certain Unknown all bytes captured; historical OnlyNeedMoney/OnlyMoneyRepairCount suggest candidates but not current widths Closed as unknown
material count row +18, 4 decoder-only u32 frames material entries Certain Certain Certain every row width is 22 + count * 14 including outer key Closed
materials[].materialItemId entry +0, 4 positive u32 accepted repair-material item Certain Certain High Lua supplies _materialEnchantKey; archived Item1..10 and all shared keys agree Closed
materials[].recoveredMaxEndurance entry +4, 4 positive u32 maximum-durability points restored Certain Certain High 3,059/3,059 shared historical RepairCount entries agree; Memory Fragment (44195) is stored with 1 and independently documents max-durability recovery Closed
materials[].unknown08 entry +8, 6 zero-copy bytes unresolved material tail Certain Certain Unknown archived next column is NeedMoney, but neither it nor current bytes establish the current binary boundary; retained losslessly Closed as unknown
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; 1,458 rows; normalized SHA-256 b268205df3ac43568a8b66cc6361582574547edcc73609ac71a1a3586844eab9 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
RME-01 Rows are intrinsically variable-width. All payload lengths equal 18 + materialCount * 14; adding the outer key gives the production row width. Decoder uses the embedded count and does not depend on offsets. Resolved
RME-02 Material IDs and recovery counts are semantic, not neutral scalars. Client Lua calls ToClient_getRepairMaxEnduranceCount with repair/material keys; archived RepairMaxEndurance.ItemN/RepairCountN agrees for every shared entry; BDOCodex identifies Memory Fragment 44195 and its recovery behavior. Promoted the first two entry words to materialItemId and recoveredMaxEndurance. Resolved
RME-03 Historical money columns do not justify current field widths. Both captures store only zero values, and SQLite cannot establish binary representation. Header and entry tails remain visible Uint8Array fields, not speculative integers or reserved padding. Resolved neutrally

Was this page helpful?