SteveC said:It seems that I am going to have to disagree with many here and give a big raspberry to the "intimidate automatically fails." Many years ago in the Complete Fighter book, TSR gave me a quote I took to heart for all of my GMing: "don't say no, determine difficulty."
But what would that achieve? Intimidating a noble is quite hard unless you are massively powerful o have some way to blackmail him, but lets say the PCs manage to intimidate the Duke to support them. What kind of support would the Duke give the PCs? Certainly not honest support but rather unreliable one and as soon as the PCs show a weakness the Duke will exploit it to get rid of the PCs.
That sounds more like the result of a failed Skill Challenge (Don't forget, a failed challenge doesn't have to mean "No" but can also mean"Yes with bad side effects") so its quite logical that a successful intimidate moves you toward the "bad" result.
So the Duke can be intimidated, but both a successful and unsuccessful attempt will in the end get the same, bad, result.
Cadfan said:I must have missed the place where skill challenges were declared to be mandatory for use by all DMs in all situations.
There is a whole chapter about Skill Challenges including imo unnecessary rules about complexity which in the end hinders roleplay because its too restrictive. If Skill Challenges would be presented as a guideline they would need less space which could be used for something else in addition to be better for the game as you can react better to what the PCs do.
Last edited: