Bad Omens and Good Omens

We've just published a new table! Bad Omens. 

Not so much events as real creepy shit that happens BEFORE the event. Eery silences and ladders falling on black cats. That sort of thing. Looking forward to start tossing these into my campaign just to make my players fear what *might* be coming next.

As for what's coming next for Glumdark: BIG STUFF!

You haven't heard as much from me (CTRO) recently, and partly that's because I've been heads-down on a total rewrite of Glumdark. We had originally written it as a node.js app in a flurry of programming to get an MVP out the door.

But I had some tools in mind that I really wanted to build. And they would have made our already-spaghetti code pretty unmaintainable. Or just gnarly to work with.

So I went ahead and rewrote Glumdark with a Rails backend and a React frontend. Ruby/Rails is sort of my first language and I've always hated React. But I figured if I wrote my own web application in React soup-to-nuts, maybe I'd learn to love it.

I didn't. I still super hate React. So I rewrote the whole frontend AGAIN. This time I just used Rails view rendering and Stimulus for the Javascript interaction. Now it is much, much nicer to work on.

BUT WHAT WAS IT ALL FOR!?

Well, I'm really interested in doing more app-type stuff. A dungeon generator, a mob generator, an npc generator, even a hero generator. Ideally we can continue to make this stuff rules-agnostic. But we've also been discussing ways of translating between 5e / Mork Borg / Pathfinder / etc.

For now, the production Glumdark site is still the node.js app. But we're hoping to launch the new app in the next week or so. I want to fix some longstanding bugs in the process, give it a quick aesthetic overhaul and also finish polishing our first new NPC generator.

Here's a little preview!

Once we launch this, I'll put together a little technical overview of the scripting language I developed for it. Some may find it interesting, I hope! It's been a lot of fun to put together.