Last updated: October 4, 2026
At Graveyard Keeper 2 Database (https://graveyardkeeper2.best), we pride ourselves on delivering verified, reproducible, and transparent data.
Because simulation RPGs frequently feature hidden mechanics, undocumented formulas, and internal balancing variables that are never stated explicitly in game tooltips, this methodology document details how our editorial and testing team extracts, parses, verifies, and publishes information across this wiki.
---
1. Primary Data Sources
Our database combines two rigorous approaches to ensure total accuracy: **static game file inspection** and **empirical in-game verification**.
### 1.1 Game File Parsing
- **Data Configuration Extraction**: Core entity definitions, base item values, stack sizes, study science costs, and technology tree nodes are extracted directly from official game configuration archives.
- **Unobtainable Item Identification**: By cross-referencing internal loot tables, drop rules, and merchant inventory files, our automated parser identifies items that exist in the code but lack any valid drop source or acquisition method (currently 118 items out of 609). These items are clearly flagged in their respective wiki entries to save players from futile searches.
### 1.2 In-Game Empirical Testing
- **Reproducible Test Environments**: Before publishing recipe durations, energy consumption rates, or autopsy penalties, testers run controlled trials in isolated game saves across multiple patch versions.
- **Save File State Auditing**: Internal variables such as town quality caps, church rating thresholds, and insanity decay curves are monitored directly through save game audits to verify theoretical calculations against real gameplay conditions.
---
2. Specific System Methodologies
### 2.1 Alchemy Rune Calculations & Color Summing The alchemy system utilizes a three-dimensional vector representation for all raw ingredients: **Red (R)**, **Green (G)**, and **Blue (B)**.
- **Formula Derivation**: Every reagent carries a fixed integer value across these three color channels.
- **Combination Math**: When two or three ingredients are placed into Laboratory I or Laboratory II, the engine computes:
$$\text{Result Rune} = (R_1 + R_2 + R_3, \; G_1 + G_2 + G_3, \; B_1 + B_2 + B_3)$$
- **Collision Checking**: Out of 6,960 possible ingredient combinations, our team mapped all 29 valid output states (such as Reanimation Liquid at `2 R, 1 G, 4 B` and Dream Dust at `0 R, 1 G, 1 B`). Any combination that does not match an exact registered formula results in ruined sludge.
### 2.2 Factory Automation & Zombie Throughput Benchmarking To provide actionable factory planning guides, zombie labor is benchmarked across standardized one-in-game-day cycles (equivalent to 12 real-world minutes):
- **Base Efficiency**: A standard zombie worker operates at a baseline speed coefficient ($k = 1.0$), scaling upwards with higher-quality zombie organs.
- **Belt Latency**: Conveyor belt travel time between input storage and workstation buffers is measured in tile-per-second increments.
- **Fuel Consumption**: Furnace smithies operating on Coal burn at a fixed rate of 1 Coal per 120 craft duration units, compared to traditional firewood furnaces burning 1 Fuel per 10 duration units.
### 2.3 Faith, Happiness & Sermon Mechanics The weekly church sermon system is one of the most critical progression gates in the game:
- **Conversion Ratio**: Parish happiness directly scales the base Faith payout.
- **Cathedral Multipliers**: Interior church decorations (candelabras, confessionals, stained glass) provide additive rating points, while graveyard quality establishes the multiplier threshold for congregant attendance.
- **Empirical Observation**: Sermons are conducted across consecutive in-game weeks to record exact silver tithes and Faith outputs under varying church score conditions.
---
3. Data Integrity & Verification Workflow
To eliminate outdated or misleading information, every article follows a strict lifecycle:
| Stage | Objective | Responsible Team | Verification Criteria |
|---|---|---|---|
| **Stage 1: Raw Extraction** | Parse files for newly patched items and recipes. | Engineering | JSON/YAML schema validation against internal dictionaries. |
| **Stage 2: In-Game Test** | Craft item, verify unlock conditions, test drop rates. | Gameplay QA | Visual screenshot verification and tooltip confirmation. |
| **Stage 3: Editorial Review** | Write clear guides, formatting recipes and strategy tips. | Content Editors | Peer-reviewed by at least two active community players. |
| **Stage 4: Live Monitoring** | Track official developer patch notes and hotfixes. | Wiki Maintainers | Immediate flag and update within 48 hours of game patches. |
---
4. How Players Can Contribute to Research
We encourage player scientists and theorycrafters to submit their observations: 1. When submitting crafting findings or quest branch triggers, provide the game build version. 2. If testing drop probabilities, compile a minimum sample size of 50 consecutive trials to minimize variance. 3. Submissions can be sent directly through our [Contact Page](/contact) or community discussions.
By maintaining transparent research standards, we ensure that the Graveyard Keeper 2 Database remains the most trusted, player-verified reference available.