Levine: Judas’ Xbox delay stems from narrative work

Ken Levine attributes the length of Judas’ development for Xbox to labor-heavy narrative systems and extensive asset organization rather than to rendering or hardware limits.

The team concentrated on building a runtime system that assembles modular narrative elements dynamically and on learning how to write stories that function inside that framework.

Levine described the effort as “not a technological hardware challenge” but an “engineering and ‘thought’ challenge” that requires a large amount of manual work.

Much of the practical work involves organizing and tagging assets and defining small game conditions that can combine with other conditions to trigger events responsive to player actions. He said the narrative systems themselves are not CPU intensive but require substantial human labor.

Levine summarized the core difficulty in two parts: creating the runtime that pieces modular elements together at runtime and then figuring out how to write stories that the system can assemble. “The reason it took so long was not really due to rendering technology or anything like that… it was figuring out how we craft this narrative system that’s combining modular elements together dynamically — at runtime — to make stories happen that’s very reactive to the player. And then we had to figure out how to write story for that,” he said.

Judas was revealed more than three years ago and still has no dated Xbox release window. The studio says the game remains a first-person shooter with immersive environments and detailed characters, similar in approach to Levine’s earlier BioShock work.

The team continues to iterate on both the systems and the writing needed to deliver stories that react to player actions. No launch date for Xbox has been scheduled.