Abstract
Problem: Should games use timed quests and in-game clocks to create urgency, and how does game time interact with features like fast travel and turn-based combat?
Approach: Tim Cain examines timed quests (including Fallout's water chip timer) and story timers, weighing their single benefit against numerous design problems, then explores how game time interacts with fast travel and combat systems.
Findings: Timed quests have exactly one pro — a sense of urgency — but this is undermined by conflicts with player agency, multiple quest solutions, exploration, and the fundamental disconnect between game time and real time. The interactions with fast travel and turn-based combat create additional unsolvable design problems.
Key insight: The sense of urgency from timed quests is largely illusory, and the design costs — broken player agency, obligation instead of fun, incompatibility with multiple solution design — far outweigh the single benefit.
The One Pro of Timed Quests
Tim identifies exactly one benefit of timed quests: adding a sense of urgency. If you don't complete the task in time, the quest fails — or in the case of main story quests, it's game over. Fallout's water chip timer is the classic example. Tim never used timed quests again after Fallout.
Some argue timed quests add "consequence," but Tim points out that all well-designed quests already have consequences. Urgency through time pressure is the only unique thing a timer provides.
Why Timed Quests Fail
They Conflict with Player Agency
When a timed quest arrives, the player may already be doing something else — another quest, exploring, crafting, collecting materials. The timer creates obligation, and obligation isn't fun. Tim had a design pillar: "fun trumps everything." Forcing the player to drop what they're doing violates this.
The Two-Timer Problem
If you use timed quests more than rarely, players will inevitably receive two simultaneously. If it's impossible to complete both, that's a "shelf moment" — the player puts the game down permanently. This means you can't use timed quests frequently, which undermines the very urgency you were trying to create.
They Break Multiple Quest Solutions
Tim is a strong advocate for giving players multiple ways to solve quests — stealth, combat, dialogue. Timed quests punish slower approaches. If dialogue is fastest (click and solve), the timer implicitly tells the player: "this is the way I expect you to play." If you make the timer generous enough for the slowest approach (stealth — sneaking, picking locks, climbing vents, waiting for patrol patterns), then the fast approach finishes in a fraction of the time, making the timer feel pointless. Either way, the timer undermines the design.
Generous Timers Defeat Their Own Purpose
If the timer is so long that failure is nearly impossible, you've eliminated the urgency — the only reason the timer exists. The sense of urgency becomes an illusion, and the player eventually notices.
Story Timers Are No Better
Some games use broader "story timers" rather than quest-specific ones — you must advance the story to a certain state by a certain time or fail. Tim argues these have all the same problems as quest timers: the same obligation, the same imbalance between playstyles, the same illusory urgency.
Game Time Is Not Real Time
A critical insight: game time is never real time in single-player games. The moment a player can pause, save, or quit, the alignment breaks. A player might stop for weeks before returning. All that urgency evaporates.
The EverQuest Anecdote
The only game Tim recalls where real time and game time truly aligned was an early MMO — likely EverQuest — where servers ran on 24-hour clocks matching real-world time zones. Because Tim could only play evenings, he saw only nighttime zones for weeks. When he finally played on a Saturday afternoon, he was shocked to discover the zones had daytime. The world kept going without him, though his character was unaffected.
Game Time vs. Fast Travel
Fast travel creates a dilemma: does the game timer advance during travel?
- If no: A disconnect forms between game time and real time, undermining any sense of urgency.
- If yes: What happens if a quest timer expires mid-travel? Does the player arrive at the destination to find they've failed? Worse — what if a player fast-travels to the wrong location and realizes there's no way to get back in time? They're still playing, the timer hasn't expired yet, but they know it's already too late. Tim calls this one of the most disheartening experiences in gaming.
Game Time vs. Turn-Based Combat
Turn-based combat raises similar problems: does time pass during combat?
- If no: How do time-based status effects work? Are they round-based in combat but time-based outside? That's inconsistent and weird.
- If yes: You must define exactly how long a turn represents. A player might enter a random encounter thinking they have plenty of time on a quest, only to have combat eat 10 turns (10 minutes), expiring the quest.
The Arcanum Lesson
In Arcanum, Tim had both real-time and turn-based combat — which he does not recommend. Both modes had to feel like they took the same amount of game time for the same actions. If they don't match, the player's perception of time breaks down completely.
Tim's Conclusion
Tim no longer uses timed quests or story timers. The reasons:
- The sense of urgency is largely illusory and easily undermined
- Timers create obligation, not fun
- They conflict with multiple quest solution design
- Game time inevitably clashes with fast travel and combat systems
- There's no implementation that won't upset a significant portion of the player base
- The single benefit (urgency) isn't worth the cascading design problems
The fundamental issue: timed systems force design choices that may not be obvious to the player until those choices cause them to fail — and that failure feels unfair because it stems from systemic interactions, not player decisions.
Source: Game Time by Tim Cain
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=spZ9RbN9jT4