BioWare’s postmortem for Knights of the Old Republic — first published in Game Developer magazine in December 2003, scoped to the combat system rather than the whole game — is about the least glamorous work behind a 60-hour RPG: making a D20 ruleset playable with a controller. The team’s stated approach was to build on what they already had instead of reinventing it.

What went right:

  • Senior staff had already shipped Baldur’s Gate and Neverwinter Nights, so KOTOR reused the personal round-based system — one action per three-second round per character
  • Combat was choreographed in paired 1.5-second animation sequences in 3DS Max, with attacker motion and defender countermove authored in tandem, so round-based fights read as continuous on screen
  • The first interface attached context menus to every button and confused casual players; watching newcomers struggle at E3 2002 forced a redesign into an explicit combat mode with an always-visible action bar
  • QA filled out a per-encounter document — difficulty, credits and XP, tactics and Force powers used — reviewed weekly; testers optimizing for speed revealed the overpowered powers, which got nerfed

What went wrong is the more useful half:

  • The game looked like an action title, so players mashed buttons and fought the turn-based system. The authors’ rule: the scale of player actions a system allows must match the scale it operates on
  • Interface convergence took over a full year and heavy manpower. The diagnosis is precise — paper sketches and mockups lacked interactivity, so the team could only learn how controls felt by waiting
  • The tutorial compressed everything into the first hour, hurting both story flow and retention; spreading it across three or four hours would have worked better
  • The in-game combat message screen was deprioritized as player-facing polish, but it was the diagnostic tool QA needed. Bugs in it obscured real bugs, and fixing it late became a schedule risk
  • Designers were meant to prototype gameplay early in placeholder areas; the work ended up being done retroactively alongside story and scripting

The reusable lesson is not “reuse your old combat system” — that is a luxury of a studio with three prior RPGs behind it. The reusable ones are the interface year and the feedback screen: both cases where the tools for judging the game were themselves under-designed, and both fixed late at real cost.