SteveC said:
This is a good point, but I have never seen a GM run a game with a paladin in it where the code didn't strongly affect not only the paladin, but the entire game. If the threads on Enworld are any indication, I'm not the only one.
I ran a game where a player played a paladin, and it wasn't too much of a problem. Okay, he wasn't the only thing that kept the whole group from going berserk and kill everyone.
In fact, the player applied the code to his character more strongly than I did: After they saved a village once, some of the female villagers (those of the young and comely persuasion) wanted to.. express their gratitude. Some nice, no-strings-attached one-night stands (they were heroes, and there was no character with a low cha score in there to boot).
The paladin refused, and spent the night with his horse (no, not like that, though the rest wound him up about that for days to come). Next morning, when he prayed to Lathander (his patron deity), the paladin felt that even his deity was surprised at this refusal of a good time.
So if a GM is not looking to have the code be a major problem for the character, then there's no real issue, but the code is still there, with mechanics behind it...and anything that affects a character mechanically one way should have a corresponding benefit the other way. (In my opinion, of course).
It's bad to balance roleplaying disadvantage with rules advantages, though.
I might add that even though paladins are subject to a more strict definition of LG, most characters in your average campaign are good aligned, including most clerics, and they stand to lose something, too, if they commit evil deeds (especially those clerics!)
SteveC said:
Hmmn, I think this is a very good question to ask, because the paladin should be mechanically more powerful than other classes.
No, he shouldn't. It's a base class, and all base classes should be about the same.
Why is that? Because they are unique in having a mechanical penalty for not being roleplayed properly.
Well, we already heard that this is something that the DM will enforce or not, and, as I said, the GM can punish everyone for bad roleplaying.
I'll say it again: Paladins either get equal treatment, or they become a PrC (personally, that fits the concept better, anyway).
3E designers went out of their way to say that mechanical benefits shouldn't be given to balance roleplaying penalties, and that makes a lot of sense to me. The problem in the paladin's case is that he has a mechanical penalty for roleplaying, but has no corresponding bonus to go with it. Or at least that's the way it seems to me: I would say that if you took away the alignment and code restrictions for the paladin, he would still be perfectly balanced with other classes out of the PHB.
Well, if you are going to enforce the roleplaying restriction the paladin has, give him roleplaying benefits: A paladin will certainly be more highly regarded by the common people (they might suspect others of acting only for their own good, but the paladin clearly does it for the common good!), and so will the authorities. After all, they see a paladin who still has his class abilities and they just know that he's one of the good guys.