The keeper’s index · Verified Sep 4, 2026

Graveyard Keeper 2 Wiki Index

Use this index to move from a player question to the most useful guide. Exact live-build databases remain closed until their records can be verified, so there are no empty item, recipe, quest, or achievement pages to waste your time.

Priority SSource-backedPre-release baseline
Official Graveyard Keeper 2 website artwork showing purple evening sky key art
Official website key art anchors the pre-release knowledge map.Official source ↗

Evidence state

Confirmed by official sources

Confirmed now

  • 32 purposeful pre-release routes are open now.
  • Release, platform, Town, zombie, automation, combat, crafting, and visual-system pages are sourced from first-party material.
  • Five tools work without assuming launch-only numbers.

Launch check

  • Entity databases open only after their facts and screenshots pass the release-build gate.
  • Search aliases will expand as verified item, quest, location, and character names become available.
No orphan routesWiki knowledge graph
01Release hub
02System pillars
03Decision tools
04Source ledger
05Launch databases

Database pages stay closed until verified records pass the gate.

FIELD DECISION / 01

What to do with this information

  1. Start with the beginner guide if you want orientation.
  2. Open Confirmed Features if you need to audit a claim.
  3. Use the Town or zombie planner when you want a decision framework rather than a speculative optimal route.

LEDGER NOTE / 02

A wiki that knows what it does not know

Pre-release wikis often create pages for search terms long before useful data exists. This index takes the opposite approach. It links only to pages with a distinct job today, and labels the data that must wait for the shipping build. That makes the route graph smaller, faster to scan, and much easier to upgrade on launch day.

LEDGER NOTE / 03

Launch-day handoff

The same URLs will receive live-build facts first: recipes, Town requirements, zombie skill values, Tech Tree nodes, equipment, and quest triggers. Reserved entity schemas already exist behind a publication gate, but they do not create public shells or sitemap noise.