‘We Are a Little Bit Masochistic’ — Developers Are Running Scared of Baldur’s Gate 4, but Warhammer 40,000: Rogue Trader Studio Owlcat Would Consider It a ‘Great Challenge’

IGN ·

Owlcat Games, the studio behind Warhammer 40,000: Rogue Trader, says it would view making Baldur’s Gate 4 as a “great challenge” if approached, despite industry concern over matching the standards set by Larian Studios’ acclaimed Baldur’s Gate 3. Creative director Alexander Mishulin stressed that any successor should bring its own approach rather than attempt to copy Larian’s formula.

Larian has chosen not to make Baldur’s Gate 4, leaving fans to speculate about a potential new developer. Owlcat is frequently suggested because Rogue Trader was well received for its characters, story and more than 100 hours of content, and the studio is already developing Warhammer 40,000: Dark Heresy; however, Mishulin did not confirm that any Baldur’s Gate project is under discussion.

In short

  • Owlcat would consider Baldur’s Gate 4 a major challenge.
  • It says copying Larian’s approach would fail.
  • No Baldur’s Gate 4 deal has been confirmed.

Explained simply

Baldur's Gate is a long-running video game franchise known for its detailed storytelling and character-driven narratives. The most recent entry, Baldur's Gate 3 by Larian Studios, was released to widespread critical and commercial acclaim, setting a high bar for any future sequels.

Larian Studios has decided not to develop Baldur's Gate 4, creating speculation about which studio might take on the project. Owlcat Games, known for the well-received Warhammer 40,000: Rogue Trader, has emerged as a frequent suggestion amongst industry observers and fans due to the critical success of that game.

The question of who develops the next game matters because Baldur's Gate is a significant franchise with a devoted fanbase. A sequel to such a successful predecessor will face high expectations from players and critics alike.

Entertainment Gaming Software Technology

Read the full article at the source →

Log in to join the discussion