Fanaelialae
Legend
In general, if there is something that might be reasonably assumed but that they didn't say, I will either assume they did so or prompt the player myself. Doing otherwise is, IMO, 'gotcha' DMing which is not a style of game that my table enjoys. It's like saying that a PC dies of renal failure because the player didn't explicitly state that he would periodically take bathroom breaks. Or like a player forgetting to state that his character picks up his cherished holy avenger, which he dropped to draw his long bow, and therefore leaving behind one of his character's most precious items (which is right there in plain sight of the entire party, but might be overlooked in the imaginations of your players).
I'm sure it works for some tables, but I view it as a very antagonistic style of DMing, so it's definitely something I think everyone at the table needs to agree to beforehand.
There was a time when my group had a DM who ran that way. IMO, never again. It was the least fun I've ever had playing D&D.
It's reasonable to assume that if you are charging through a cloud of gas that you know or suspect to be poisonous (Cloudkill is described as yellowish green vapors) then you are holding your breath unless otherwise stated.
That said, Cloudkill says it functions on targets even if they're holding their breath or not breathing, so a quick look at the spell description would have rendered this argument moot.
It's also reasonable to assume that if the PCs took pains to camp in a difficult to reach location, they pulled the rope up behind them. Now, if there are reasons to leave the rope down (the rogue is still downstairs doing a bit of scouting) then, again, it's best to simply ask.
Requiring the players to state things that can be reasonably assumed is fine if everyone involved wants to play that style of game.
Otherwise, it is antagonistic and mires the game in nonsensical tedium, as the players learn to specify all manner of meaningless minutia lest the DM pull a 'gotcha' on them.
I'm sure it works for some tables, but I view it as a very antagonistic style of DMing, so it's definitely something I think everyone at the table needs to agree to beforehand.
There was a time when my group had a DM who ran that way. IMO, never again. It was the least fun I've ever had playing D&D.
So last session me and one of my players got into a minor argument a couple of times about what his character was doing.For the purpose of this post we'll call him Morath (his PC's name). I want the your guy's opinion on whether I made the right calls in the specific situations and also on how other DM's handle the idea of what actions by a PC don't need to be stated . Skip to the Bold if you want to just get to the general question and skip the specifics scenarios.
1) Morath rushed through a cloudkill spell to reach the rest of the party on the other side. I had him roll his con save and another player asked if he holding your breath when going through the cloud allowed you to make the save with advantage. Morath says that of course he was holding his breath when he ran through the cloudkill. I inform him that he would have had to state that before running into the cloud and Morath argues that he thought it went without saying that he did so.
On this issue my thinking is that if you want to try for some sort of mechanical advantage, such as getting advantage on a save, you HAVE to tell me your doing something. I'm not going to assume it.
Also I never actually made a call during the session, since I established that he wasn't holding his breath, but I would have ruled that holding your breath does nothing to help. It's more an issue of the PC's having to state they are doing any action they are hoping to grant them a mechanical advantage, whether or not the action actually helps at all.
It's reasonable to assume that if you are charging through a cloud of gas that you know or suspect to be poisonous (Cloudkill is described as yellowish green vapors) then you are holding your breath unless otherwise stated.
That said, Cloudkill says it functions on targets even if they're holding their breath or not breathing, so a quick look at the spell description would have rendered this argument moot.
2)Morath and another PC are sleeping inside of a statue that has stairs leading to the top. The stairs are collapsed partway up and the only way to the top of the statue is by climbing a rope. The next morning the party has left the area, comes back, and finds a wizard at the top of the statue with the rope curled around his feet. When talking about it Morath claims that of course he would have pulled the rope up after him when climbing the tower, he thought it didn't need to be stated that he would do so. I again said that he would have had to of told me he did so the night before when they were making the camp.
On this issue my thinking is that I'm not going to make assumptions about the parties preparations that they don't state. During the previous scenario the other half of the party described how the tied off doors to secure their camp and what watch order they took. Morath and his companion described how they climbed the tower and set up a guardian of faith at the top of the tower. If they didn't also state "we also pull up the rope after us" then the rope is still hanging down.
So my general style of DMing, as you may have guessed by my answers above, is that if you don't tell me about something it didn't happen. I try and be fair about this. If the party makes a plan I will generally ask if that is all they are doing and then repeat the plan back to them, to clear up any misunderstandings. If the party says something like "we make camp for the night" I don't just assume they fall over asleep on the spot, I'll prod them about watch order and any defenses they want to erect.
My question to you playground is what do you think it is reasonable to just assume a PC is doing even if they don't state it? in a dungeon are they closing doors behind them? Are they collecting rope used in exploring? If they sleep in a dungeon is it assumed the door is barricaded? If they sleep in an inn is it assumed the door is locked? Where do you draw the line?
P.S. if curious my answer to the above is no, no, no, and yes.
It's also reasonable to assume that if the PCs took pains to camp in a difficult to reach location, they pulled the rope up behind them. Now, if there are reasons to leave the rope down (the rogue is still downstairs doing a bit of scouting) then, again, it's best to simply ask.
Requiring the players to state things that can be reasonably assumed is fine if everyone involved wants to play that style of game.
Otherwise, it is antagonistic and mires the game in nonsensical tedium, as the players learn to specify all manner of meaningless minutia lest the DM pull a 'gotcha' on them.