The Hidden Craft Behind Larian’s Next Divinity RPG

Larian Studios, the team behind Baldur’s Gate 3 and the Divinity series, has become a modern symbol of what story-driven RPGs can achieve. When its founder and director publicly credits “unsung heroes” for enabling the studio’s next big Divinity game, it highlights a truth many players never see: the most important work in game development rarely appears in trailers, patch notes, or awards speeches.

This article explores the invisible labor that turns Larian’s wild, systems-driven ideas into a playable reality. Drawing inspiration from recent discussions around Larian’s in-development Divinity project, we’ll look at the teams, tools, and practices that make a massive RPG possible—and why celebrating them matters for the future of the medium.

From Baldur’s Gate 3 to a New Divinity: Raising the Bar Again

After the runaway success of Baldur’s Gate 3, expectations for Larian’s next Divinity RPG are sky-high. The studio is known for:

• Complex, reactive storytelling with extensive branching paths
• Turn-based combat that rewards experimentation and creativity
• Co-op and multiplayer systems that let players break the story in delightful ways
• Robust mod and systems support that encourages community tinkering

Scaling from earlier Divinity titles to Baldur’s Gate 3 already required huge changes in team size, budgets, and development processes. Industry reporting and public presentations reveal that BG3 involved hundreds of developers, spanning multiple studios and locations, with sophisticated pipelines to manage content, testing, and iteration at scale.¹ Now, Larian faces a new challenge: how to take everything it learned on BG3 and apply it to an original, non-licensed Divinity game—without the guardrails and constraints of Dungeons & Dragons.

That challenge doesn’t rest solely on directors or lead designers. It depends on the people who keep data in sync, keep build tools running, watch performance metrics, organize playtests, and ensure that thousands of small tasks move forward each week. These are the “unsung heroes” behind the announcement headlines.

The Invisible Backbone: Production, Operations, and Support

In many interviews and postmortems from large studios, producers describe themselves as “human routers” or “force multipliers.” Their work is difficult to showcase in a trailer but absolutely essential to projects as big as Larian’s games. The same applies to operations teams, internal IT, and administrative staff.

Producers: Orchestrating a Moving Target

On sprawling RPGs, producers and project managers often:

• Break high-level creative visions into concrete milestones
• Coordinate work across disciplines—art, code, sound, narrative, QA
• Maintain schedules and risk assessments as features evolve
• Support communication across time zones and studio locations

The International Game Developers Association (IGDA) notes that modern game production increasingly resembles complex software projects, where agile and hybrid methodologies are used to stay flexible.² For a studio like Larian, whose games are defined by systemic complexity and player freedom, that flexibility is vital: a single change to a combat rule or dialogue system can ripple across hundreds of quests, encounters, and cinematics.

Operations and IT: Keeping the Lights On

Less visible still are the teams who maintain infrastructure:

• Build servers that compile the game multiple times per day
• Version control systems that track changes to thousands of files
• Network and hardware support for developers across multiple countries
• Security practices that protect both intellectual property and player data

As the game industry has become increasingly globalized, maintaining secure, performant infrastructure is not optional. The European Commission has highlighted the importance of secure digital infrastructure and resilience for creative industries, including games, in maintaining competitiveness.³ Without those foundations, even the greatest RPG designs would never leave a designer’s notebook.

Tools Teams: Building the Machines That Build the Game

One of the least celebrated but most impactful roles in large RPG development is the tools engineer. Players often imagine level designers manually scripting every interaction, but in practice, powerful internal tools and editors magnify what creative teams can achieve.

Custom Engines and Editors

Larian’s games run on a proprietary engine that has evolved over multiple projects. Tools engineers and technical designers work together to create and maintain:

• World and level editors that let designers assemble maps, encounters, and interactive objects
• Dialogue and narrative tools for branching conversations, flags, and conditions
• System configuration panels for combat rules, AI behavior, status effects, and item properties
• Automation scripts for generating and validating content at scale

The Game Developers Conference (GDC) has featured multiple talks in recent years about the impact of better tools on production efficiency and creativity, with studios reporting substantial time savings when editors are designed around developer workflows.⁴ For a deeply systemic RPG, better tools don’t just save time—they also reduce bugs and enable more ambitious narrative branching.

Why Tools Matter Especially for Divinity

Larian’s Divinity games are famous for emergent interactions: oil slicks catching fire, electricity arcing across water, physics-driven object shenanigans. Supporting that style of play requires internal tools that:

• Let designers quickly prototype new environmental combos
• Show how status effects and surfaces interact under different conditions
• Help QA reproduce and log issues that arise from obscure combinations

For the next Divinity RPG, these tools will be even more critical. The studio is no longer adapting an existing ruleset like D&D; it is defining, testing, and balancing its own systems from scratch. That means tools must support constant iteration, and tools teams become key partners in both design and production.

Writers, Narrative Designers, and the Burden of Reactivity

The narrative of Baldur’s Gate 3 drew wide praise for making player choices feel meaningful and remembered over dozens of hours. Reaching that level of reactivity demanded a huge writing and narrative design effort, supported by pipelines that track branching storylines, variables, and cinematic triggers.

Building Stories That Remember You

For the next Divinity game, Larian’s writers and narrative designers face similar expectations, but in a new universe of their own making. Their tasks include:

• Creating a coherent lore foundation: cultures, histories, religions, and factions
• Designing quest structures that can flex around different playstyles
• Writing dialogue that accounts for party composition, prior choices, and outcomes
• Coordinating with gameplay teams so narrative choices have mechanical consequences

Research on narrative in games by scholars such as Espen Aarseth and Marie-Laure Ryan has emphasized the unique challenges of interactive storytelling, where players are co-authors rather than passive recipients.⁵ In large RPGs, this means narrative teams must continually anticipate off-script behavior and ensure the world responds believably—even when players do things the writers never expected.

Localization and Cultural Adaptation

Another unsung aspect of narrative production is localization. For global releases, thousands of lines of dialogue must be translated and adapted to multiple languages while preserving tone, humor, and character voice. This involves:

• Localization producers coordinating schedules and assets
• Translators working closely with lore bibles and context notes
• QA teams checking in-game text for consistency and context

As digital games have become a major cultural export for regions like the EU and North America, localization is recognized as both an economic necessity and a cultural responsibility.³ For a narrative-heavy RPG, localizers are effectively co-writers, bringing the world to life for players everywhere.

Quality Assurance: Guardians of Stability and Coherence

RPG fans often joke that “you can’t ship without bugs,” but there’s a vast difference between a quirky cosmetic issue and a progression-breaking quest failure. Quality assurance (QA) teams stand between players and chaos, especially when a game allows extreme player freedom.

What QA Actually Does on a Massive RPG

Contrary to stereotypes, QA is not just about “playing the game early.” Testers and QA engineers:

• Design test plans and coverage strategies for quests, systems, and platforms
• Reproduce and document bugs with precise steps and data
• Run regression tests after each major build or feature change
• Collaborate with developers to prioritize issues based on impact

The Entertainment Software Association has underlined the growing complexity of game testing as titles span multiple platforms, online modes, and content updates.¹ For Larian’s next Divinity game, QA’s job will likely be even harder than before: new systems, a new ruleset, and complex co-op interactions mean more edge cases—and more potential for players to break things in creative ways.

Playtesting and Feedback Loops

In addition to formal QA, structured playtesting helps reveal:

• Balance issues in combat and progression
• Quest clarity problems and “where do I go next?” friction
• UI and UX pain points that slow players down
• Moments where narrative choices feel unfair or misleading

Many modern RPGs rely on iterative feedback cycles—internal playtests, external focus groups, or early access programs—to refine their experience. While Larian has not publicly detailed how it will approach testing for the new Divinity title, its experience with early access on previous games suggests that community feedback will once again play a major role. The unsung heroes here include community managers, user researchers, and analysts who translate raw feedback into actionable insights.

Comparing Roles: Who Does What?

The following table summarizes some of the less-visible roles that contribute to a large-scale RPG like Larian’s next Divinity project.

Why Public Praise for “Unsung Heroes” Matters

When a high-profile studio head publicly praises support and backend teams, it’s more than a feel-good moment. It challenges a persistent myth in both games and other creative industries: that success is driven mainly by visionary leaders and star creators.

Shifting the Narrative Around Game Development

In reality, research into creative industries—from film to software—shows that enduring success rarely comes from lone geniuses. Instead, it arises from well-coordinated teams, robust infrastructure, and cultures where collaboration is valued.² By spotlighting the people who maintain tools, coordinate schedules, and stabilize builds, studio leadership sends a signal about what the studio values internally.

For employees, that recognition can improve morale and retention; for aspiring developers, it can broaden perceptions of what a “real” game development job looks like. Not everyone needs to be a designer or artist to contribute meaningfully to the next great RPG.

Setting Expectations for Players

Publicly acknowledging the scale and complexity of development also helps temper player expectations. When fans see that a game involves hundreds of people across disciplines, it becomes easier to understand why:

• Delays may occur as teams stabilize new features
• Major updates require extensive testing before release
• Seemingly simple requests might have complex dependencies

The more transparent studios are about these realities, the more room they have to prioritize long-term quality over short-term marketing beats.

Looking Ahead: What This Means for the Next Divinity RPG

Larian’s upcoming Divinity game exists at the intersection of high expectations and hard-won experience. The studio:

• Knows firsthand the scale of effort required to ship a critically acclaimed RPG
• Has invested years into building a proprietary engine and toolset
• Has cultivated a community that expects depth, reactivity, and freedom

Delivering on those expectations again will rely on more than clever combat or striking concept art. It will depend on:

• Mature pipelines that can handle enormous volumes of content
• Well-resourced QA and localization to ensure global players get a polished experience
• Stable infrastructure and tooling that give developers time to focus on creativity rather than firefighting

When studio leadership publicly celebrates the people building and maintaining those pipelines, it hints that the next Divinity game is being crafted not just as a passion project, but as the product of a healthy, learning organization. For players, that’s good news: great games are less likely to be accidents when the systems that support them are intentional and robust.

Key Takeaways for RPG Fans

• Massive RPGs like Larian’s next Divinity project depend on hundreds of specialists whose names rarely appear in marketing.
• Tools engineers, producers, QA teams, and operations staff make bold narrative and systemic design possible at scale.
• Public recognition of these roles signals a healthier internal culture and more sustainable development practices.
• Understanding this invisible work can help players set more realistic expectations around scope, timelines, and post-launch support.

As anticipation builds for Larian’s new Divinity RPG, paying attention not just to trailers, but to how the studio talks about its people and processes, can offer valuable clues about the game’s eventual quality. Great RPGs are made, not magically conjured—and the makers deserve to be seen.

Frequently Asked Questions

What makes Larian’s RPGs stand out from other role-playing games?

Larian’s RPGs are known for systemic depth, reactive storytelling, and support for cooperative play. Instead of scripting every possible outcome, the studio builds rule-based systems—environmental interactions, status effects, AI behaviors—that combine in unexpected ways, giving players freedom to improvise solutions. Its games also prioritize meaningful narrative choices and character-driven stories.

Why are “unsung heroes” so important in AAA and large indie development?

Roles like tools engineers, QA, producers, localization staff, and operations don’t directly create visible assets, but they ensure the project runs smoothly and scales. Without them, content teams would be overwhelmed by technical issues, coordination problems, and unstable builds, making it much harder to deliver complex games on any reasonable timeline.

How does the next Divinity RPG differ from Baldur’s Gate 3?

While detailed public information is still limited, one major difference is that the new Divinity game will use Larian’s own setting and rules instead of the Dungeons & Dragons license that underpins Baldur’s Gate 3. That gives Larian more creative freedom, but it also means the studio must define, test, and balance its own systems and lore rather than relying on an established framework.

What skills are useful for someone who wants to work in these “hidden” roles?

It depends on the role, but broadly:

• Tools engineers benefit from strong software engineering skills and an interest in UX for internal users.
• Producers need communication, organization, and basic understanding of multiple disciplines.
• QA roles require attention to detail, methodical thinking, and clear documentation skills.
• Localization demands language proficiency, cultural literacy, and sensitivity to narrative nuance.

Will recognizing these roles change how games are marketed?

Marketing will always prioritize instantly understandable hooks—visual spectacle, story premises, and recognizable IP. However, as more studios and journalists highlight behind-the-scenes work, players may place greater value on development transparency and studio culture, which can indirectly influence marketing narratives over time.