How this site is built

Every number is generated from Core Keeper's own files. This page says exactly how, including what we could not establish.

The source

Core Keeper's dedicated server is a free download requiring no account (Steam AppID 1963720). Inside it, StreamingAssets/Conf/ holds plain JSON that the developer documents in its own README.txt: loot tables with real weights, spawn tables, all 12 talent trees, fishing behaviour and factions. That is a sanctioned modding surface, not datamining.

Item and creature statistics are not in that JSON. They sit on Unity DOTS prefabs named <Name>Entity. Their type information is stripped from the build, so we recover the field layout from the game's own .NET metadata and walk each component's bytes in order.

The checks every number passes

• Exact-length check. A component must consume its payload exactly. Any component that does not is discarded, not published — 2,419 of 2,419 object records now decode exactly.
• Monotonicity. Weapon damage must rise across a known tier ladder. It does: 33 → 50 → 132 → 163 → 214 → 248 → 280 for the sword line.
• Cross-provenance. Values are compared against an independent public source that shares no input with the game files. Boss health matched on 18 of 18 bosses; Copper Sword durability (250) and cooldown (0.4s) matched exactly.

Two things we corrected rather than shipped

An early read put health at the wrong offset and returned 0 for every entity. A uniform result is a broken measurement, not a discovery, so it was fixed before publication. Separately, a guess that a stored float was durability ÷ 350 predicted 0.2514 where the file says 0.2500; the guess was dropped and the field left unlabelled rather than dressed up.

What we could not establish

• Whether drills run in unloaded chunks is answered from strong evidence, not proof — see the automation page, which states the difference.
• In-game display names. Localized text ships only with the client, so names here are derived from the game's internal identifiers. Boss names come from matching our extracted health values against a public index — the join was exact, but it is a join, and we say so.
• Whether the guaranteed group consumes one of the draws. The developer's README says one item from the guaranteed group always drops, but not whether that pick uses up one of the table's unique draws. Our per-kill figures come from the draw model alone, so for guaranteed-group entries the true number is at least what we show. Everything else is exact.
• Ghorm's composing entities — the candidates are obvious but unconfirmed.

Version

Generated 2026-09-05 from Core Keeper 1.2.1.5, build 23543502, released 2026-06-08.