The Foundation: Defining Immersion
When most people talk about an immersive game, they immediately point to photorealistic graphics, an emotional musical score, or a massive open world. But relying on surface level aesthetics is a trap. To build an immersive world, we must first define what immersion actually is. This requires distinguishing the feeling of being present from simply being in the zone or experiencing flow. Michailidis et al define flow as “being in the zone”. Immersion is defined as “feeling present”1. This is a crucial distinction for developers. Flow is about mechanical mastery, like entering a trance while playing Tetris. Immersion is about psychological presence, like physically ducking your head when a virtual dragon flies overhead. Immersion is not just about writing good lore. It is a measurable output of a game’s architecture.
To actually build this architecture, we need a blueprint. We can understand this through the MDA framework presented by Hunicke, LeBlanc, and Zubek, which breaks games down into three layers which are Mechanics, Dynamics, and Aesthetics.2 The mechanics are the code and rules, the dynamics are the system in motion, and the aesthetics are the resulting emotional response or immersion of the player. This framework reveals a hard truth about game development: you cannot directly program an emotion. You can only program the rules.
Furthermore, as Janik points out in their analysis of Baldur’s Gate 3, even analog rules like tabletop dice rolls must be refactored into automated code to build these underlying mechanics.3 When a player rolls a critical failure during a tense combat encounter, the resulting panic they feel is entirely generated by cold, calculated math functioning correctly behind the scenes. By treating immersion as a systemic output rather than just good graphics, developers can engineer better experiences.