Official update / published 27 Sep 2026

Graveyard Keeper 2 Patch 1.006 Notes Explained

Patch 1.006 fixes several specific crash, stuck-state, zombie-work, inventory, trading, and progression defects. This summary keeps those fixes separate from similar-looking reports that the changelog does not address.

What patch 1.006 fixes

The developer says intermittent crashes on ultrawide and non-standard resolutions are fixed. That statement is narrow: it does not say every area-transition crash or every freeze shares the same cause. Players who still crash should include the exact resolution, transition, build number, and hardware in a new report.

Zombies, stations, and cooking

Zombies should now earn red tech points in fights, play work sounds when starting off-screen, and avoid blocking the millstone when placed at the cooking oven. Kitchen zombies should no longer consume or burn ingredients without producing a dish. The patch also targets two wedged-player cases: the kitchen chest/firewood gap and being pushed between workstations, chests, or extensions.

Inventory and trading

Extra bag slots should accept pickups and vendor purchases when the backpack is full. Static-price goods should no longer double in price on the first purchase. These notes identify observable results, so a useful recurrence report should name the item, vendor, inventory state, and displayed versus charged price.

Progression and crops

Defender's Emblems can no longer be destroyed in a way that soft-locks zombie squad unlocks. Crop beds should no longer become permanently stuck just before harvest. The changelog does not explain whether an already affected save is repaired, so Keeper Ledger does not promise recovery.

What the patch does not confirm

The reviewed notes do not confirm a fix for battle objectives blocked by a locked door, a flag behind inaccessible geometry, or a player spawning inside green fog. They also do not confirm a general manual-save option, universal crash recovery, or a specific bioreactor fix. Those symptoms remain community reports until the developer publishes a matching record.

How to check your result

  1. Confirm the visible build is 1.006 before reproducing.
  2. Write down the map area, workstation, objective, or vendor involved.
  3. For crashes, include resolution, display mode, and the exact transition.
  4. For progression, note whether the save was already affected before updating.
  5. On Steam PC, use the in-game bug report function added in 1.006.

Match your symptom