FIRST CHECK
Use the order counter as your dividing line. A counter that never rises points toward acceptance, item matching or the deposit interaction; a completed counter shifts attention to collection and the separate quest objective. The official PC 1.007 notes also name an iron-delivery fix, so record your build when reporting a persistent block.
Start with the symptom
No delivery prompt
- Inspect
- Active contract and carried item
- Next move
- Check the pile named in the player reports and capture the blocked interaction.
Deposit recorded but no reward
- Inspect
- Collection date
- Next move
- Check the next board collection cycle.
Jack still has no new dialogue
- Inspect
- Current town quest objective
- Next move
- Inspect progression separately from the completed shipment.
What you need
- Your installed version and platform.
- The current contract name, counter and quest text.
- The time of your last delivery attempt.
Inspect the failed checkpoint
- 01Order active?
- 02Output matches?
- 03Deposit registered?
- 04Collection / quest
1Confirm that the order is active
Open the board and find the accepted contract rather than relying on a quest title or a crate in inventory. Record its target and counter. If the contract is absent, resolve acceptance before changing a working production line.
2Compare the actual output
Read the label of the item you intend to hand in. Use the contract’s wording to distinguish a supply crate from raw materials or an intermediate kit. Suggested check: keep a single example beside the recipe menu instead of crafting another full batch.
3Check the deposit interaction
The basement crate stack is identified in player reports as the hand-in object. Record whether it shows an interaction and whether the board counter changes. Normal warehouse storage and a successful deposit are separate checkpoints.
4Separate collection from progression
If the counter is full, check the next collection cycle. If the shipment resolves but dialogue remains locked, write down the separate quest objective. Do not erase the successful shipment or make duplicate crates to troubleshoot a different town task.
Give the report a before-and-after state
A useful report lets another player recognize the same failure. Show the accepted contract, the carried supply label and the basement interaction in one short sequence, with the board counter visible before and after the attempt. Our recommendation is to stop repeating the deposit once that sequence reliably reproduces the symptom. Include the platform and installed build, then describe the exact checkpoint that failed: no interaction, unchanged counter or unavailable collection. If the shipment resolves while Jack remains blocked, preserve the successful result and report his current objective separately. Combining those states into one warehouse complaint makes the actual blocker harder to identify.
Workbench questions
Should I remake every crate?
First check the counter. Remaking a registered shipment adds work without testing the failed checkpoint.
Does the PC patch prove my console save is fixed?
No. Record the installed console version and compare its own patch information.
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 contextThe interface checks below are editorial diagnostics based on two player discussions and the official patch log. A patch fix does not prove that every platform or existing save has the same state.
Source-reviewed guide; player routes are identified below. Not an in-game test.