01. Overview
Mothlight is a third-person 3D stealth psychological horror game about a small moth-like creature who hoards memories inside a haunted manor owned by a monstrous family.
She is invisible by default. Noise makes her visible, and so do fear, sprung traps, and objects left out of place: the monsters know their rooms, and they notice when something has been moved.
Her invisibility is not a power: it is what the family did to her. They decided, long before the game begins, that she does not belong in the house, and she believed them so completely that inside the manor it became physical. So the player sees a soft, wide-eyed creature, while the monsters see vermin.
What pulls her into danger is wanting. She is a moth – drawn to luminous things – and memories shine, light beckons, and everything she wants sits in plain view.
At her scale, furniture is architecture, rooms are hostile landscapes, and crossing a floor is a stealth problem.
The manor belongs to her monstrous family; it doesn’t want her there, it doesn’t want her to leave, it feels like home.
02. The Design Problem
I wanted a horror game in which the player feels small, unseen, and unsafe without relying necessarily on combat power or scripted jump scares.
That meant two rules from the start.
First, fear had to be a system, not an event: because the moth’s visibility is tied to her emotional state, panic is a mechanical liability the player learns to regulate, and staying calm is itself a survival skill.
Second, the monsters could not be obstacles with health bars. Each one is a member of the family that owns the manor, with their own territory, behaviour, emotional history, and reasons. Each of them has their own way of finding you. One hunts by sound, another by sight, another by noticing that something in their room has been moved. Each monster is a different stealth grammar the player has to learn. They hunt you, and the longer you survive, the better you understand why. That understanding is where the horror lives.
03. How It Plays
The player’s first goal is simple: leave. The door behind them is locked, and the only way out is further in.
Exploration is never neutral. The moth is drawn to light, and memories appear as luminous objects scattered through the manor. Following them is dangerous: light leads toward monsters, traumatic spaces, and choices the player does not yet understand. But light is also the only way forward.
Memories are the game’s currency and its moral ledger. They come in three kinds: core, true, and false. The player can carry them, return them, or consume them. Every option does something, and every option costs something.
Memories also have weight. Hoarding them slows the moth down and makes her louder, and louder wakes the hunters: the player’s greed literally summons the predator.
04. Choice Example
The Collectionist (aka The Collector) is one of the manor’s monsters: an obsessive trapper who keeps a wunderkammer of things he could not let go.
His encounter is designed to make the player hate him. His game-over is deliberately ugly and unjust: he pins the moth like a specimen, with a faint smile. Nothing about him invites mercy.
If the player kills him, he drops a memory: a child’s curl of hair, kept in a film canister.
That drop is the point. The player earned their hatred, acted on it, and the reward asks whether the hatred was the whole story. Every monster in Mothlight follows this logic: the kill is always available, always justified in the moment, and always leaves the player holding evidence that the person they destroyed was once something else.
05. What Corruption Looks Like
Corruption is a choice, not a fate.
A player can cross the whole manor without feeding either corruption track, and the game honours it, but the clean path is restoration, and it is the hardest one: freeing the monsters means understanding what they lost and enduring their pain, one family member at a time.
Every kill and every lie leaves a mark, and the game keeps score on the moth’s body.
Kill and consume, and she becomes more insect-like: stronger, stranger, less herself. Manipulate and feed the monsters false memories, and she becomes more beautiful, more ladylike: less a trespasser, more one of the house’s own.
False memories carry a design rule I am particularly attached to: they have no weight. A fake memory is the only treasure in the manor that costs nothing to carry. This way the hoarding system doubles as a hidden lie detector.
06. Design References
Little Nightmares for scale and vulnerability.
Gone Home for environmental observation and non-linear exploration.
Bloodborne for fragmented lore, object descriptions, and indirect storytelling.
The shared goal: a game where the player reads the world rather than having it explained.
07. Current Development State
Mothlight began as a solo, documentation-first project: full gameplay documentation, then in-depth monster documentation, each monster defining its own emotional pattern, spatial logic, memory structure, and player-facing choices.
It is now in production with a team of five: myself on creative and narrative direction, plus a programmer, a 3D artist, an environment artist, and a sound designer. An advanced game design document exists, and a playable greybox prototype is running in Unity.
08. Why I Am Building It
I started Mothlight to design from meaning outward. I wanted to build mechanics from the story’s central ideas instead of attaching a story to mechanics that already existed, tied to a specific genre.
This is how invisibility became stealth, memory became currency and burden, and every choice in the game follows the same rule I hold in all my design work: when the player gains something, they lose something else, and they have to live with it.