Skip to content
Crowd Control
← Devlog

Starting Crowd Control

· 2 min read
meta netngine

I’ve loved videogames for as long as I can remember, and for just as long I’ve wanted to make one. For years that stayed a someday-dream — the kind that never really moves. Not enough time, not always enough motivation, and every road into game development seemed to have one more wall to climb.

So this is me starting for real, in public, and writing it down as I go.

Why an engine first, and not a game

The honest answer is that I wanted to understand how real-time multiplayer actually works, all the way down, rather than gluing together someone else’s middleware and hoping. Multiplayer is the part of game development I find most interesting and most intimidating: prediction, reconciliation, interest management, the way a server and a dozen clients disagree about the present and have to be talked back into agreement.

So the centerpiece is NetNgine, a real-time multiplayer engine written from scratch in C# (.NET 8), with a Godot client. The rule I set myself is simple: the engine core never knows the rules of the game on top of it. Sync, interest management, persistence and sharding are each a swappable piece behind a small, fixed contract. A new game plugs in as a module and the engine doesn’t change.

That constraint is doing a lot of work. It keeps the core honest, and it means every feature has to prove it belongs by being useful to more than one game.

What this site is

Not a store, not a studio front. It’s a place to point people — from GitHub, from a link in a chat — so they can see what this is in a few seconds, and follow along if they want to. The devlog is the living part. Everything else is stable.

It’s free and non-commercial. One developer, building in the open, with a lot of help from working alongside AI. I’m not going to pretend otherwise: the tool is the difference between a dream that stalls and one that actually moves. But the direction and the understanding are mine — I’m learning every part of what I build.

Next post: the modular core, and how a handful of deliberately boring demos keep it honest.