Axiomatic Unicorn said:
Yes, a gnoll paladin would be suboptimal. But a gnoll is not a core race. Rogue and Paladin are both core classes.
Not that all class combinations are equal, wizard/sorcerer for example.
Gnolls aren't a core race, agreed. That's why I gave all those other examples of sub-optimal decisions, which are all core examples. But we agree, not all combinations are equal.
I'll repeat myself as well, I don't have a problem with Paladin Orders that require a more stringent code. I just don't see that the requirements you place on the are demanded by the PH anywhere.
I agree with this statement. You may have misunderstood me. Think of the "no sneak attacks on unaware opponents" restriction as my personal interpretation of the "dishonorable" part of the Code for my campaign. There is nothing in the PHB to directly restrict sneak attacks by paladins in any way. Some DMs will do so, because they will perceive it as dishonorable and a gross violation. That's my POV, and I'm applying it to all orders of paladins IMC, even though it will probably not be an issue in actual gameplay. I doubt I'll have any rogue/paladins.
Honestly, I don't see how your example addresses my knight in shining armor concern. Your example WAS still a knight in shining armor. Perhaps he was not a full Cavalier Lawful Stupid stereotype. But he was still an "I challenge thee" Knight in shining armor. I find the idea that this attitude is a MUST to be depressing. There is so much more roleplaying potential in the Paladin class that gets buried in these narrow stereotypes.
And if you are inplying that being a paladin in one of my games would be easy, you are wrong. I just think I have a wider variety of what may make the paladin's duty challenging.
Sorry, I guess I didn't understand the question. I
do see all paladins as "knights in shining armor" as far as behavior is concerned. The Code of Conduct backs that belief up. By its nature, it's a restrictive class.
What you find depressing, I find challenging. Nothing wrong with disagreeing on something that subjective.
And I wasn't implying anything, except maybe that playing a rogue/paladin in your campaign would be easier than playing the same character in my game. Probably a gnoll paladin would be easier to play in my game than yours. Anyhow, I doubt playing any character in your game would be easy, since you're a card-carrying member of B.A.D.D. My players certainly haven't had an easy time lately.
You say that paladins are supposed to be warrior types, not rogue types. Of course you are correct. The fighter class is also supposed to be a warrior type and not a rogue type. But, to me, these comments greatly miss one of the fundamentals of 3E. Characters are no longer defined by A SINGLE class, but rather the whole of their parts. Just because the fighter is not a rogue type, does not mean a rogue with levels of fighter is not a rogue type. By the exact same token, a rogue with levels of paladin is still a rogue. Fighters and Paladins are not rogues, but characters are the sum of their parts. Paladins are also not arcane spellcasters. But a paladin sorcerer would gain all the abilities of both classes.
I agree with this sentiment for all classes except the paladin.
Another underlying principle of 3E is that roleplaying restrictions should not be used to balance game mechanics. The paladin does just that. Paladins are special because they have such strict roleplaying restrictions that balance their game mechanics.
A rogue character with levels of paladin would consider himself primarily a paladin, regardless of his skill set. Answering the call of being a paladin defines a character. The paladin class is much more than a skill set.
And yes, you have not crippled the rogue, you have simply made him fight with one hand behind his back.
Nonsense. He still has plenty of options to use sneak attack, and has plenty of use of the other rogue abilities and skills.
Btw, isn't "crippled " the same as "fight with one hand behind his back."? Or is my sarcasm detector broke?
The same argument could be made regarding other classes. If I think that a paladin/wizard who casts a chaotic spell (And I'm not saying I feel that way) has acted dishonorably then there will be repercussions. This doesn't cripple the wizard class. And even if it did, the player made the choice to play such a character, not me. You can choose to play a wizard with an Intelligence of 9, btw, or play a sorcerer with the Quicken Spell feat, but I don't recommend it. The freedom of choice extends to the freedom to make bad choices. Caveat Player.
Have I weakened paladin/rogues IMC? Yeah, a little. But I can do that IMC. And I haven't stepped outside of the core rules to do so.
Allow me to tweak your alternative example:
The paladin watched the heavily armored foe step blindly by and considered attacking him from behind, certain that he could destroy the threat to the city in one quick thrust. But his honor would not allow it. So instead....
"The paladin stepped from the shadows, and locked eyes with his heavily armored foe. 'Your dawn has come. Surrender or be destroyed by the light of Pelor'.
The dark knight's grin could almost be seen beneath his skull visor as he charged his leather-clad foe. His blackened great sword swung into a great arc and sliced into the side of the paladin.
Wincing in pain for only an instant, the noble warrior faltered, apparently in fear. The black knight saw his chance and raised his blade for a mighty blow. But the paladin was not as wounded as the evil one believed, and certainly not afraid. With stunning speed and precision, his holy rapier lunged upwards,
But the foe's smashing blow rang true and darkness fell upon the paladin. The foe, thinking the paladin killed, fled before the battle drew attention. The paladin later recovered and healed himself, but the foe knew he was being hunted and could not be caught unaware again. Within weeks the town was conquered and the people enslaved. But, on the bright side, the paladin had his honor."
(Remember, bluff is a standard action that gives a bonus the NEXT time, the other guy gets a turn in between.)
Oh I know how it works. I envisioned the paladin as readying a Bluff action when attacked, then sneak attacking before the black knight on the 2nd round because of his higher Dex.
Not important though.
The point I was trying to make is that a rogue/paladin can behave like a traditional paladin and still use sneak attack, and that I haven't crippled that class combination or tied anyone's hands.
Oh, and I also never said that paladins are not concerned about HOW they win. They are. A paladin rogue will be more limited in action than a lawful good fighter rogue. That does not mean that there is only one narrow path to victory that is allowed.
Despite that statement, it's clear from the scenario you wrote that you (and many others) favor more of a "the end justifies the means (as long as it's not evil means)" approach to playing a paladin, and I favor an approach that is more of "the way you fight is as important as whether you win" approach. I put more emphasis on the honor of the paladin than most seem to.
The cool thing is that we're both right. The vagueness of the Code allows both interpretations. The un-cool thing is when the player of a paladin and the DM have a misunderstanding over something like this. It's clear that communication is key.