Can We Finally Agree That Dragon Age: The Veilguard Was Actually Terrific?

Polygon ·

BioWare is closing after three decades, making 2024’s Dragon Age: The Veilguard the studio’s final game. The article argues that the RPG deserves a better legacy than its lukewarm reception, saying its troubled development and online backlash obscured what it achieved.

The game’s development began with a cancelled prototype in 2017, then included live-service plans before EA and BioWare rebooted it in 2021 as a single-player RPG. It faced criticism over its art style, story focus and nonbinary character Taash, whose storyline addresses the conflict between identity and Qunari culture. The article says reviews were solid but not exceptional, citing an 82 Metacritic score for the PlayStation 5 version; the supplied text ends before giving sales figures.

In short

  • The Veilguard became BioWare’s final game as the studio closes.
  • Its development shifted from live service to single-player.
  • The article argues online backlash overshadowed its merits.

Steelman: both sides, in good faith

The strongest fair case each way — we don't pick a winner.

The case for

The Veilguard merits a more generous reassessment: despite a disrupted development, it delivered a polished single-player RPG, and its solid reviews suggest real strengths in play and storytelling. Online controversy over its art style and Taash’s identity storyline may have overshadowed those achievements, so judging the game on its own merits could give BioWare’s final release a fairer legacy.

The case against

A disappointing legacy can also be a fair judgement: an 82 Metacritic score is respectable, but does not establish that the game was exceptional or that criticism was mainly driven by online backlash. Players may reasonably find its art style, story focus or handling of cultural and identity conflicts unpersuasive, and the troubled development history does not by itself make the finished game terrific.

Entertainment Gaming

Read the full article at the source →

Log in to join the discussion