WHAT CHANGED
Your old shipment plan may now overproduce. The official PC 1.008 announcement changes order demand, delivery likes and Happy Supplier, without publishing a new crate-count table. Compare the active contract with supplies already on hand; revise the remaining queue before deciding whether the factory needs any rebuilding.
What you need
- PC 1.008 installed, or the patch log for your own platform.
- A current order counter and reward preview.
- Any pre-patch notes you intend to reuse.
Update your working plan
- 01Installed build
- 02Live contract
- 03Revised batch
- 04Observed reward
OLD PLAN
Launch-week assumptions
- Old crate targets
- Old delivery reward notes
- Old Happy Supplier expectations
CURRENT CHECK
PC 1.008 contract display
- Read the reduced target in your active order
- Check the increased delivery likes
- Review the increased perk bonus
Confirm the installed build
Record the version shown by your game and compare it with the announcement. A dated guide is not a substitute for the installed version. Keep console and PC observations in separate notes if you play on more than one platform.
Read the contract again
Replace your old target with the quantity displayed by the current order. Keep the requested supply type alongside that number. Suggested ledger layout: old target, current target, stock on hand and remaining production; this makes an outdated batch size obvious.
Recalculate before rebuilding
Compare the current target with the stock already made. Our recommendation is to shorten the next queue first. A smaller order might fit your existing line, so there is no need to assume that every balance patch requires a different factory layout.
Review the reward in context
Keep the delivery reward, vendor trading reward and battle reward labels separate in your notes. Avoid transferring an old player spreadsheet’s ratios into your save without checking the same perks, prayer and contract. Finish one cycle and record the actual result.
Plan with released behavior, then watch for the next change
The announcement feed mixes completed fixes with future development plans. For production decisions, connect each released change to something you can read in your save: the contract target, reward display or machine state. Our recommendation is to keep a short comparison tied to the installed build, with old stock and the remaining queue beside the new target. Carousel output and sermon Faith also appear in the future-plans post; that wording does not make them part of this patch. When a later update ships, replace the relevant assumption in your plan instead of treating every announced improvement as already available.
Common blockers
| What you see | Check | Next action |
|---|---|---|
| Old guide asks for more crates | Publication date versus live contract | Use the live counter for the next queue. |
| Expected reward differs | Perks and contract labels | Record the actual reward before updating your estimate. |
| A promised feature is missing | Future plan versus released log | Check whether a later patch explicitly shipped it. |
Workbench questions
What are the new exact crate counts?
The reviewed announcement does not list replacement counts. Read your active contract.
Should I assume the same patch is on every console?
No. Use the patch information and installed build for that platform.
Keep the work moving
Official game references
- Graveyard Keeper 2 — official developer announcements ↗Official patch notes and developer updates
- Graveyard Keeper 2 — official game overview ↗Official game page
Version & evidence
Reviewed against PC 1.008 patch contextPatch facts here refer to the official PC 1.008 announcement. The order strategy is editorial advice. Future-plan items in the same feed are not treated as released features.
Source-reviewed guide; player routes are identified below. Not an in-game test.