Ytdyklly

(Some of) my players are trying to role play in a meta-gaming sort of way.

For instance, I had an array of weapons in a dungeon, and when they took them, they had to make a Wisdom saving throw, else they feel ridiculously guilty and take 1d4 psychic damage. A few of the players tried continuously take stuff down, even though they had failed the Wis save. I tried to discourage them from this a few times, but they seemed to meta-game in the sense that: "Oh boy, my level 3 character has 21 hit points left. I'll take another one."

I was trying to model an episode of Critical Role I'd seen where a character had to make a wisdom saving throw when he killed someone with fire. He failed, and the DM described how he kinda felt guilty, and as a good RPer, the character spent the rest of the day somewhat depressed and guilty, but everyone at the table looked like they were enjoying it. But my players were willingly hurting themselves for a little more loot. I was trying to give them the cues that they should feel guilty, drop the longsword and walk away, but they seem to think about it in a different way.

To clarify, the guilt is magically induced.

Am I, as a DM, allowed to tell the players what they do when they are affected in this way?
If not, how am I supposed to imply that they should drop the weapon and walk away? And in a different scenario, how am I supposed to imply the harshness/the to what effect of the magic?
Are there any compromises between the two?

Thanks.

When you dictate emotions to a player, dictate mechanical effects of those emotions.

Assuming good faith here - your players are not deliberately metagaming or ignoring your narration. They may have just come away with the impression that 1d4 psychic damage is the full and complete effect of the guilt their characters felt.

If you want to compel an action from them, take control away from them. Make it clear where the effects of the spell end and their agency begins. D&D has a lot of mechanics which punish players with heavy things (like dead characters) if they fail an encounter. This creates an expectation that player characters will, most of the time, cooperate and do what is best for the team.

In that situation, instead of giving players vague directions and expecting them to then choose to act in a way that is against what they perceive to be the party's best interest, you should make it clear what actions they are allowed to take or not take, and then leave them free to roleplay their character as they like in the space that remains.

When they fail the wisdom save, you say:

You are overwhelmed by inexplicable guilt. You put the weapon back on the rack, and back out of the room, and resolve not to touch the weapons again. You take 1d4 psychic damage from the lingering guilt even afterward.

Then, if they try to take the weapons again, do not let them repeat their save, instead, re-iterate the effect of the previous failed save, and make it clear that you won't budge.

You reach out to take the weapon, but the inexplicable feeling of guilt returns. No matter what you do, you cannot bring yourself to do it.

That said, you should only dictate emotions if they come from a magical source

In most circumstances, players are the final authority of their character's inner life. Dictating emotions or actions from a character without a clear external force acting on them is robbing them of their one and only source of narrative control within the game. Don't do it.

If you want them to feel guilty for a reason besides magical mind control, give them a reason to feel guilty, then accept however they choose to roleplay in the face of that reason.

Matt Mercer and his player were making their own fun, outside the rules of D&D. You shouldn't expect it to work for you.

So Critical Role is kind of the cooking show of D&D games. Experienced professionals are out there doing things that are easy and even fun for them, but which are not likely to be easy or fun the first time you try them in your kitchen and may even backfire horribly.

The most important thing about the player who couldn't save vs. guilt and went on to emote it for the rest of the session is that they knew Matt, and they trusted that Matt would give them something to do that would be fun.

(The second most important thing is that, being Critical Role, the player was probably a professional actor of some description and had at one point spent four hours in a soundproof booth pretending that their soul was being burned by zenthium, which is not even a thing that has ever happened to anyone. Pretending to have a human emotion for an understandable reason is baby stuff.)

In D&D, you as the dungeon master get to say things without restraint about the entire world in all its wonder and majesty - except for the tiny, tiny bit of it that's inside each player character's head. Your players are the ultimate authority on the things their characters are thinking. If you want to put a voice in their head, either it's not supposed to be there or, for some reason, there actually is a voice in this character's head that they cannot control.

You are, however, free to describe a situation that should make people feel guilty and take note of how the player characters react.

How To Describe A Situation That Should Make People Feel Guilty

So the first thing you should understand is the ethics of heroic adventuring. In the absence of mitigating factors, when you present adventurers with a dungeon, regardless of alignment, they tend to assume that the dungeon and everything in it is theirs. Theirs to kill, theirs to break, theirs to plunder, because it's not like anything else can legitimately claim it. If someone else was responsible for it, it wouldn't be a dungeon. Or maybe it's bad guys who are responsible for it, and bad guys don't get to have cool stuff like dungeons when there are good guys around.

So the most important thing you can give them is a reason why the dungeon, or even just the part of it that is these weapons, might not be theirs. It might be:

• an actual claim from someone the PCs respect. The dungeon is the burial site of the Order of the Emerald Heart, and in between the pilgrimages out there some monsters killed the novices set to guard it and moved in. Anything not of obvious monster make is the Order's - you're really going to take it?


• an imputed claim from a stranger. The dungeon was built by a high-level adventurer or team of same who left on a journey some years ago and have not returned, and in the meanwhile something dangerous has broken in. Or possibly out. These things are mementos - you're really going to rob a house?


• someone else's, by a tradition they respect. Around these parts you're buried with your weapon; it's a common folk belief that you'll need it to continue to fight in the lands beyond. You're really going to leave the dead helpless in the hereafter?


• someone else's, by a tradition they might not respect. So the dwarves believe that when a weapon's time is done, when the person who it was made for abandons it, it should be returned to the earth. The dwarves also believe in showing off the things they've made, so in practice they just leave it up for display and rub some dirt and stone on it; if the earth wants more than that it's welcome to take it, but the earth's got time. All these weapons have been treated that way - if you just lift them and sell them, how likely is that going to be to tick off some dwarf?

And maybe they take the stuff anyway. Maybe they're greedy, maybe they're desperate, maybe they're gonna frame Drake and his stuck-up band of bravos. So at that point, nod and write it down. You've got something to use for later. Not something you must use, this isn't a morality play, but if the PCs are incautious or unlucky, well, it's possible that someone cared about the dungeon, even if they didn't.

Losing 1d4 HP is too small a cost for your trap.

It sounds like you were trying to design some sort of mental trap for the PCs. The weapons are the bait, and taking the bait has some consequence.

Unfortunately, this was not a well-designed trap, and the players saw right through it.

Pretty much, they were willingly hurting themselves for a little more loot.

Every trap or hazard has a cost. Let's do the math: 1d4 is 2.5 on average, and with a Wisdom saving throw to negate it, the average is even less. So you gave your players a predictable choice, where they could gain a weapon at the cost of ~2.5 hit points per weapon.

At 3rd level, that's arguably an affordable tradeoff, since the PCs are out of combat, and can recover hit points later via spells or resting.

How do you design more interesting and costly traps?

In general, traps and hazards should, at minimum, consist of a cost and a reward. The cost is the consequence that the PCs incur by activating or failing the trap. The reward is what the PCs get if they bypass or succeed against the trap. Usually the reward is survival, or forward progress, or gaining some extra loot.

For the PCs, interacting with the trap involves a tradeoff between its reward and its cost. If the reward is much higher than the cost (e.g. free weapons for some minor hp loss), then you incentivize the PCs to engage the trap. If the reward is much lower than the cost, then you incentivize the PCs to avoid the trap.

Hit point hazards are certainly feasible, and the DMG (Dungeon Masters Guide) provides a table of recommended hazard damage based on the average PC level.

Damage Severity by Level
begin{array}{|c|c|c|c|}
text{Character Level} & text{Setback} & text{Dangerous} & text{Deadly} \
hline
1st-4th & 1d10 & 2d10 & 4d10 \
5th-10th & 2d10 & 4d10& 10d10 \
11th-16th & 4d10 & 10d10 & 18d10 \
17th-20th & 10d10 & 18d10& 24d10 \ hline
end{array}

For a 3rd level party, even a low-severity setback should have a cost of roughly 1d10 (average of 5.5) damage. And rolling a 10 on that d10 would certainly make the PCs think twice about grabbing another weapon from the rack.

However, if you want some game mechanic for representing a sense of overwhelming guilt, then the hazard's cost should be more interesting and lasting than simple hit point loss. Get creative here. Maybe failing the trap imposes a level of exhaustion, or a short-term madness option, or a thematically relevant spell effect.

Lastly, you can make traps more costly simply by reducing the reward. Much like a treasure chest that turns out to be a monster, you could have the loot degrade in value; if the weapons suddenly crumbled into dust, you incentivize the PCs to leave the trap and move elsewhere.

Trying to impose a character's emotion as DM can be one of the worst things a DM can do. Choosing how the character acts and feels is the role of the player. No player wants to be told how THEIR character should be acting. It breaks immersion and destroys any feeling of freedom the players have.

If a player is acting in a way that is blatantly counter to the character's motivations and backstory, mention it between games and talk about changing the character's story to better reflect the player's play-style. If they're stubborn and won't work with you, remember that you control everything BUT the character and the player. You can make consequences for their actions (they get kicked out of their paladin order). But you can't choose how they feel about the consequences.

If this is meant to be a magical trap, describe what is trying to cause a sense of guilt in them. Maybe upon touching the weapons, the player is bombarded with a vision of the weapons waiting for their master to return, how scared they are of being taken and not being there for their true master when he needs his precious tools and friends. At that point, it's up to the character if they feel too bad to take the weapons.

Alternatively, you can have the magical trap trying to magically charm the characters into not taking the weapons. At that point, you as the DM can dictate how the characters react while the charm is in effect, because the characters themselves don't have control of their bodies. But expect them to come back and try again.

You could also magically trap the weapons to give horrible mental images of what might happen if they take the weapons, and say the character pulls his hand back instinctually. At that point, the player can choose not to take the risk, or try to fight through the fear, at which point they make a wisdom throw or be frightened and incapable of moving toward the weapons.

In Critical Role, Matt Mercer worked with the Liam O'Brien on Caleb's madness, and relies on the madness table to decide how Caleb Widogast's fire trauma affects him. This is part of Caleb's character, and Matt only makes Liam roll a save after an agreed upon trigger.

You should not unilaterally impose feelings on a character unless they come from a magical source, or have a pre-agreed mechanic for causing it. Doing otherwise breaks your social contract with your player.

The episode(s) of Critical Role where the mechanic you mention is used have a story based reason for them. Importantly the mechanic you mentioned is something that Liam O'Brien (the character player) and Matthew Mercer have worked out together, and is related to the character's backstory.

The details of that backstory and the mechanic are in this spoiler:

Caleb killed his parents using fire spells while under the effects of a spell that planted false memories in his mind (of his parents being traitors to the empire). This effect broke him and resulted in him being put in confinement. Since his "escape" any time he kills someone using a fire based spell and fails a wisdom saving throw the trauma of what he did comes back to him, stunning Caleb for a while (a minute iirc).

Without that agreement you are taking away the player's agency, which will reduce your players fun.

The exception to this is if the effect is caused by magic, in which case the players should have some way of removing said magic (or detecting the magic effect).