Here’s the honest picture of where Grimmloch stands today, read through the three layers from the last two posts: the server that runs the world, the client you play it through, and the content and tools that fill the world in.
One thing to hold onto as you read, because it makes everything else make sense. A gap in the first two layers means something is genuinely unfinished. A gap in the third layer just means the world is young. The UO community learned this the hard way: the server and the client each have a real “finished enough” point, but the content layer never does. A living world can always grow, and the busiest old shards never once considered it done.
So as you go through this, the question that matters isn’t “is there a gap.” It’s “which layer is the gap in.”
This is the layer that took the UO community years, and the one most projects never actually finished. We have it.
The server speaks a real language to the client. It holds one authoritative version of the world that everyone shares. It remembers everything through restarts. It verifies who you are and protects your characters. It runs a genuine turn-based combat engine. And it drives its NPCs with real autonomy: real emotions, real conversation, and an astrological personality sitting behind each one.
In UO terms, the hard, invisible engineering, the part that kills most projects, is done.
Two honest caveats, and you should hear them plainly. The server does not yet stop a cheating client from doing things it shouldn’t, like walking through a wall. And it has never been tested under a real crowd. That second one is a big reason we’re running this playtest at all.
The machinery you actually stand on is solid. Windows dock and float. The connection recovers on its own when it drops. The world renders, with day and night and water. Character creation works from start to finish. Chat, the roleplay log, and the combat display are all genuinely live.
What isn’t finished is a set of screens that look real but don’t have anything behind them yet. The inventory, direct messages, roleplay partners, and a few others are storefront windows waiting for their back room. You’ll see them, and right now they’re mostly for show.
And there’s no game sound yet. None. That’s coming.
This is where Grimmloch is young, and by the UO timeline, this is exactly where a project our age should be.
The tools to build the world are real and strong. And one town, Bukenstrand, has a deeply authored cast of forty-seven characters with real history and personality. But the world beyond that is mostly empty for now: one demo map, no roads laid down yet, and the wider world still to come.
This is the layer that, if the game succeeds, never stops being worked on. It’s supposed to be barely begun right now.
Almost nothing here is broken. The gaps are two friendly kinds.
Some are engines that are fully built and just waiting to be wired to a screen or fed their content. The system that runs locations, for example, is finished and will light up the moment the world is populated. Nothing to fix there, just connecting and filling.
The rest is tuning and content, which is the work that never ends and is meant to never end.
The one-line version: the hard part, the part that usually kills projects like this, is done. What’s left is dressing the world and making it feel good, and that’s the fun part that lasts for years. That’s where you come in.
Here’s the part I mean most. A lot of what’s left is the kind of work a community can actually shape, and I want you in it. The screens that still need dressing, the way the interface feels in your hands, the advanced systems we’re still designing, the political layer, the deeper world, the pieces we’ve said out loud aren’t finished yet, all of that is better when the people who’ll live in it help build it.
This is why I run Grimmloch the way the old shards were run. Not a studio handing you a finished box, but a world being made with the people who love it. So when we open up a design question, or ask how a screen should work, or put an unfinished system in front of you, that’s not us running out of answers. That’s the invitation. I’d rather build this with you than for you.