tinyBuild now lists stuck Town Warehouse iron deliveries, non-interactable crematorium and Study Table stations, missing console pre-order bonuses, and item loss when a partial stack enters a full chest. These remain known issues, not patch fixes. Save by resting in bed and relaunch if long-session performance declines; copy Player.log before restarting if you plan to report a PC bug.
About this guide
This guide distinguishes official information, player reports, and details that still need gameplay evidence. Source notes below identify what each reference supports.
How information is handled ↗Key details
- Scope
- Official support checked September 23; affected builds unknown
- Long-session advice
- Save in bed, then relaunch
- PC report
- Copy Player.log before restarting
- Open quest issue
- Town Warehouse iron deliveries can become stuck
Protect your items and saves
The current support page warns that moving items into a chest can delete the excess when only part of a stack fits. Check free space before transferring a stack, and keep a backup of important saves where your platform permits. An earlier support snapshot warned about Nintendo Switch demo transfer, but the current list no longer names it; that removal does not confirm a fix.
Town orders and workstations
tinyBuild now confirms that Town Warehouse iron deliveries may not be accepted or may leave quest progression locked after turn-in. The player-reported Jack order sequence can help check that the intended hand-in was attempted, but it does not resolve the confirmed stuck state. The publisher also lists a corpse stuck in a non-interactable crematorium and a Study Table that stops responding after an item is inserted for Science. Preserve the save and report repeatable steps rather than repeatedly spending materials.
Console bonus and garden well
For missing pre-order bonuses on consoles, tinyBuild says to install the DLC, re-import the demo save, and relaunch; a console patch is still in progress. It also warns that crafting the garden well upgrade again on consoles may crash the game. The September 22 Steam bonus hotfix should not be read as a console fix.
Rewards, tearing and older reports
tinyBuild still lists occasional missed rewards after giving soldiers beer or pie and screen tearing on consoles; it says it is working on a tearing fix. The September 19 support check also listed crafting-stack overconsumption, unspent zombie skill-point resets and endlessly spawning Nintendo tree or bush materials. Those entries no longer appear on the page checked September 22. Their absence does not prove a fix, and Kingy has not reproduced them in a released build.
Performance after a long play session
For declining performance during extended play, tinyBuild recommends saving frequently by resting in bed and closing/reopening the game every few hours. This advice does not establish a fix for every crash, screen-tearing issue or blocked quest. If reporting the problem on PC, preserve the current Player.log before relaunching.
PC and Steam Deck stutter
For PC performance trouble, tinyBuild recommends checking the minimum hardware requirements, lowering graphics quality or resolution, updating Windows and GPU drivers, temporarily disabling overlays, and verifying game files. Try one change at a time and note whether the problem happens immediately, after a long session, or in a particular area.
A Steam Deck player reports stutter even on low settings, especially in rain. One reply finds a 30 FPS cap with medium or low graphics playable, while another still reports noticeable stutter. Treat that cap as a player suggestion, not an official fix or performance promise. Steam marks the game Deck Verified, which does not establish a steady frame rate in every scene.
Send a useful bug report
Open the official “How to report a bug” source below. Include the platform, whether you are playing the demo, the version if visible, the steps that trigger the issue, and a screenshot or clip.
On PC, support requests the .dat and .info save files plus Player.log from %USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2. Copy Player.log before restarting because it resets when the game launches. Keep the original save files; use copies for the report.
What is not a verified fix
This wiki has not reproduced these issues or tested workarounds. The checked support list also names research points leaving bounds, an incorrect morgue corpse counter after exhumation and cremation, and Speech Volume not affecting mumbling; the 999 research counter cap is intentional. None is marked fixed in the September 22 hotfix. Avoid treating a community suggestion as a guaranteed fix, especially if it requires replacing or deleting a save.
Related questions
Sources for this guide
Guide reviewed September 23, 2026. Official notices, community reports, and demo footage have separate scopes; Kingy has not playtested this guide.
- Known issues · official Graveyard Keeper 2 support ↗
Official support list · checked September 23, 2026 · Source checked September 23, 2026
- Performance issues during extended play sessions ↗
Official troubleshooting · Source checked September 19, 2026
- General troubleshooting · Graveyard Keeper 2 Support ↗
Official platform troubleshooting · checked September 23, 2026 · Source checked September 23, 2026
- How to report a bug · official support form ↗
Official bug-report instructions · Source checked September 19, 2026
- Graveyard Keeper 2 · Steam store page ↗
Official store listing · Source checked September 23, 2026
- Steam Deck Performance · Steam discussion ↗
Release-build performance reports · checked September 23, 2026 · Source checked September 23, 2026
- Graveyard Keeper 2 · Steam bug reports ↗
Live player bug reports · checked September 23, 2026 · Source checked September 23, 2026