The Dragon's Fire: Reflections on a Wonderful Failure

 

Welcome back! Today I go over some of my thoughts on the latest Crescendo epic.

Games have design goals. They're meant to provide an experience, which keeps people coming back because they're having fun! The goal of Crescendo is to replicate the feeling of reading Wolfe, to take his principles and put them in a TTRPG space. Adaptation does not mean trying to replicate the original exactly, but to adapt its principles into a different medium.

So, on the one hand, Crescendo is a ton of fun. People are coming back and having a really meaningful time. Heroes are a wonderfully designed character type, and literally nothing in the TTRPG space exists that does what Heroes in Crescendo does. That's a fact. Heroes are successful. They successfully draw an arc found in Wolfe extremely well.

However, that doesn't mean Crescendo is successful in achieving the goal "replicating Wolfe's principles". And that is... not what Crescendo does. Not yet.

Let me try to explain. Let me try to show you what's wrong.

At the beginning of The Dragon's Fire, I introduced a girl-vampire (as in, a vampire who was turned when she was a girl), called The Bride. Now, I had a backstory for The Bride. She was a child who was brainwashed into thinking she loved Eous, The Big Bad. So when he turned her, as an 11 year old child, she went willingly. I didn't come up with more than that, just enough to know this NPC was evil, and liked it... and was seemingly naive about it in a way that should have been chilling.

The Bride showed up four times in thirty plus sessions of gameplay.

Four.

Now, to be clear, this wasn't exactly a problem, per se. The game does a good job of shaking up the spotlight around the players pretty thoroughly. So there was always something interesting going on, it just wasn't... well.. any of the villains, the monsters, of the setting. There were hints of what could have been depth, but nobody cared when Raphael took the Bride down, and when the original dragon vanished, nobody looked. This was because, in order to capture Wolfe's startling breadth of vision in a game, I had to put a completely different kind of workload on the Weaver, who is not a GM. As I have repeatedly stated. 

This is a problem for a few reasons:

1. Wolfe's stories manage to squeeze a lot of depth into each and every character that ever hits the page. They're not "NPCs", but protagonists in a stories that you simply can't linger on. The current set up does not support that feeling.

2. Without that depth, it is hard for players to fully invest in the setting itself. There needs to be some parts of the world that push back harder than others, in a way that preserves player autonomy.

3. Because of the chaos, the Weaver cannot focus on NPCs to develop.

4. The game is about challenging Beliefs and then holding the players responsible to the Myth. That's already a lot.

In short, I think this was the best campaign of Crescendo I have ever run, one of my best in general, and it was somewhat in spite of the game I made.

That.. doesn't make me feel good. My players were awesome, I was absolutely on fire, and Crescendo carried us pretty far... and could have carried us a lot farther.

Fortunately, there's a pretty simple fix.

Whatever you want to give depth to, you give to a player. 

GMs, who aren't having to work with half as many left-field "WTF" moments as a Crescendo Weaver, benefit incredibly from this principle (see the book on the right)... and that's going to go  triple for Weavers.

Fortunately, that's going to be really easy to mine out of Wolfe, because he gets into the psychology of monsters, a lot: they're simply creatures who don't want any change to affect them. They cannot adapt in a way that others can work with, because their very nature makes them unable to adapt in a way that's friendly to others.

Wolfe's stories do not skimp on monsters who have very deep, very complicated, inner lives... that are utterly unable to do anything other than look to their own interests. Unlike Heroes, whose development can go anywhere, Monsters can only be interested in themselves... and have an infinity of ways of thinking about their own needs.

Someone's going to go "Just stop developing already! Move on!"

No.

Let's get this clear, for anyone who's reading this and who cares. This is my hobby. This is for fun. Anyone who thinks I am trying to develop a commercial product needs to rethink their assumptions.

I am not.

Yeah, sure, there's a PDF up on DriveThruRPG. You can go buy it for five bucks. It would be nice if you did. But I also just drop the PDF on people for free, because this is what I do for fun. If it makes money, cool. If it doesn't... okay? I want this damn game to do Wolfe. And it's gonna do it. 

Because the stuff this game does right deserves to be supported. I think about King Melny the Dragonslayer, Alistair the Serpentbane, and Raphael the Hordefighter... and my goodness that legitimately makes my heart hurt, in the best way possible. These huge legends and the things they did that literally nobody will know about. The apology of King Melny, where he admitted that his evil ways were born of fear and how he wanted to be better... and how that cost him Junior. Like, that hit me really hard. Alistair trying to understand how Natasha was still with him, actually with him, even after death, and failing to do so, and having to accept that he would never fully get it. Raphael holding his friend after a good and long life and being the last thing he ever saw. 

That shit means something to me. It lives in me, in the best way possible. Those memories are the reason I run games like this. Like, sure, I want to have fun too, but... there's something so human in it, and I need that. I think people in  general need that: unplanned humanity.

My priority is that experience, at my table. And Monsters will make that stronger. There could have been the moment where The Bride doubled down on her evil, in a way that shows she literally can't think of another way to do things, eliciting pity and horror. There could have been the moment where the original dragon tried to escape her tormentors and failed. That wouldn't have taken away from the Dragonslayer, Serpentbane, and Hordefighter. Quite the opposite. It would have made those moments even better, because the pity and horror of The Bride would have made the good moment sharper.

But that requires adding things to the game, and that's fine. The design shall continue until morale improves!

So yeah. This was a gorgeous failure. Let's make the next one work better. ONWARDS.

It is here that I leave you. If I do not see you next time, I do not blame you. It is no easy road.