DOCUMENTATION

Nine Realms wasnt just a game. It was a systems problem wearing the costume of mythology.

Every enemy had to feel dangerous. Every ability had to feel meaningful. And the economy had to hold — not just for one player, but for the entire ecosystem of progression, loot, and player-perceived value.

I built the mathematical backbone of that world. Not conceptually — literally. Damage formulas. XP curves. Faucet/sink balance. Then I wrote the universe those numbers lived inside: the lore, the characters, the nine realms themselves.

Nine Realms was designed before it was built.

The game's fiction, world design, and system architecture took shape on paper first. I assembled the team based on that design — I derived what skills were needed from the design itself, rather than adapting the design to whoever was available.

That order matters. In most indie studios, the team assembles first, then the game gets written. In Nine Realms, the game was designed first — and the team was chosen to match what that design required.

PlayStation and Xbox don't partner with every game.

Core criteria for their partner programs include system quality and documentation clarity — the ability to explain why specific decisions were made about economy, progression, and combat balance, and what effect those decisions have on player experience.

What met that standard in Nine Realms was simple: every design decision was mathematically defensible. Every number had a reason. Every balance decision had a simulation behind it.

The partnership didn't come from "this game looks good." It came after a design documentation presentation.

The story of this project begins before 2020. In high school, in the middle of lessons I found boring, I was writing things down. Characters. Dialogues. World rules. The story and lore of Everything Is for Humanity took shape during that time, within the pages of those notebooks.

But I lacked the technical proficiency. When it came to gamification, mechanics, and puzzle design, I would get stuck. Ideas remained on paper.

Years later, when it was time to start the first real studio project, I pulled out those old notes. The drawings, the dialogues, the world designs. And I rewrote it from scratch—this time with technical proficiency, a team, and a real production line.

An obsession that started in high school turned into a game released on Steam in 2022.

The biggest trap in horror is this: It is assumed that fear comes from visuals. Jump scares, darkness, blood.

What I wanted to test in Everything Is for Humanity was different: When a player understands the system, realizes what the system means, when the environment says something silently—can that be eerie enough?

This is why puzzle design was critical. Each puzzle had to feel "discovered" rather than "solved." The player shouldn't learn something—they should remember something. And that remembering needed to be unsettling.

"Level layouts implemented directly in-engine."

B2B contract work is where theory meets accountability.

A client came with an idea — not a concept, not a design, just a direction. I built everything else: the systems architecture, the economy, the progression logic, the documentation. The design was mine from the ground up.

One thing I cannot disclose here: information covered by NDA. The game's name, client details, specific numbers — these remain confidential. But I can describe what I did and why it matters.

In an MMORPG, changing one variable breaks six others.

Increase Warrior class damage output by 5% — Mage PvP win rate drops. Adjust loot drop rates — economic inflation shifts. Change the XP curve — the casual player's sense of progression breaks.

The design challenge wasn't building the system — it was building a system the engineering team inheriting it could sustain and develop after I left.

Every GDD page was written with that in mind: not just "how does this work," but "can someone who comes after me understand why this decision was made?"

Every major game design debate eventually comes back to the same question: What actually keeps a player playing?

Is it visual quality? Narrative? Production value?

Or — if designed correctly — can a single well-crafted mechanic be enough?

I built this project to find out.

Hypothesis: A single well-designed interaction loop — stripped of visual polish, narrative scaffolding, and conventional production value — can produce genuine player engagement and emotional response.

Independent variable: Mechanic quality. Controlled variables: Visuals (deliberately retro and minimal), narrative (deliberately thin), production value (reduced to functional).

Target mechanic: A door/choice system — binary decisions with escalating psychological weight, generating fear through anticipation architecture rather than audio-visual shock.

The door/choice mechanic is one of the least theorized tools in game design.

Fear is never what's behind the door. Fear is the moment before you open it.

This is the Zeigarnik Effect in its purest interactive form — the mind fixates on suspended events, not resolved ones. Every decision closes one loop and opens two more. The design challenge wasn't building the mechanic — it was calibrating it. Pacing the reveal correctly. Engineering the exact moment when player anxiety peaks just before the loop resolves.

I didn't tell anyone about this project. Not friends. Not social media. Not my 120,000+ subscribers.

That wasn't a lack of time or resources. It was a methodological decision. If I had launched under my own name, every review would carry that social weight — and the market signal would be contaminated.

So I launched anonymously. Durultay Games is an independent label. No cross-promotion. No announcement. Every player found the game through Steam's organic discovery systems. Every review was written by a stranger.

This wasn't humility. It was methodology.

During the prototype phase I couldn't talk about the project to anyone. I also couldn't test it myself — I had designed every beat, so I couldn't genuinely measure whether the fear mechanics were working.

The solution was practical: I played it with my wife, who dislikes horror games. I had neighbors try it. I noted micro-expressions, hand tension, and the specific moment each person decided to continue or stop.

Those observations directly shaped the door animation timing, the audio cues, and the pacing of the tension curve.

91% Very Positive. 83+ verified reviews. From players with no relationship to the designer.

Players didn't say "the graphics are great." They said "I couldn't stop." Players didn't say "the story hooked me." They said "I was genuinely scared."

The mechanic held. Without visual support. Without narrative primer. A single well-calibrated interaction loop produced real fear, real tension, and real player retention.

Hypothesis confirmed.

This experiment does not argue that visuals and narrative are irrelevant. They aren't. World-class art direction and deep narrative architecture act as multipliers — they amplify a mechanic that already works.

What this experiment proves is a sequencing principle: mechanic integrity is the foundation, and everything else is architecture built on top of it. A beautiful game with a broken loop fails. A minimal game with a clean loop survives.

I bring this philosophy to every project.