Skip Navigation
50 comments
  • DM 1: "We're going to have a magical just-so adventure and everything will be on rails! I've got a bunch of art I'm going to show you and I expect everyone to do voices and play in whatever vague medieval fantasy pastiche passes for In Character. I want everyone to have a good time, but also cry when my NPC gives a twenty minute monologue. This game is my entire personality."

    DM 2: "Here's a stack of character sheets. I found a dungeon in a magazine called The Infinite Rectal Immolator that looks cool as hell. You have a 25 point buy and three magic weapons of less than 15k gp each. Just ordered a stack of pizzas and a five gallon jug of Mountain Dew. Let's see who makes it through. If we get bored, I've also got the new Halo game on XBox."

  • I'm not trying to kill my party, but I also won't stop them from being stupid and getting themselves killed. I design my campaigns like an open world video game. Everything is going on and just reacts to the players. They can find bits of information about things and then act on it, doing whatever they want until they start finding clues about the big bad because I like to try and make it more natural with the characters just existing in the world and not the stereotypical call for adventure a lot of modules and stuff do. But this also means balancing out the world by having the encounter zones being somewhat static. Over here shit is low level, but over there stuff is high level. But like, they will have clues. If they hear the rumors of a Balrog at level 3 and want to go fight it, that's on them.

  • I am (was to be more correct) more in between

    • You can be the first type, and some players will still see you as the second.

      Like, they attack the king's castle for no reason and are upset the guards don't lie down and die, then refuse to surrender when things are entirely hopeless and they're offered mercy. Such a mean DM!

      • I'm a big fan of the "wisdom " check before players do something that seems, to me, completely stupid. Like, hey, before you set out to storm the castle, roll your highest knowledge skill.

        Tactics, architecture, history, etc, all good. But any success on any skill (or even, literally, Wisdom if nothing else) gets you a little hint that this is a terrible idea.

        "OK well, as a Baker, you understand that the huge wagon pulling 500 loaves of bread into the castle means there must be an enormous amount of guards. Since you got a natural 20 on your Cooking check, you can estimate the number precisely to around 150. Even if they weild the baguettes as weapons, you are certain they will defeat you."

        And then, most parties I've played with will then begin formulating their plan to sneak in on the bread wagon, which is a much funnier story. Or they'll complain that they meant the druid should cause a storm to distract the guards or something like that. It's kind of amazing how often these bad plans arise from a miscommunication.

50 comments