Dateline – Storm Point

***SPOILER ALERT***

I’m running Tomb of Horrors for this leg of the Storm Point campaign. You may not want to read on if you’re playing the game yourself.

***SPOILER ALERT***

The last Storm Point session was pretty much a wash. We hadn’t played in almost two months, summer scheduling being what it is, and spent most of the evening socializing rather than playing. We even had to stop the combat partway through when we wrapped for the evening.

The group made it through the secret door and into another oddly-shaped room. They entered carefully, mindful of traps, and everything went dark for a second. When the lights came back up, there was a duplicate of each of the characters standing near them. And, of course, the duplicates attacked.

The fight is tough. The monsters that are being used as the duplicates ((I’m not going to say what they are, yet, because the fight is ongoing, and at least three of my players read my blog.)) are well-chosen, and quite effective, even when I forget one of the powers. The mechanics for seeing if players attack their intended target or an ally have caused a couple of bad moments for the group ((And if they didn’t know that this adventure was The Tomb of Horrors, they would have been calling me out for such a dick move. Because they know what the adventure is, they take the boning almost in good humour.)), but I’ve been a little less stringent with that than I might, because it is a nasty thing to do to the players.

But at the end of the evening, we’d only got through three rounds of combat, and none of the enemy had been dropped, yet. I took a picture of the battlemap, and we called it a night.

I’m hoping for one more session before my Ireland trip, which should finish this encounter. After that, I expect one or two more sessions to wrap up the adventure. Then it’s on to the city-state of Belys.

Tagged , , . Bookmark the permalink.

One Response to Dateline – Storm Point

  1. Milo says:

    A grueling mashup thus far.

Leave a Reply

Your email address will not be published.