The Blood of Dawnwalker’s divisive time mechanic was once much stricter, but it was loosened because of “fear” around the game. Game director Konrad Tomaszkiewicz confirmed that the devs pulled back on the original plan after hearing player concerns.
The game gives players 30 in-game days and nights to save their character’s family from a pack of vampires. But Tomaszkiewicz said the early version was far harsher. “We had at first a more restricted time where it was harder to beat the game,” he told Eurogamer. “But we started to speak with Mateusz [Tomaszkiewicz, creative director and Konrad’s brother] and the rest of the team about what we wanted to achieve, and we figured out that we don’t want to create a mini-game from it.”
The Tightening That Was Pulled Back
The original design forced players to think about every action with extreme care. “You needed to think about everything even more carefully,” Tomaszkiewicz said. He described the earlier version as a challenge that could have felt punishing, especially for players who wanted to see the game’s full content.
The current system is still strict, but it is generous compared to what was originally planned. Players gain 16 segments of time per day, and most quests cost only a few segments. That means there is plenty of room to complete tasks without rushing.
The prologue remains the tightest test of the time mechanic. It is the first small field where players see how scarce time can be, and Tomaszkiewicz said the team kept it unchanged to show what the full game would feel like. “The prologue was the first small test-field for time,” he said, “and we didn’t change it because we wanted to give this experience for people and show them what they can expect.”
Why Skills Cost Time
One of the strangest design decisions in The Blood of Dawnwalker is that upgrading skills costs time itself. Players accumulate skill points and spend them at shrines, and it is common for day to turn into night while they upgrade. The time gauge shows exactly how much each upgrade takes, and the cost rises as skills grow stronger.
Tomaszkiewicz explained that the design choice was born from observation. Without the time cost, he said, players skipped the game’s core content. “If we don’t have it, then what players are doing is skipping the whole content,” he said. “They are farming the boars, wolves, and other enemies to [level up and earn skill points]. They’re learning the perks and then they just go, on the first day, to kill Brencis.”
Brencis is the main antagonist and final boss of the game. By forcing players to spend time on upgrades, the devs ensured they took the time to explore the world properly before facing him.
Why There Are No Fixed Timetables
Another question players have raised is why the game does not include events that happen according to their own schedules. With a time system this precise, it would be easy to build quests that appear or disappear depending on when players arrive.
Tomaszkiewicz said the team considered it. “We spoke about it,” he said, “and we were afraid that it’s too risky to show the player that something happens somewhere and you are not taking part in it. You are not aware that it’s happening.” Instead, the devs chose a simpler approach. “We will approach it this way: that you are encountering some stuff, and if you decide that you don’t want to be part of it and you’re just going to do other things, then we have the choice of doing the quest or event or doing something else in the world.”
The risk, as Tomaszkiewicz framed it, was that players might miss something important without knowing it. Better to let them choose their path directly, even if it means fewer events overall.
The Patch on the Way
The time mechanic has been a major part of the conversation around The Blood of Dawnwalker since it launched. A popular mod to remove the time limit was released after the game came out.
Rebel Wolves is preparing a first big patch for early October, addressing combat, difficulty, performance, and more fluid traversal around the game’s world. The company continues to respond to feedback post-launch.
| Feature | Original Design | Current Design |
|---|---|---|
| Time limit | More restricted, harder to beat | 30 days and nights, generous pacing |
| Skill upgrades | Free or negligible cost | Cost measured in time segments |
| World events | Considered, then abandoned | Not described in the source |
| Stage | Detail | Status |
|---|---|---|
| Prologue | First test of time, unchanged | Complete |
| Main game | Rebalanced before release | Complete |
| October patch | Combat, difficulty, traversal improvements | In preparation |
Our View on the Trade-Off
The story is a small one, but it carries a larger lesson about game design. Developers often start with ambitious systems, then pull them back when they hear how players actually react. Tomaszkiewicz’s honesty about the fear behind the change is refreshing, even if it is a bit amusing.
The devs were careful about the world events because they feared players would miss them without knowing. That is a pragmatic choice, but it also speaks to how cautious developers can become when they see a community pushing back.
The Blood of Dawnwalker is a game about a vampire threat, and the devs made that management easier than they first imagined. The October patch will test whether the remaining issues hold the game back. Until then, players who found the time limit generous can rest easy — the devs responded to concern before release.
See the video the story is built around at Eurogamer.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.