The Elder Scrolls II: Daggerfall (1996)

A map bigger than the game industry knew what to do with

Daggerfall's headline feature is still its scale. Using procedural generation, Bethesda built a game world reportedly comparable in size to Great Britain, packed with over 15,000 towns, villages, and dungeons. No RPG before it had attempted anything close, and honestly very few have tried to match it since. The ambition was so far ahead of the hardware of the era that Daggerfall shipped riddled with bugs, some of which became infamous enough that Bethesda has referenced them in later games as an inside joke.

Setting: the Iliac Bay

Rather than the whole continent, Daggerfall narrows its focus to the Iliac Bay, the region connecting High Rock and Hammerfell. The story follows the player investigating the disappearance of a king's ghost, a plot that eventually spirals into one of the series' first real Dragon Break moments, where multiple contradictory endings to the game are all treated as simultaneously true in later lore.

What it introduced

A lot of Elder Scrolls staples trace back to Daggerfall rather than Arena. Character creation got far more detailed, guild reputation systems appeared for the first time, and the game's tone leaned further into political intrigue and moral gray areas than its predecessor. It's also the first entry where the writing really starts to sound like the Elder Scrolls voice fans recognize today.

Should you play it today?

Daggerfall is a harder recommendation than Arena in some ways, since its scale makes the jank more noticeable, but the fan community has kept it alive through the Daggerfall Unity project, an unofficial modern engine remake that fixes most of the original's technical problems while keeping the game intact. If you want to actually experience Daggerfall rather than just read about it, that's the version most fans point newcomers toward.