48 Hours to Build Something That Scares Me

A Solo Developer's Journey Through Global Game Jam 2026

The countdown started at 5 PM on Friday. Forty-eight hours. One theme. No team.

I sat in a room full of developers forming groups, exchanging Discord handles, sketching ideas on whiteboards. I had a laptop, a rough understanding of Unreal Engine, and a decision I'd already made: this one would be mine alone.

When the theme appeared, MASK, the noise in the room faded.

My mind went somewhere specific. Not to superheroes. Not to masquerade balls.

To a question I'd been circling since my Psychology studies:

What happens when the face we show the world becomes more familiar than our own?

I opened a blank project and started building.

The Concept

The game needed to make the player feel something true about masks—not just wear one.

The design emerged quickly:

WORN would place players in a world where masked figures roam. Wearing a mask grants safety. The figures ignore you, accept you as one of their own. But the mask has a cost. A corruption meter fills slowly. Let it reach maximum, and you lose yourself permanently. You become one of them.

Remove the mask, and they see you. They chase. But at least you're still you.

The question the player faces isn't "how do I win?" It's "what am I willing to sacrifice to survive?"

The camera system started as a functional decision. First-person felt right for vulnerability—you see what the character sees, you're present in the danger. Third-person made sense for the masked state—distance, observation, detachment. Then I tested it.

The shift wasn't just mechanical. When the player puts on the mask, they literally step outside themselves. They watch their own character from behind. The perspective change is the dissociation.

This accident became the game's thesis statement. I hadn't planned it. The constraint revealed it.

The NPCs needed to feel wrong without being explicitly monstrous. High-fidelity horror wasn't an option—I lacked the time and assets. So I went minimal. Ready assets. Masks for heads. Simple.

At 2 AM, the corruption system worked. The camera switched smoothly. NPCs detected the player correctly. The post-processing shifted between warm, saturated "safety" and cold, desaturated "reality."

The game was playable.

So naturally, I decided to add "one more feature."

By 3 AM, nothing worked. The mask toggle broke. NPCs chased regardless of player state. The UI stopped updating. Four hours of debugging later, I found the problem: a single variable that wasn't resetting properly.

The lesson burned itself into memory: after hour 36, only polish. No new systems. No refactoring. The risk compounds faster than the reward.

I knew mine couldn't be a simple escape. The theme demanded something that questioned the premise itself. The player reaches a final room. The masked figures turn toward them. Slowly, each one reaches up and removes their mask.

The faces underneath are identical. All of them are the player's face. A single line of text appears:

"We were all hiding from each other."

The monsters were never "them." They were people—each one wearing a mask for the same reason the player did. Fear. Self-protection. The belief that hiding was safer than being seen.

The horror isn't the chase. It's the loneliness we create when everyone hides simultaneously.

The build started compiling with one hour remaining. Progress bar crawling. Palms sweating. Mental inventory of everything that could go wrong. The export finished at minute 52. I uploaded. I submitted. I sat back.

The game wasn't polished. Some textures were placeholders. The AI occasionally got confused. The "cinematic ending" was black screen with white text.

But it existed. An idea that lived only in my head 48 hours prior was now something anyone could download and experience.

What I Learned

Constraints don't limit creativity. They focus it.

My original vision included branching narratives, multiple environments, dynamic dialogue, original score. The final game has one building, silent NPCs, and ambient sound I found at 4 AM.

Every cut improved the result. The limitations forced clarity. When you can't add more, you refine what remains.

Tools serve intention, not the reverse.

I entered the jam barely knowing Unreal Engine Blueprints. I left having built a complete game loop, AI behavior, dynamic post-processing, and UI systems—all through visual scripting.

The tool didn't make the game good or bad. Understanding what I wanted to create made the tool useful.

Completion creates momentum.

A finished project, regardless of quality, produces something an unfinished project never can: proof that you can finish.

WORN is imperfect. I see the rough edges every time I look at it. But it's done. That fact matters more than any individual flaw.

The best work often emerges from discomfort.

I was not qualified to make this game. I learned essential systems in real-time, debugged problems I didn't understand, and made decisions without enough information.

The discomfort was the point. Growth doesn't happen inside competence. It happens at the edges.

Final Thoughts

Game jams compress an entire creative cycle into a single weekend. The pressure reveals patterns—both productive and destructive—that longer timelines obscure.

I learned how I work under constraint. I learned what I prioritize when time forces choices. I learned that my instinct to add "one more thing" is reliable and reliably dangerous. Most importantly, I learned that starting scared doesn't predict finishing failed.

If you're considering a game jam—or any creative challenge that feels beyond your current ability—I offer this:

The gap between "not ready" and "ready" is smaller than it appears. Often, the only way to close it is to begin before you're certain you can finish.

You might surprise yourself!

Project Details

Title: WORN

Genre: Psychological Horror

Engine: Unreal Engine 5.4

Development Time: 48 hours

Team Size: Solo

Event: Global Game Jam 2026, Lithuania

Play WORN: [Global Game Jam Link] | [Itch.io Link]

Connect: [LinkedIn]