There’s a slightly strange part of starting a game studio where you’re doing a tremendous amount of work while publicly having almost nothing to show for it.
That’s roughly where we are.
Project 01 is real.
It’s in active development.
And we’re deliberately not announcing it yet.
Why stay quiet?
Mostly because we want the game to have enough of an identity before we ask anyone else to care about it.
Early development changes constantly.
You can spend several days building a feature, play with it for ten minutes, and realize the entire approach was wrong.
You can build an environment that technically contains everything it needs and still discover that it doesn’t feel right.
You can write systems that work perfectly in isolation and immediately fall apart once they have to interact with the rest of the game.
That’s useful work.
It just isn’t necessarily useful marketing material.
We’d rather make those decisions while we still have the freedom to make them.
Foundations first
A lot of our current work isn’t flashy.
It’s the stuff everything else eventually depends on.
We’re spending time thinking about questions like:
- How should interacting with the world feel?
- How much information should the game explain?
- How much should the player discover themselves?
- Which systems need to be flexible enough to support later ideas?
- What should feel physical instead of abstract?
- How do we keep complexity understandable?
- What visual details actually matter?
Those aren’t features you can easily summarize with a flashy GIF.
But they affect almost everything that comes afterward.
The dangerous version of “temporary”
One thing we’re trying to avoid is building too much around assumptions we already know are temporary.
Game development produces a lot of:
We’ll fix that later.
Sometimes that’s completely reasonable.
Sometimes six months later you’ve built fourteen other systems on top of the thing you were definitely going to fix later.
We’re trying to be deliberate about which shortcuts are actually temporary and which ones quietly become architecture.
That doesn’t mean we’re attempting to engineer the perfect system before moving on.
That would be another great way to never finish anything.
It means trying to understand which decisions are cheap to change later and which ones aren’t.
Finding the game
There’s another reason we’re staying quiet.
We’re still learning things about the game ourselves.
Not the broad idea.
The smaller things.
The things that determine whether interacting with it for an hour is actually enjoyable.
How fast should something happen?
How much control should the player have?
When should the game assist you?
When should it stay out of your way?
How much detail makes something interesting before that detail becomes noise?
Those answers generally don’t come from design documents.
They come from building something, using it, and noticing what feels wrong.
Then doing it again.
When do we show it?
When there’s something worth showing.
That’s the incredibly sophisticated marketing strategy.
We’re not interested in announcing a logo for a game that barely exists, spending the next year explaining that we’re “still cooking,” and then slowly discovering that half of what we originally announced no longer represents the game.
At the same time, we didn’t want to disappear completely until reveal day.
We’re building more than a game right now. We’re also building Syscall Studios.
So while Project 01 stays under wraps, we still want to start putting ourselves out there. We want people to get to know how we think, how we work, what we care about, and what kind of studio we’re trying to become.
Ideally, by the time you get to know our first game, you’ll already know a little bit about us.
That’s part of what this Dev Log is for.
Eventually Project 01 will stop being [ CLASSIFIED ].
For now, the work continues.