I’m usually the Director, so I was excited when a player asked to run this for the Group. It gave me a chance to see Dark Heart of the Wood from the player side, I also read through it afterwards.

The threxyls are fun! The stat blocks are solid and fit the theme well.

The combat encounters are also well designed, with a nice mix of brute force and clever solutions. For example, there’s a fight in an overgrown chapel where an ambusher uses darkness and low visibility to their advantage.

Opening the windows, removing that darkness, completely shifts the encounter and levels the playing field. I like this kind of design a lot, encounters where players can either push through or try to find smarter solutions, without being forced into one approach.

Overall, the group had a good time with it.

However, I don’t think it’s as easy to run as it should be, and that’s an issue.

1 - Crucial information is implied, not stated

There are several places where it feels like the writer assumes the Director will just fill in the gaps. In practice, that means extra prep.

For example, the adventure says the village has no food left, so players can’t take a Respite unless they brought supplies. But supplies aren’t tracked in Draw Steel, so this reads more like a vague way of saying “no resting during the adventure” without actually stating it clearly.

The biggest issue is the final fight.

The map has strong verticality that clearly gives the dragon an advantage. There are teleporters leading to a corrupted source of Green that can be cleansed, forcing the dragon down for a final stand.

That seems like the intended structure, but it’s never actually stated. The adventure just presents the map elements, the teleporters, the well, and the dragon, and leaves the Director to assemble how it all connects.

That’s a lot of interpretation for a climactic encounter.

2 - The structure is more restrictive than it needs to be

At one point, progression is explicitly blocked unless players complete all prior scenes and retrieve a specific item.

I’ve run plenty of linear adventures, so structure itself isn’t the problem. The issue is that these mandatory scenes mostly function as lore delivery, not meaningful decision points.

It feels like the same structure could work without forcing every step, and the information could just as easily be delivered organically or in a post-adventure debrief.

As written, it adds rigidity without adding much gameplay value.

Verdict

The production quality is what you’d expect from an MCDM product, and there’s a good adventure in here.

But I don’t think it’s a $20 “run it out of the box” one-shot. I’d happily pay that if I could drop it on the table and go. But as written, it requires enough interpretation and reconstruction that it stops being plug-and-play.

At that point, the price is hard to justify.