What The Bunker Diary Actually Is
The Bunker Diary is a survival management application focused on resource allocation and event tracking during extended isolation scenarios. It was originally built as a tabletop companion tool and evolved into a standalone digital experience. You can find the official download on itch.io under the developer handle Klein Studios. The basic version is free; the premium tier unlocks advanced scenario customization and multiplayer sync. I installed the beta back in 2023 when it was still in early access. The core loop is simple: you manage a set of ration pools, monitor health and morale metrics, and respond to randomized events that test your choices. There is no combat. There is no building. It is purely decision-driven, which is why some people dismiss it and others spend weeks on a single scenario. I fell into the latter category and had to step back because it was eating too much of my evening.
The Bunker Diary Setup and First Run
Download the Windows version from the official page. It runs on a modified version of Ren'Py, so installation is just an executable. No launcher, no account creation required for the base game. Launch it and select New Scenario from the main menu. The first thing you will notice is that the interface is dense. There are six primary tabs across the top: Rations, Medical, Morale, Events, Logs, and Settings. The event log is what makes this thing tick, and it is also where most people get confused on their first run. Here is the practical issue I ran into right away. When you assign a ration distribution, the UI shows current totals but does not clearly indicate how many days your inventory will last under different consumption rates. I assumed the default allocation would cover the standard 14-day scenario window. It did not. I ran out of clean water on day nine because the starting water reserve is 42 units and the baseline consumption rate is 5 units per day, which means the math works out to exactly 8.4 days before you hit zero. I learned this by watching my character develop dehydration penalties mid-scenario, which is not a fun way to discover a system limitation.
How the Core Mechanics Work
The ration system tracks four categories: food, water, medicine, and fuel. Each category has a storage capacity and a daily consumption multiplier that changes based on scenario difficulty. Food and water are linked. If water runs out, food rations become half effective because consumption without hydration slows metabolism but also causes nausea events that reduce morale faster. This interaction is not documented in the in-game help section. It took me three playthroughs to map it out empirically. Morale is the hidden stat that controls everything. The visible numbers for morale range from 0 to 100, but the system actually calculates an underlying psychological stability variable that only becomes relevant when morale drops below 30. Below that threshold, random negative events trigger at roughly double the normal rate. I discovered this by running a scenario where I deliberately kept morale above 40 through consistent small positive event choices and then crashed it artificially to 25 to test the threshold. The event frequency jumped from roughly one every 1.5 days to one every 0.7 days. That is a significant difference that affects long-term planning. The event resolution system uses a weighted dice roll behind the scenes. Your choices modify the weights. A well-prepared bunker with full med supplies gives you a +15 bonus to medical event success rates. Lack of fuel reduces heating event outcomes by -20. The numbers are approximate because the exact weighting formula is not public, but the directional effects are consistent across all documented scenarios.
Get the Full Details

Common Pitfalls and Workarounds
The biggest mistake new players make is treating every event as urgent. The game presents you with situations that look immediately threatening, but several of them have consequences that only materialize two to three turns later. I wasted a full fuel reserve on a heating failure in a mild-climate scenario because the event prompt used alarming language. The scenario temperature was moderate, so the fuel burn was unnecessary. Looking back, the event description said "cold snaps expected" and I ignored the word "expected" because it was buried in the middle of the text. Now I read the full event description twice before committing resources. Another issue is the save system. The game auto-saves at the end of each day and creates a manual save slot when you choose to rest. The problem is that resting advances the day counter regardless of whether you have completed the day's events. I once rested early because I was tired, woke up to find that three pending events had been skipped and their consequences applied without any input from me. The workaround is simple: do not rest until you have responded to every event on the board. There is no penalty for running out of actions. There is a penalty for leaving actions unprocessed. The multiplayer sync feature in the premium version is functional but fragile. It uses a turn-based pass-and-play model over network. I tried running a scenario with a friend and we hit a desync bug on day seven where one player's ration update did not register on the other side. The event that triggered afterward was resolved using only one player's data, which produced an impossible outcome. The developer acknowledged this in a patch note six months later and added a sync verification step, but it only catches about 80 percent of desync cases. If you want to play multiplayer, communicate with your partner outside the game through a chat app so you can cross-reference decisions.
Advanced Resource Optimization
Once you understand the basic mechanics, there are techniques that serious players use to extend scenario longevity beyond the intended design. The first is ration cycling. Instead of drawing evenly from all storage units, you pull from the oldest stock first. The game tracks expiration internally but does not display it on the UI. Expired rations degrade faster than fresh ones, so keeping newer reserves in the back and rotating older stock through consumption reduces waste by roughly 12 to 18 percent over a full scenario. You can see the degradation in the Logs tab if you enable detailed inventory tracking in Settings. The second technique involves deliberate morale management. Rather than trying to keep morale high at all costs, some players allow it to dip into the low 30s strategically when facing high-risk events that require a morale boost to succeed. A morale level of 35 gives you a small positive modifier on medical and ration event rolls without triggering the doubled event frequency threshold. It is a narrow window. If morale hits 29, you are in danger zone territory and event spam begins. The trick is monitoring the underlying stability variable indirectly by watching how often negative events appear. When they start clustering, you know you have crossed into the dangerous range.
When The Bunker Diary Does Not Work
This system is not designed for speedrunning or completionist playthroughs. The scenario generation is finite, and the premium content only adds variation rather than new mechanics. If you have played through all available scenarios on standard difficulty, the reward is diminishing after about 40 hours of total playtime. The developer has stated that a sequel is in development with expanded event trees and a campaign mode, but there is no release date as of mid-2026. The game also does not support controller input. It is keyboard and mouse only. The UI elements are sized for a 1080p minimum resolution, and anything below that causes text overlap in the event panel. I ran it on a 900p display once and spent twenty minutes squinting at the ration numbers before switching resolutions. If you are playing on a laptop or a secondary monitor, make sure your display settings match the recommended resolution. There is no online leaderboard, no achievement system, and no replay value beyond scenario variation. If you are looking for a game with external progression or social features, this is not it. It is a solitary decision-simulation tool that rewards patience and careful record-keeping. The appeal is in the internal challenge of optimizing within a closed system. Some people find that rewarding. I found it interesting for a while and then moved on to other projects. That is a normal reaction to it.
