Demo-visible branches · player-observed detail · Verified September 19, 2026

Graveyard Keeper 2 Tech Tree

The Tech Tree is live in the demo and works as a dependency system: a visible recipe or objective may still require the right branch, inspiration, mastery, or station. Official material proves the interface and module relationship; player demonstrations add early branch observations that remain build-specific.

Demo · Sep 14, 2026 releaseWindows PC · SteamDemo verified
Official Graveyard Keeper 2 screenshot showing the graveyard keeper 2 building tech tree
The official Building Tech Tree screenshot establishes the branching interface.Official source ↗

DIRECT ANSWER

Spend early points against a current blocker: identify the missing recipe or action, open its likely branch, read the node and prerequisites, then confirm the workstation or quest dependency. Do not follow a universal “best tree” while costs and launch balance remain unverified.

Evidence state

Demo verified

Confirmed now

  • A multi-branch Tech Tree is visible in official media and the demo.
  • Graveyard modules unlock through Tech Tree progression.
  • Player-recorded demo footage shows Fishing I on the Farming branch.

Launch check

  • Complete branch and node graph.
  • Exact point costs, prerequisites, and 1.0 balance.
  • Quest, mastery, inspiration, and location gates outside the tree.
Officially named categoriesGraveyard module families
01Tombs
02Benches
03Columbaries
04Monuments
05Graves

Footprints, costs, and prerequisites await the release build.

FIELD DECISION / 01

Steps to follow

  1. Name the blocked actionWrite down the exact missing recipe, station, material, or interaction instead of buying a loosely related node.
  2. Trace every prerequisiteRead branch, node, inspiration/mastery, objective, and station requirements before spending.
  3. Verify the unlock in the worldAfter purchasing a node, inspect the relevant workstation or interaction; a tree unlock may still depend on construction or quest progress.
  4. Record the buildTreat demo costs and connections as demo data until rechecked in 1.0.

WHY THIS WORKS

Why this route is reliable

A dependency-first method prevents wasted points and distinguishes a missing material from a missing unlock. It also creates clean launch evidence for later node and recipe records.

IF IT DOES NOT WORK

Failure states and fixes

SymptomCheckNext move
A recipe stays hidden after collecting inputs.Inspect tree, mastery, inspiration, objective, and station.Resolve the missing dependency rather than hoarding more inputs.
A guide’s node name or cost differs.Compare platform, demo build, and publication date.Use the current in-game label and treat the report as version-specific.

LEDGER NOTE / 02

Demo-visible progression

Player demonstrations show Building and Farming examples, inspirations, perks, mastery dependencies, and early crafting unlocks. These observations are useful for navigation, but they do not prove the complete launch tree.

LEDGER NOTE / 03

Launch data structure

Private tech-node records already support exact name, branch, costs, prerequisites, unlocks, evidence source, build, and verification time. They create no public URL until full-build verification is complete.