Prologue: The Genesis of a Vision

The air in the dorm room was thick with the smell of instant noodles, stale coffee, and the electric hum of three overworked laptops. It was 2012, and in a modest university accommodation in Shanghai, three young men—Liu Wei, Cai Haoyu, and Luo Yuhao—were not just planning a game; they were attempting to architect a second life. Their vision was a world so vivid, so emotionally resonant, that players would forget they were merely interacting with code and polygons. This was not a whimsical dream of teenagers; it was a calculated, almost rebellious, bet against the prevailing wisdom of the Chinese game industry, which was then dominated by free-to-play mechanics, simplistic art, and transactional narratives. Their audacious goal was to prove that a small team, armed with a radical philosophy and an unwavering commitment to quality, could create an experience that would resonate globally. The crucible of this ambition—the intense, resource-starved, ideologically pure environment of that dorm room—forged the foundational tension that would define miHoYo for a decade: the relentless pursuit of boundless creative ambition within the inescapable constraints of finite resources and time. This chapter is the story of that genesis, of the philosophical bedrock laid in those early days, and of the first, fragile prototype that would eventually become *Honkai Impact 3rd*. It is the story of how a desire to build a world necessitated the invention of a system to build worlds.

The trio’s backgrounds were a study in complementary tension. Liu Wei, the pragmatic engineer, saw the world as a series of solvable problems. For him, the virtual world was first and foremost a magnificent technical challenge: a persistent, dynamic simulation capable of supporting rich interaction. Cai Haoyu, the artistic visionary, was driven by a deep desire to evoke *feeling*—the sublime awe of a vast landscape, the intimate sorrow of a character’s loss, the visceral thrill of perfectly timed combat. He worshipped at the altar of cinematic storytelling and visual poetry. Luo Yuhao, the strategic anchor, understood the brutal realities of the market. He was the bridge between pure creation and commercial viability, constantly asking how their art could find its audience, how their technology could be sustained. Their shared dorm became a constant, vibrant debate club, a pressure cooker where these perspectives clashed and fused. The core thesis that emerged from these late-night discussions was both simple and profound: the true potential of interactive entertainment lay not in the dominance of one discipline, but in the synergistic fusion of Technology, Art, and Storytelling. This was their “holy trinity,” a non-negotiable pillar. A game could not be merely a technical showcase (a common pitfall for many engine-driven projects), nor merely a passive film (the risk of overly cinematic titles), nor merely a mechanical Skinner box (the prevailing model of the time). It had to be all three at once, in a state of perpetual, dynamic equilibrium.

This philosophy was radical in its context. The prevailing industrial logic, especially in China, was one of specialization and modularization. Art, programming, design, and writing were siloed. An artist delivered assets to a programmer who implemented them in a designer’s level, which a writer might later flavor with dialogue. The result was often a disjointed experience, a concatenation of parts rather than a unified whole. miHoYo’s nascent vision demanded the opposite: integration from the ground up. The story had to inform the art direction (a tragic backstory demanding a specific color palette and architectural decay), which had to inform the technical requirements (a dynamic weather system to mirror emotional tone), which had to inform the gameplay mechanics (combat moves that were narratively justified character expressions). This was not a linear pipeline but a constant, messy feedback loop. The technical limitation of the time only intensified this need for integration. They couldn’t afford to build massive, bespoke assets for every scene. They had to create systems—procedural generation, smart asset reuse, modular design—that could serve multiple narrative and artistic purposes. The engine they would eventually build was not conceived as a tool to *display* pre-made content, but as a narrative instrument, a system capable of *generating* meaning through interaction.

The first concrete expression of this philosophy was a prototype. Not a design document, not a PowerPoint, but a playable, skeletal thing coded in a rush. It was a top-down, arena-based action game featuring a blonde girl in a sailor uniform fighting biomechanical horrors. This was the embryonic form of *Honkai Impact 3rd* and its protagonist, Kiana Kaslana. The prototype was brutal in its simplicity but revolutionary in its intent. It wasn’t just about hacking and slashing; the combat animations were meticulously crafted, each combo a short, silent story of determination and struggle. The enemy designs—twisted amalgamations of flesh and machine—spoke of a world gone wrong. The very act of playing felt weighty, impactful, and strangely melancholic. This tiny, playable kernel contained the entire miHoYo DNA: the technical achievement of smooth, high-frame-rate 3D combat on mobile hardware; the artistic direction of a distinct, anime-infused aesthetic with a dark sci-fi twist; and the storytelling through environmental detail and character action, with barely any dialogue. It was proof that their tripartite philosophy could manifest in a tangible, interactive form. Yet, it was also a terrifying glimpse of the mountain ahead. Building this prototype had taken months. Scaling it into a full-fledged, narratively rich, technically polished game with dozens of characters, hours of cutscenes, and complex systems seemed impossible for three people.

Here, the core tension crystallized. Their ambition was infinite—a living, breathing world with the emotional depth of a novel and the visual splendor of a blockbuster film. Their resources were desperately finite—three recent graduates, a shoestring budget, and the looming threat of failure that stalked every startup. The conventional solution in the game industry would have been to reduce scope. Make a simpler game. Cut the story. Use cheaper art. Prioritize monetization mechanics. This was the path of pragmatism. But for the trio, scope reduction felt like a betrayal of their founding vision. To dilute any of the three pillars—tech, art, or story—was to produce something they would not recognize as their own. The question that haunted their dorm room was not *if* they could make a game, but *how* they could make *their* game. The answer, slowly dawning on them, was not to work harder within the old industrial model, but to invent a new one. The solution was not to find more resources, but to multiply the effectiveness of the resources they had.

This nascent idea—that the bottleneck was not labor but systemization—was the glimmer of a systemic solution. If they could not hire a hundred artists, they needed tools that allowed one artist to do the work of ten. If they could not afford endless custom animation, they needed a combat system where a small set of animations could be recombined in endless, meaningful ways. If they could not script every narrative beat by hand, they needed world-building systems where lore and environment generated each other. The engine they would build was the answer to this riddle. It was to be a force multiplier, a set of interconnected pipelines and tools designed from the ground up to serve the integrated philosophy. The art pipeline would feed directly into the narrative database. The animation system would be tied to combat stats and character lore. The level editor would be a storytelling tool. This was the birth of an industrialized approach to storytelling