Despite having done this many times before, both with Hunger and previously with Hell Let Loose, there’s always something uniquely nerve-racking about the first few hours of a large-scale test. In many ways, launching a test is an exercise in waiting to discover what goes wrong. It’s a challenging but absolutely necessary part of development, and I thought it might be interesting to explain what actually happens behind the scenes once we open the doors. Essentially, the entire development team assembles in Discord, with different people monitoring just about every channel imaginable. We’re looking for emerging patterns, reports of bugs, technical issues, crashes, and anything else that might suggest something isn’t working as intended. As issues emerge, our production team begins compiling and organising them. These are then fed through to QA, who start the process of reproducing them, establishing how consistently they occur, under what circumstances, and ultimately trying to isolate the underlying cause. Naturally, we have a fairly strict order of priorities. Server crashes sit right at the top, followed by client crashes, serious game-breaking issues, bugs that negatively affect other players, and then a descending list of less critical problems. Once we’ve isolated something, we then need to assess how difficult it is to fix, how much risk the fix introduces, and whether it actually makes sense to deploy that fix during the test itself. A seemingly straightforward fix can introduce an entirely new set of problems, so there’s a constant calculation taking place around whether something warrants a hotfix, when that hotfix should happen, and whether it requires taking the servers offline. All of this needs to be weighed against the disruption caused to people who are actively enjoying the game. Meanwhile, another part of the team is watching Twitch streams, YouTube videos, reading Discord conversations and generally observing how people are actually interacting with the game. As developers, we spend so much time playing our own game that we inevitably develop a very particular understanding of how everything works. Watching thousands of people encounter those same systems, often for the first time, is enormously revealing. We’re looking for the moments where players become excited, confused, frustrated, surprised, or start behaving in ways we hadn’t anticipated. Importantly, we’re not necessarily trying to eliminate every source of frustration. Hunger - like every game - is one that deliberately incorporates friction. There are moments where we want players to feel uncomfortable, under pressure, or frustrated by a difficult situation. That’s what makes overcoming those situations rewarding. The challenge is distinguishing between frustration that’s a valuable part of the experience and frustration that exists simply because something is poorly communicated, unnecessarily cumbersome, or not working particularly well. At the same time, we’re paying very close attention to the conversations taking place within the community, particularly between people who are actually participating in the test. Often, the most useful feedback isn’t a formal bug report or a direct suggestion to the developers, but simply two players discussing something they’ve just experienced. So while a Closed Beta might look like a relatively straightforward event from the outside, internally it’s an extraordinarily busy period of observation, diagnosis, prioritisation, decision-making, development and inevitably, quite a lot of waiting to see what breaks next. For those of you joining us this week, thank you for taking part. Whether you’re reporting bugs, discussing the game, streaming it, or simply playing, you’re providing us with an enormous amount of information that will help shape what Hunger becomes.