Former Elder Scrolls Designer Says a Timeline Typo May Have Inspired Dragon Breaks

One of The Elder Scrolls’ most famously elastic lore devices may have begun with the least mystical force imaginable: somebody entering the wrong date.

Kurt Kuhlmann, a writer and designer who worked at Bethesda from 2003 to 2023, has said he is convinced that a conspicuous multi-millennial gap in an older series timeline was, in real-world terms, a typo. Rather than quietly correcting or ignoring the oddity, the setting ultimately gained Dragon Breaks: metaphysical disruptions in which time, history and causality stop behaving in a single, tidy line.

It is an entertaining origin story because Dragon Breaks have become a useful answer to an extremely practical RPG-writing problem. The Elder Scrolls II: Daggerfall has multiple possible endings. A later game that wants one shared history must normally decide which player outcome “really” happened. The lore-driven alternative was much stranger: treat every outcome as having occurred, while accepting that nobody inside the world can provide a clean, universally agreed account of events.

In short, a possible clerical blunder became an in-universe feature. That does not make the typo theory confirmed historical fact; Kuhlmann presented it as his personal certainty about what happened in production. But his account offers a useful look at how long-running game worlds can turn continuity pressure into fiction rather than merely sweeping it away.

The gap that became a possibility

Kuhlmann described an old timeline created in the Daggerfall era that contained a substantial jump between dates: the final date of one year and the first date of the next were separated by roughly 3,000 years. His view is that the gap was accidental, the result of a date being typed incorrectly.

That kind of inconsistency could have been handled as a mundane editorial correction. Large fictional settings are built by many people over many years, and timelines are particularly vulnerable to mistakes because they compress huge amounts of story into small pieces of data. A wrong numeral can create a contradiction far larger than its original typo suggests.

But in this case, the discontinuity proved creatively attractive. Michael Kirkbride, a concept artist, writer and designer on the series, saw scope in the anomaly and developed the Dragon Break idea around it. Kuhlmann connected that development both to the timeline gap and to the question of what to do with Daggerfall’s divergent conclusions.

The resulting lore does not simply say that historians made a mistake. It makes uncertainty part of the setting’s architecture. A Dragon Break is a period in which temporal order fractures or becomes unreliable, leaving incompatible accounts and outcomes able to coexist. That is deliberately more complicated than a canonical retcon, but it gives the series room to preserve the significance of player choice without forcing every later game to inherit a single selected ending.

Why branching endings create sequel headaches

Branching endings are one of role-playing games’ strongest promises. They tell players that decisions can produce materially different consequences. The trouble arrives when a sequel needs to establish a stable starting point.

There are a few broad ways a series can respond:

Select one outcome. A later installment declares a particular route to be the historical version, even if other endings were available to players.
Minimize direct references. A sequel can avoid specifying past choices where possible, though this can leave previous decisions feeling disconnected from the wider series.
Move far enough forward in time. A later story can create distance from prior events and their immediate consequences.
Build ambiguity into the fiction. This is the path Dragon Breaks represent: multiple outcomes are retained through a setting-specific explanation.

Kuhlmann’s point was that the conventional approach is usually to pick an outcome and continue. That is straightforward, but it also means some players learn that their ending was not the one future continuity chose. The problem is not unique to fantasy games; it is a structural tension between an individualized playthrough and a franchise that wants a common history.

The Elder Scrolls did not solve that tension by claiming every branch is equally ordinary. Instead, it attached the convergence of incompatible outcomes to an extraordinary event involving Numidium and a break in time. The implausibility is the point. A normal historical explanation would not be able to make mutually exclusive events all true at once, so the fiction introduces a condition under which normal history is no longer sufficient.

What a Dragon Break means in plain terms

The phrase “Dragon Break” can sound like a piece of lore intended to intimidate anyone without a stack of in-game books beside them. At its basic level, it describes a rupture in linear time.

Linear time is the ordinary assumption that events happen in one order: one cause leads to one effect, and a particular past leads to a particular present. A Dragon Break challenges that assumption. Differing outcomes can be experienced, remembered or recorded without a single uncontested version winning out. The aftermath is therefore not merely confusing because evidence is missing; it is confusing because reality itself has not produced a neat, singular answer.

The name is tied to Akatosh, the Dragon God of Time. The concept is also associated here with Numidium, the figure or force invoked in Kuhlmann’s description of the attempt to make Daggerfall’s endings coexist. These proper nouns matter because they anchor what might otherwise look like a meta-writing patch inside the setting’s own mythology.

That dual purpose is why the device has endured. At the production level, it is a continuity solution. At the narrative level, it creates an atmosphere in which certainty is limited, official accounts can be contested, and metaphysical events have consequences that ordinary chronology cannot cleanly contain.

An editorial workaround that became worldbuilding

The most interesting part of Kuhlmann’s recollection is not simply that a typo may have existed. It is that the creative response was to expand the setting around the mistake rather than erase it.

There is a meaningful difference between covering a continuity gap and incorporating it. A cover-up tends to reduce attention: the inconsistency is quietly changed, replaced or left unmentioned. Incorporation turns the inconsistency into new material. It gives writers and players a reason to think about why accounts conflict, why the timeline is strange, and why a clean answer may not exist.

That choice also suits a series built around interpretation. When history has been scrambled by a Dragon Break, certainty becomes something characters can argue over rather than a fact delivered from outside the world. The lore gains space for contradictory testimony without automatically treating every contradiction as an error in need of repair.

There is a risk to this approach. If used carelessly, “time broke” can become a catch-all explanation that dissolves stakes instead of enriching them. Any continuity device works best when it clarifies what the fiction is trying to preserve. In this case, the apparent goal was specific: acknowledge Daggerfall’s varied outcomes while allowing subsequent Elder Scrolls stories to operate from a shared but uncanny historical foundation.

That is a narrower and more purposeful use than simply declaring that anything can happen. The lore does not remove the need for writers to make choices going forward; it changes the terms on which a past set of choices can be remembered.

Why the anecdote matters beyond one date entry

Game development produces documents, drafts, spreadsheets and timelines alongside code and art. Not every small inconsistency becomes important. Most should not. Yet Kuhlmann’s account is a reminder that unexpected artifacts can sometimes reveal a better creative direction than the original plan.

The lesson is not that mistakes are automatically valuable, or that a fictional universe should preserve every error as sacred canon. It is that teams can examine whether an anomaly opens a meaningful storytelling door. The useful question is not “Can this be excused?” but “Does building on this make the world more interesting and make the game’s prior choices easier to respect?”

For The Elder Scrolls, the answer appears to have been yes. The Dragon Break framework provided a way to treat the aftermath of branching role-playing decisions as lore rather than administrative cleanup. It also helped establish a setting where cosmic strangeness and disputed history are not exceptions to the world; they are part of its texture.

There is a broader contrast with the way RPG sequels often establish a single inherited reality. A fixed choice can make a timeline easy to explain, but it can also make the player’s alternate path feel less durable. Dragon Breaks offer a more audacious proposition: the player’s outcome does not have to disappear just because another player’s outcome was different.

That willingness to make a complication into mythology is part of why the story remains memorable. A gap that may have started as a wrong number became a framework for discussing time, truth and player agency. For fans revisiting older fantasy RPGs, including the wider genre conversation around games such as The Witcher 3: Wild Hunt, it is also a sharp illustration of how sequel continuity can be as much a design challenge as a plot challenge.

The key detail in Kuhlmann’s account is its uncertainty: he believes the original gap was a typo, while the Dragon Break concept was the imaginative response that gave the anomaly a lasting place in the fiction.

So the next time an Elder Scrolls history lesson becomes a maze of incompatible accounts, a missing stretch of time and metaphysical logic, it may be worth remembering the mundane possibility at its root. Sometimes a setting’s grandest mysteries begin not with an oracle, a god or an ancient artifact, but with somebody entering the wrong date and another creator deciding it was too interesting to waste.