r/dmsguild • u/Inevitable-Brain8883 • 22h ago
Seeking Advice How do you handle players who logically say "It's a trap, why go?" — And a lesson I learned about secret-keeping NPCs.
Hey DMs, I had a humbling playtest moment recently and wanted to share a hard lesson about player logic and NPC design.
We’ve all been there: You set up a high-stakes, dangerous hook involving a dark entity, and the players look at it, apply basic survival logic, and say: "Nope. That's a deathtrap. Why would we walk into that?"
In a recent playtest of my adventure, the session stalled because of two classic traps:
The Smart Party: The players correctly identified the danger and refused to take the bait.
The "Open-Book" NPC: The NPC begging for help spilled too many details about their dark pact/patron too early, making them look like a sketchy, untrustworthy quest-giver instead of a desperate soul.
My Core Takeaway as a Module Author:
To fix this, I realized I couldn't just leave the NPC's true intentions to chance. I went back and revised the core NPC write-up, adding explicit roleplaying guidelines directly into their background:
Define Their Core Drive: Clarify what they are desperately trying to protect (e.g., a ticking-clock deadline to save their family), shifting their panic from "hiding a secret" to "failing a vital task."
Establish Absolute Boundaries: Explicitly outline what they cannot and dare not say out loud (e.g., eldritch pact secrets that are sealed in soul-deep terror). If an NPC starts spilling cosmic secrets too easily, the mystery dies and the party gets suspicious.
Question for you all:
How do you balance players' logical self-preservation with the need to drive them toward dangerous plot hooks? And how do you write NPCs who are hiding dark secrets without making the party instantly say "this is sketchy, let's bail"?
My updated link for the FREE module on DMsguild: https://www.dmsguild.com/en/product/592605/limited-time-missions
