|Picture of Lennithon|
The Adult Blue Dragon Lennithon, as far as I can tell, has no pre-existing history in the realms. Here is everything we know about him:
- He is not an enthusiastic participant in the raid.
- He doesn't want to fight adventurers.
This encounter showcases bounded accuracy and enemies that are much more powerful than you.
There's a wall, see? The players don't know what's in the module. When they reach this encounter, they will assume that if they engage the creature, they will all die. The only way to not think that is to have some sort of meta-knowledge about the game. So what's this choice like as a player, hm?
Either run and hide or die.
So that's frustrating.
The solution, or at least the only one I can see, is to be forthright about the situation.
"The (insert dramatic description of) dragon is (insert graphic depiction of) murdering guards on the parapets. You feel waves of fear come over you (make DC 17 wisdom saves). Those of you not terrified can act. Watching, you can tell that the dragon is only reluctantly attacking the towers and can likely be driven off with a good hit or two, unwilling to risk his own skin. However, any successful attack that doesn't drive him off is likely to focus his quite lethal attention on you. Driving him off now would save hundreds of lives and the surviving guards would make life that much more difficult for the cultists. What do you want to do?"Then track 1 minute of real world time, having a round pass if no one takes an action, with the dragon killing more guards.
Providing a bonus for capturing cultists (and only cultists) means that there's a choice between more difficult movement for a reward. For new players, this also teaches them that they can choose to knock out opponents with melee attacks instead of killing them.
The information on other ways to leave the keep is also buried here, inside the text.
Charisma (Performance)? Well, whatever.
This encounter straddles the line of character skill and player skill on the wrong side. If the player's take the time to stop and look, they still are likely to fail to determine that it's a trap.
In addition to the "go save the mill" speech given, I'd give clues in the description of the scene. "A cultist looks around into the night waving his torch back and forth, cackling evilly as Dragon-Dogs stack kindling up against the door. He moves towards it for a second, and then back, waving his torch around! What do you do?"
Then, I'd grant the mechanical check in either case. The DC should be higher if they don't stop to look or ask questions (DC 20). Being suspicious and stopping to look should either grant advantage (at DC 15) or lower the DC (to 10). The players can ask questions about the description until they make up their own mind to attack. Obviously they won't set it on fire with the force inside, so after enough time it should become obvious it's a trap with no roll needed.
No complaints. No changes necessary. Well done.
I'd like to call out the "let the players make their own plan" and "pressure the players based on your group makeup" as excellent techniques and it's awesome to see them in published materials.
I once had a player complain when I held up a timer for some time limited event, crying out "It's not fair!" This is something players in a pressure situation who don't deal well with pressure (or who might think they can remove the pressure through argument or discussions) might do. I said to that player "You are absolutely right, it isn't fair." and then just waited. Acknowledging when players complain that things aren't going their way goes a long way to having them accept that sometimes bad things happen in games.
You know, I have no real major problem with this section, except for this statement:
"If by some mischance Cyanwrath is killed or captured, his place in the dragon hatchery is taken by another half-dragon."No. No it isn't.
Other quibbles have to do with presentation. Do characters know how much more powerful than them this creature is? Is that presented in a way that the player can get that information? The answer is no. It needs to be.
The whole "fair fight" thing is also ridiculous. The replacement of "I'll execute one townsperson I've got every minute until someone comes to face me or I run out of townspeople" is a much better solution. Tell them he wants to fight a single opponent. If they all come out, let them all fight the 15 dragon dogs, Cyanwrath, and a half dozen cultists. Let them fight him one on one. Let them try to cheat and plan. Let them do whatever they want.
If they do kill him, then they should kill him. He won't be in episode 3 or any other episode, because he will be a corpse.
Why have Cyanwrath kill (or almost kill) a party member at all?
The idea is to take something from the players. Not just have something bad for them as characters, but for them to become invested as players in seeing this person go down.
In Phandelver, I achieved conversion when I had Yeemick jump down and say "You'll never catch me!". Suddenly my players were very interested in catching Yeemick. Not their characters—the players.
They weren't bothered or as invested in his unsurprising and ultimately inevitable betrayal. But telling them they couldn't catch him, had the 9 hit point party wizard jump down 20' off a ledge (taking 2d6 damage) and run outside to hunt him down by himself, alone.
The problem is that what's printed in the module doesn't cause that. Just fighting a dude you can't beat and one that knocks you down doesn't do that. It's the way in which he kills you that's important.
If you fight this dude, he will kill you. If you don't he will kill these women and children. This is Sophie's choice—it just makes players feel bad and is unfun.
However, if he toys with the players and they see the encounter is winnable (even if ridiculously difficult) and he taunts them and gets away with it, then he'll be hated by the players.
This isn't a mechanical thing. It's a personal thing, which means that it requires the Dungeon Master to be skilled at pushing buttons. You can't just write this encounter without calling this out, because a bunch of the people running it are going to make it frustrating for the players, and not something that makes them, personally, as players, hate your opponent.
Hack & Slash
Follow, Google +, Newsletter, Support
Hack & Slash
Follow, Google +, Newsletter, Support