Real-Time Fallout

tim-cain fallout real-time game-design combat ux-design perks action-points

Abstract

Problem: What would need to change if Fallout were remade as a real-time game instead of turn-based?

Approach: Tim Cain walks through a systematic hypothetical redesign — examining weapons, skills, perks, UI, healing, looting, and multiplayer — explaining what breaks when you remove action points and turn-based pacing.

Findings: Nearly every system in Fallout is entangled with action points and deliberate decision-making. Converting to real-time requires gutting and rebuilding weapons modes, the perk tree, skill usage timing, inventory UI, and healing mechanics. Multiplayer still doesn't belong in Fallout regardless of combat system.

Key insight: Turn-based combat isn't just a mechanical choice — it's load-bearing for Fallout's entire design philosophy. Removing it doesn't simplify the game; it forces a cascade of redesigns across every system.

Source: https://www.youtube.com/watch?v=yVN2IlzORoE

1. Context and Disclaimer

Tim Cain states emphatically that he would not make Fallout real-time — not in 1997, not today. This is a pure thought experiment. He reminds viewers that Interplay's marketing team pushed him to go real-time in 1996 because of Diablo's success, and he killed the idea by presenting the true cost in time and money.

He also points out that Arcanum (2001), which he made right after Fallout and which features real-time combat, is essentially "the real-time Fallout game I would have made in the '90s."

2. Action Points Must Go

The first and most consequential change: action points are completely removed. This single decision cascades through everything — attributes, perks, weapons, weapon modes — because so many systems reference AP directly. Agility loses one of its primary functions. Everything that touches action points must be thrown out or rebuilt.

3. Weapons and Called Shots

Weapon modes (single shot, burst, throw) can survive, but need a new UI for quick switching — the old interface is too slow for real-time. Balance comes through rates of use: single shots fire frequently, burst shots have longer cooldowns (reloading), creating natural pacing.

For called shots (a signature Fallout feature), Tim sees three options:

  • Time-stop: selecting a called shot freezes the game, you pick a body part, time resumes
  • Slow-motion: time slows dramatically; perks could control how much it slows
  • Pure real-time aiming: where you aim on the enemy determines the called shot target — no guarantee of the special effect, but it keeps the flow

4. Skill Usage: Stop, Slow, or Real-Time

Each skill needs individual assessment:

  • Lockpicking should probably stop time, especially with a minigame
  • First Aid stays usable in combat (fast, field-ready — like a trauma medic)
  • Doctor gets disabled in combat or interrupted by damage (requires sitting down, using instruments)

This creates a natural split: combat skills vs. out-of-combat skills, where the real-time constraint itself drives the design distinction.

Tim also suggests introducing cooldowns — cautiously, since players have mixed feelings about them. Some skills get brief cooldowns, others long ones, and some become once-per-combat abilities.

5. Healing Mechanics

Instant healing (jam a stimpak, get full HP) works fine in turn-based but feels wrong in real-time. Tim recommends heal-over-time (HoT) — inject the stimpak and watch your health bar grow while damage continues to chip away at it.

This opens up design space: small instant heals, large slow HoTs, fast HoTs, hybrid heals (some instant + some over time). The interplay between incoming damage and healing rate becomes a real-time balancing lever.

6. Looting and Inventory UX

If looting doesn't stop time, the interface must be dead simple — no grid-based inventory. Click items to grab them; they go straight into your inventory unless it's full.

For the player's own inventory, the key question: does opening it pause the game? If yes, you can keep a complex inventory screen. If no, it needs to be streamlined — but then that same streamlined UI is what you use outside combat too. Tim advises against having two separate inventory interfaces.

A middle ground: only items in accessible slots (belt, top of pack) are reachable during combat. Everything else is locked until combat ends.

The overall UX solution: hotkeys everywhere. Banks of hotkeys for skills, items, and weapons — this is why games like Diablo work.

7. Perks: What Survives and What Dies

Perks that still work:

  • Faster stealth movement
  • Bonus XP, hit points, damage resistance
  • Anything that doesn't reference action points or turn order

Perks that must be scrapped or completely rebuilt:

  • Earlier Sequence (no turns = no sequence)
  • Action Boy, Bonus Move, Bonus Rate of Fire, Bonus Hand-to-Hand Attacks
  • Anything referencing action points

Rebuilt perks would need to control attack speed or movement rate — effectively becoming entirely new perks with independent balancing. At that point, you're not adapting the old system; you're designing a new one.

8. The Inevitable Balance Pass

After all these changes, nothing will be balanced correctly on the first try. A full balance pass is required across every system — perks, skills, UI, weapons — looking for friction points, useless options, or mechanics too complex for real-time decision-making.

9. Multiplayer: Still No

Even with real-time combat, Tim firmly rejects multiplayer for Fallout. His reasoning is about core identity, not mechanics:

  • Fallout's world should feel desolate — bunny-hopping vault dwellers in groups destroy that
  • It should feel uncaring — running with friends who have your back undermines this
  • Player choices should matter — but another player can reach a town first and kill everyone, voiding your agency

Multiplayer is fundamentally incompatible with what makes Fallout feel like Fallout.

10. References