Underkeep Bug Reports: Capture a Reproducible Problem

A useful report explains what happened, where it happened and how someone else might reproduce it. First compare the symptom with the current patch notes, then preserve the evidence rather than repeatedly overwriting the affected save.

Rule out a normal restriction

A movement lock after a combat action, an incompatible weapon, a missing tool and an empty food supply can all stop an intended action without a software fault. Check the relevant tooltip and current state before diagnosing a bug.

Patch 1.0.4 already names several specific issues. Update through the store client if your installed build lacks that fix; do not install an unofficial patch merely because a search result says it repairs the game.

Record the essentials

1. Game version, store client and operating system.
2. Area and recognizable nearby feature.
3. The exact item, skill, dialogue or puzzle involved.
4. The steps immediately before the problem.
5. What you expected and what actually happened.
6. Whether loading the preserved save reproduces it.
7. A screenshot of the error or relevant state, with private information removed.

For a quest issue, include whether the item was found before or after accepting the request. For an equipment issue, note whether the item was equipped when transferred.

Use the official route

The Underkeep Steam discussion hub includes a bug-report area. The developer’s official site is another public support reference. This independent guide does not submit reports or collect save files.

Preserve privacy and recoverability

Do not publish credentials or overwrite your only good save while experimenting. This guide does not recommend save-file editing, deleting game data or changing undocumented configuration values.