Why HAWKER Uses a 30-Day Deadline Instead of Permadeath
Most roguelites end a run when you die. HAWKER ends the game when the clock hits thirty days. This is a design choice, not a quirk, and it's been the single largest pressure on everything else in the project. This piece from the team at Tyrian Games is a developer log on why we picked the thirty-day deadline over traditional permadeath, what the deadline does that permadeath can't, and what it costs us.
TL;DR
- Traditional roguelite permadeath resets on combat failure. HAWKER's thirty-day clock resets on temporal failure.
- Permadeath measures skill. A deadline measures priorities.
- Deadline structures force strategic decisions about what to skip, which permadeath never requires.
- The design cost is runs that can't be failed quickly. The upside is that every decision carries weight across the entire arc.
- Similar structures appear in Persona, Outer Wilds, Deathloop, Majora's Mask, and tabletop RPG campaign frames.
The two failure modes
A roguelite can fail its player in one of two ways. The first is combat failure. You die, the run ends, you lose most progress, you start over. This is the Hades, Dead Cells, Binding of Isaac pattern, and it's the one most players recognise when they think "roguelite."
The second is temporal failure. The clock runs out. The deadline hits. Whatever state you're in when the clock strikes is the state you keep, or lose. This is the Persona, Outer Wilds, Deathloop, Stardew Valley-with-Grandpa's-evaluation pattern.
Most roguelites pick the first. HAWKER picks the second, for specific reasons.
What permadeath measures
Permadeath is a skill gate. A Hades run that ends in combat failure ends because you played worse than the game demanded. You didn't dodge, you didn't parry, you didn't use your boons well. The next run is an opportunity to do better.
This is an excellent design for games that are about combat mastery. Hades is explicitly about mastering combat. Dead Cells is explicitly about mastering timing. The reset tells you: your skill level is the bottleneck. Improve, and you'll finish.
The problem for us was that HAWKER isn't only about combat. HAWKER is about the tension between scavenging, selling, surviving, and relating to the people around you, which is four things held in balance simultaneously. Combat is one of those four. Making combat the only way to fail would have made the shop, survival, and relationship layers feel decorative. We didn't want a game where the combat is the real game and the shop is scenery. We wanted a game where all four matter.
What a deadline measures
A deadline gate is a priority test. When the clock is ticking, every choice you make asks: is this the best use of the remaining time? Fighting a boss takes time. Upgrading your shop takes time. Talking to an NPC takes time. Running away from a biome takes time. Spending a day sleeping to save ichor takes time. And the clock doesn't care how skilfully you do any of these. The clock cares that you did them at all.
This means a skilled combat player can still lose a run of HAWKER by making good combat decisions at the cost of shop progression. A weaker combat player can still finish a run by sequencing the right non-combat days. The test isn't your reflexes. It's your planning.
Persona established this pattern in JRPGs in 2008 with Persona 3's calendar system. Outer Wilds used it in 2019 to create a space-exploration loop where the 22-minute timer forces hard priority decisions every loop. Deathloop used it in 2021 to turn a first-person shooter into a schedule-optimisation puzzle. Majora's Mask built the entire game around it in 2000, and the pattern has been quietly appearing in tabletop design for longer than any of its video game appearances. HAWKER is the shopkeeper-roguelite application of the same idea.
What deadlines cost
We need to be honest about the trade-offs. A deadline structure has costs that permadeath doesn't, and we ran into all of them during development.
Failed runs are slower to diagnose. In Hades, if you die, the lesson is usually obvious. You took too many hits in Tartarus, or you built a weak boon combination, or you missed the dash timing on Zagreus. In HAWKER, a failed run can be the result of anything from a bad combat day on day six to a missed shop upgrade on day eleven to a wrong biome priority on day nineteen. The thirty-day horizon means the diagnosis is harder. Some players will bounce off the game because they can't identify why a run went wrong, and we've spent a lot of 2025 in playtesting tuning the feedback that surfaces at day thirty to make retrospective diagnosis easier.
The first few runs are slow. A Hades run is 30 minutes if you die early and 90 if you reach the end. A HAWKER run is always close to thirty days, regardless of how well or badly it's going. This means the first failed run costs a player 90 to 150 minutes, not 20. The failure threshold is higher. We mitigate this by making individual days quick, roughly five to fifteen minutes each, and by making incremental progress feel meaningful even when the final payoff is far away. We can't fix the fundamental arithmetic. A thirty-day game has thirty-day runs.
Design has to keep the clock ticking even during combat. In Hades, combat stops the rest of the world. In HAWKER, the day advances whether you're in combat, in the shop, or asleep. We spent substantial design time on how the clock should advance during dungeon runs, and the current answer is that time advances in chunks tied to room completion and rest stops, with combat itself not consuming a full day. We still have open questions about how far we've threaded that needle, and we're watching playtest data carefully through the 2026 Early Access period.
UI has to carry a lot. Deadline games with weak UI feel stressful in the wrong way. When a player can't see where the clock is, how far they've come, and what's left that would be worth doing, the deadline starts to feel arbitrary. We spent more time on the day counter, the calendar overview, and the progress-toward-debt indicator than we did on several of the combat systems, because the deadline structure only works if the player always knows where they are in it.
What deadlines get us that permadeath can't
Four specific design affordances make the trade worth it.
Priority stories. A narrative roguelite with permadeath tells stories about hard combat moments. A narrative roguelite with a deadline tells stories about hard choices. "I chose to skip Ramzel this run to finish Duval's quest" is a different kind of memorable moment than "I nailed the Megaera fight perfectly." Both are good memories. We want the former to exist in this genre alongside the latter.
Mattering NPCs. Because the clock is ticking for the NPCs as well as for the player, NPCs can have their own deadlines. Sulon's storyline at the scrivener's office resolves one way if the Hawker reaches her by day seven and another way if he doesn't. These deadlines give NPCs agency in a way that permadeath roguelites struggle to achieve. In Hades, nobody in the House of Hades is on their own clock. In HAWKER, almost everyone is.
Endings that depend on path, not proficiency. HAWKER has multiple endings that depend on what the player did during the thirty days, not on whether they won or lost the final encounter. This is closer to Outer Wilds' ending structure than Hades'. It's the structure a game needs when the run is about the route you took to get there, not the boss waiting at the end.
Tone carried by structure. A deadline is a recognisable shape that communicates tone before any dialogue runs. Thirty days until the debt comes due isn't a neutral structure. It announces urgency, mortality, and the feeling that the game is not going to let you relax. That's the feeling Hawker is reaching for, and the structure does half the work of establishing it before the first cutscene.
Design references we looked at
While pre-producing HAWKER, we studied a handful of deadline systems closely. Persona 3, 4, and 5 are the canonical calendar JRPGs, with each day tied to a fixed budget of activities. Stardew Valley uses Grandpa's evaluation at the end of year three as a classic soft deadline. Outer Wilds treats a 22-minute loop as the world's clock. Deathloop turns four time periods into an optimisation puzzle. Majora's Mask organises the entire game around a three-day cycle ending with moonfall. Cult of the Lamb handles cult management with rolling soft deadlines. And tabletop "doomsday clocks" in Apocalypse World and Blades in the Dark games are mechanical, abstract, and very influential on how we built Ankou's debt milestones.
None of these games are shopkeeper roguelites. All of them shaped how we think about what a deadline is for and what it has to do.
A first-hand Hawker example
One of the clearest moments where the deadline structure paid off in playtest was during a Day 17 playthrough in late 2025. A tester had been chasing an optimal run: maximum ichor ducats, minimal wasted days, clean combat lines. On Day 16 she got hit by a blightstorm that chewed through her cart and forced a slow return. Day 17 opened with her down to fourteen days and the realisation that she couldn't hit her original debt target. We watched her re-plan in real time at the caravan table. She dropped two side quests, collapsed three biome runs into a single riskier sequence, and redirected a relationship thread away from a character whose side arc she no longer had time for.
At the end of the run, which she finished with a modest surplus and a distinctly different ending from the one she'd been aiming for on Day 1, she said the tester equivalent of "I've never had a roguelite make me feel like I was choosing rather than just playing." That's the moment we'd been chasing. Permadeath can't give you that, because permadeath resets the whole plan when combat fails. A deadline lets the plan break in the middle of the clock and demands you keep working with a shorter deck. That specific kind of pressure is the reason we committed to the deadline, and the reason we're not planning to walk it back.
FAQ
Is HAWKER a roguelite if there's no permadeath?
Yes. HAWKER has roguelite structure with temporary boons, inventory that resets on death, and permanent upgrades that survive, but it ties the run reset to the thirty-day clock rather than combat failure. Combat death in HAWKER advances the clock and strips you of the unsold loot you were carrying. It doesn't end the game.
What happens if I fail to pay the debt?
Ankou becomes actively hostile. The specifics sit past the spoiler wall.
How long is a HAWKER run?
A full thirty-day playthrough is roughly fifteen to twenty-five hours depending on how thoroughly you explore and how efficiently you manage the calendar.
Can you replay HAWKER after thirty days?
Yes. The game has multiple endings and substantial replay incentive. Some of the persistent character progression carries between runs.
Are there other shopkeeper roguelites with a deadline?
Recettear has a debt-installment schedule that functions like a soft deadline. HAWKER is the first to build the entire structure around a strict thirty-day clock.
Spoiler wall
Everything above this line keeps to the Day 7 demo boundary. The mechanics discussed (day counter, priority structure, Sulon's Day 7 resolution, Ramzel at the end of the demo, the train to Keridann) are all openly shown in our store page or trailers. The specific outcomes of late-game debt failure, the branching at Keridann, and the endings that depend on relationship state across days 20 to 30 sit behind this wall and aren't discussed in this piece.
Closing
The thirty-day deadline is the spine HAWKER is built around. It forces players into priorities, gives NPCs agency, and produces a different kind of memorable moment than permadeath does. It also costs us pace, accessibility, and diagnostic clarity on failed runs. We think the trade is worth it. In September 2026, players will get to decide whether they agree.
Next read: The light and shadow mechanic: a game design deep-dive, or What is a shopkeeper roguelite?.