Why There's No Devlog Yet

There's a devlog sitting in my drafts. It's been there for a while.

It would have been easy to publish. I've got architecture diagrams, screenshots of pipelines, notes on nearly every decision I've made so far. Plenty of material. Enough to post something that looks like progress.

That's exactly why I haven't.

I told a few of you that devlogs were coming, and then they didn't come. You deserve a straight answer for the delay, so here it is.

The easiest content I could make right now is narration. Here's what I'm building. Here's the diagram. Here's the grand plan. It would look productive, and it would be hollow. A diagram isn't a working system. A plan isn't proof. A roadmap is just a list of promises you haven't broken yet.

I've watched too many projects document themselves into a corner. Months of polished devlogs, clean thumbnails, a roadmap that quietly slips quarter after quarter, and underneath all of it, a thing that never actually ran. The content becomes the real product. The audience falls in love with the story, and the story slowly replaces the work it was supposed to be about. I don't want to build an audience for something that doesn't exist. If I'm going to show my work, the work has to exist first.

There's a reason this is taking long enough to need an explanation at all. Early on I made a decision most people building a game would call insane: I'm building almost the entire stack underneath it myself. The servers. The deployment pipeline. The thing that packages a build and hands it to a player. The system that will eventually spin up a match and tear it back down. The unglamorous infrastructure that most indie devs rent, outsource, or paper over until it becomes an emergency.

I did that on purpose. Lean costs, full control, and, maybe most importantly, nothing in the critical path that I don't actually understand. The tradeoff is that "making a game" has mostly looked like building everything that isn't the game. For a long stretch there was genuinely nothing to show that wouldn't have just been me pointing at boxes and arrows.

I've also already run the version of this where you spend real money every month keeping infrastructure alive for an audience that isn't there yet. I sunset it. I'm not in a hurry to repeat the part where the cloud bill shows up before the users do.

So I drew a line for myself. I call it v0.

v0 isn't the game. It isn't pretty, and nobody's going to see it. It's the smallest version of this whole thing where the entire loop works end to end, on the same machinery I'll use for real, not a demo rigged to look good for thirty seconds of footage.

And here's the part that's hardest to keep quiet about: some of it already works. Not long ago I took my actual game (the real build, not a mockup), pushed it through my own content pipeline, and then installed and launched it straight out of my own launcher. No storefront, no third party, my stack from one end to the other. Every file signed, because the moment you ship software to someone else's computer, "just trust me" stops being an acceptable answer. That was a genuinely good day. It would have made a great devlog.

But it's only half the loop.

The other half is the part that actually intimidates me, which is how I know it's the right bar to set. A server has to spin up on real infrastructure. A player has to connect to it. A match has to run. And then, the part everyone forgets, the server has to come down cleanly when it's over. No leaks. No orphaned machines quietly billing me at three in the morning for a match that ended hours ago. That's the full loop: publish the game, place it on a server, play it, and tear it all back down without anyone babysitting it.

I'm doing that the cheap way first, deliberately. I'm proving the whole thing locally, standing the system up on hardware I already own, before I lease a single box from anyone. I would much rather find out my fleet logic is wrong on a machine that's already paid for than on one that's charging me by the hour to be wrong. v0 is the moment I get to stop saying "this should work" and start saying "this works." Until I clear it, there's nothing here worth documenting that isn't just hype with a nice font.

Building the half that already works taught me the thing I most needed to learn. There's a canyon between "it compiles," "it ran on my machine," and "it ran on a machine that wasn't mine." Each one is a different claim, and only the last one really counts. Most devlogs get written from the first wall of that canyon, pointing at the far side as if they'd already crossed it. I'd rather not narrate the crossing until I'm standing on the other end.

In the first thing I wrote on this site, I said I wanted to show my work as someone a few steps into the same road, not as someone who has it all figured out. I meant it. But a road you can't actually walk on isn't a road, it's a sketch. Anyone can narrate a map they've never tested. I'd rather walk the first stretch myself, prove it holds, and then tell you exactly how I did it.

Once v0 is proven, everything opens up. That's when the devlogs start for real, not as marketing, but as a running record of building toward v1 on a foundation I already trust.

And v1 is bigger than my game. The entire reason I'm building the boring parts by hand (the servers, the pipelines, the matchmaking) was never to run one project on top of them. It's to get to a point where other developers can deploy and test their own games on the same platform. People who write code for a living and have one idea they can't stop thinking about, hitting the exact walls I'm hitting right now. My game just happens to be the first tenant.

That's also why the bar sits where it does. If it's only me, a bug is an annoyance. The day someone else trusts this platform with their own project, that same bug becomes a broken promise. I'm not going to ask anyone to put their weight on a foundation I haven't already stood on with my own.

I'm not going to hand you a date. I've got a day job, and I'd rather stay quiet and deliver than throw out a timeline just to feel accountable to strangers on the internet. What I'll tell you is that I'm close enough to v0 now to see it clearly. Close enough that writing this felt more honest than publishing the devlog would have.

When I clear it, you'll know. And the next thing you hear from me is going to come from solid ground.