Graveyard Keeper 2 guide: data coverage and method
See the game build, complete catalogue coverage, review states and the limits of our 40-topic player-question sample.
Last updated: 2026-09-23
Which game version does this guide cover?
The catalogues use a local PC installation of Graveyard Keeper 2, Steam build 25467846, and its English and Simplified Chinese game text. We checked this edition on September 23, 2026. These are base game definitions; quests, upgrades and the state of your save can affect what is available.
The official Steam page identifies the game and its September 22 release. Information from the first Graveyard Keeper is not used as evidence for this sequel’s recipes.
What is included?
Catalogue | Entries | Scope |
|---|---|---|
| Items | 814 | All raw item definitions; quality variants can count separately. Reader-facing pages use readable game names and mark unverified names clearly. |
| Recipes | 827 | All raw recipe definitions, with special actions and internal entries labelled separately |
Workstations and extensions | 68 | Construction information for stations in the reviewed recipe subset, rather than every building |
Technologies and progression gates | 236 | Predecessors, listed costs and clearly identified unlocks |
Merchants | 21 | All merchant configurations, tier catalogues and buy/sell directions; reader-facing pages use readable game names and mark unverified names clearly. |
Search recipes · Browse technologies · Browse merchants
All raw definitions appear in the four catalogues, each with a separate detail page. Search, category and review-state filters work together. Lists show 24 entries per page with previous, next and numbered page controls.
“Structure reviewed” means the data structure and explicit relationships have been checked, not that every record has been tested in play. “Unverified” covers unclear names, conditions or relationships. “Special action” marks operations such as autopsy, fuel handling or repairs. “Internal / test” marks records with explicit internal flags. Reader-facing pages show readable game names and gameplay information supported by the indexed evidence. When a name or relationship has not been established, they use a concise pending-verification notice. Original IDs stay only in internal data and local evidence for matching records; they are not shown to readers. A definition does not guarantee availability in your save.
Batch calculations are available only for the previously reviewed 372 recipes. One-time crafts are limited to one batch; variable or unknown amounts are not treated as fixed numbers. Quality groups use explicit members only, and unresolved dynamic ingredient groups remain unverified.
A missing unlock link means the requirement has not been established here; it does not mean that no requirement exists. Variable output is not shown as a guaranteed quantity. Merchant stock figures describe base catalogues, not your current stock or a fixed replenishment promise. Full alchemy mixtures, quest walkthroughs and conditional outcomes are not yet covered.
How did player questions shape these pages?
On September 23, around 04:14 UTC, we selected the first 40 different, non-pinned topics in Steam General Discussions’ default recent-activity order. We read the original posts, without filtering for complaints. Of these, 21 described a concrete question or obstacle during play.
The other topics include buying decisions, language requests, general discussion and older expectations. Thirty-five original posts were created on the release date or later; five were older, including one explicit demo report. Recently active does not necessarily mean newly posted.
The table uses two denominators: all 40 topics and the 21 gameplay topics within them. A topic can have several labels, so the rows must not be added together. Example links show the kind of question behind each label; they do not establish a game mechanic or prove a bug.
Topic label | All 40 | Gameplay 21 | Example source |
|---|---|---|---|
Materials and recipes | 6 | 5 | Finding Polished Bronze |
Progression and unlocks | 4 | 3 | Gratitude cap question |
Automation and deliveries | 4 | 4 | Compost collection |
Building and workstation use | 5 | 4 | Kiln interaction |
Farming and fertilizer | 3 | 3 | Peat duration question |
Energy, time and saving | 4 | 3 | Energy and fatigue |
Tools and inventory | 1 | 1 | Handling old tools |
Performance or suspected faults | 9 | 8 | Town stuttering report |
Demo-save transfer | 3 | 2 | Save loading question |
Display and language support | 3 | 0 | Italian language request |
Purchasing, presentation and production information | 10 | 0 | Launch discount question |
Positive feedback or social discussion | 3 | 0 | Voice-over feedback |
Cremation and sermon mechanics | 3 | 2 | Crematorium report |
This led us to prioritize the crafting and early-roadblock answers and links between recipes, stations and unlocks. It does not mean every topic in the table has been solved.
What can this sample tell us?
It records questions visible in one Steam discussion window, not the percentage of all players who have each problem. Recent-activity sorting favors active debates and unresolved threads. The sample contains 36 English posts, two Russian posts, one Chinese post and one Spanish post; it cannot establish Chinese-language demand or console-wide experience.
We counted topics, not verified unique people. Replies, Steam reviews, private communities and players who never post are outside this sample. Older or edited posts may describe a different build. Posts were summarized and coded by one researcher; no author profiles were collected.
How are uncertain answers handled?
Game-data facts, official support information and player reports have different roles. We use player reports to find questions; we use verified game data to answer the parts it supports. We have not replayed every recipe, upgrade or quest, and an apparent fault still needs a confirmed cause before it can be presented as a fix.
For changing technical issues, use the publisher’s known-issues page. For official game information, see our sources.