Ravia.
My first game taught me how much work sits behind a choice that feels meaningful.
I began with a story I wanted people to get involved in. Building it in TyranoBuilder opened up a different interest: the logic needed to make choices change what happened next.
PROJECT / RAVIAI wanted players to care what happened next.
It took me a while to work out exactly what I wanted players to feel. I kept coming back to engagement: a choice should provoke a reaction because the player is invested in the story. Making those consequences persist was where I discovered the technical challenge.
Choose
Players select a response or action.
Branch
Immediate dialogue and events change.
Remember
Accumulated decision weights unlocking later choices.
The diagram distinguishes working branches from a planned counter-based consequence system. It does not imply the latter shipped.
I had to think in variables, not just scenes.
The prototype made the technical side of design compelling: state, conditions, progression and what a player can actually experience.
What started as an interest in choice-driven storytelling became curiosity about the machinery behind player agency.
The question I never wanted to answer.
Ravia leaves confinement and encounters Trauss. The story leaves room for psychological, supernatural and physical explanations.
ORIGINAL / GAME BUILDTrauss is never resolved.
The player's interpretation matters. The prototype hints at multiple readings without confirming whether the voice is a supernatural presence or a way Ravia understands her own abilities.
FIRST SUBSTANTIAL PROJECT
The beginning of technical curiosity.
Ravia taught me that a choice isn't meaningful just because a player can click it. It has to be supported by systems that can carry its consequences.
The build is short and unfinished. That's part of the story. Its value now is showing where I started learning to make decisions executable.
OPEN RAVIA ON ITCH.IO ↗