What causes a compendium not recording items the player has seen?

Items are only marked seen when picked up (or the seen set is never persisted), so items merely encountered or skipped never enter the codex.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix the Compendium Not Recording Newly Seen Items

Quick answer: Mark an item as seen the first time it is offered or revealed, add it to a persistent seen set, and save that set so the compendium survives across runs.

If the codex stays blank despite encountering items, you are recording too narrowly or not saving the set. Marking on first reveal and persisting the seen set fills the compendium.

How to fix it

1. Record on first reveal

Add an item to the seen set when it is first shown to the player (offered, dropped, or used by an enemy), not only when taken, so skipped items still register.

2. Persist the seen set

Store the seen-item set in the persistent profile and save it when it changes, so the compendium reflects everything encountered across all runs.

3. Load and render from the profile

Build the codex UI from the persisted seen set at boot so newly seen items appear after a restart, with locked entries for the unseen.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.