Looking on the threads it seems like these 3 classes have some grey areas within the rules. My aim for this thread is for everyone to collaborate to make guidelines for the codes, help with difficult in-game scenarios, answer FAQs, and do whatever else the Paizo community needs.
So, first of all, we need codes of action for the 3 classes. Spacelard did a pretty good job with the druid code I think. Here's a paragraph:
"You are young and can not bear much reality. Respect age. Respect women and the totems of the hearth. Respect the secrets which are too dangerous for you know. Listen before you talk. Speak only when spoken to and do not raise your voice. Sit only when invited. Treat everyone and everything with respect. Share everything you have and take everything that you need. That is our Law. Hunt and gather only what you need. Beware of young women who invite you to sleep at their hearth!
There was more too, I felt this paragraph was a good summary.
Paladins and Clerics need their codes explained and clarified. The Druid code seems pretty well explained (to me, anyways) by Spacelard. But, as I said, this is a collaboration, and everyones opinion helps.
Looking on the threads it seems like these 3 classes have some grey areas within the rules. My aim for this thread is for everyone to collaborate to make guidelines for the codes, help with difficult in-game scenarios, answer FAQs, and do whatever else the Paizo community needs.
So, first of all, we need codes of action for the 3 classes. Spacelard did a pretty good job with the druid code I think. Here's a paragraph:
"You are young and can not bear much reality. Respect age. Respect women and the totems of the hearth. Respect the secrets which are too dangerous for you know. Listen before you talk. Speak only when spoken to and do not raise your voice. Sit only when invited. Treat everyone and everything with respect. Share everything you have and take everything that you need. That is our Law. Hunt and gather only what you need. Beware of young women who invite you to sleep at their hearth!
There was more too, I felt this paragraph was a good summary.
Paladins and Clerics need their codes explained and clarified. The Druid code seems pretty well explained (to me, anyways) by Spacelard. But, as I said, this is a collaboration, and everyones opinion helps.
Thanks.
I'll dig out my versions of the Paladin's code and an example of a couple of Cleric ones. I prefer to use a story telling method of explaining what my cranky mind is trying to say. Giving examples of what it means to be a Druid is better than a list of Do's and Don'ts and it works for me and my group.EDIT LINK
Part of the problem is that everyone has a different idea of what the code should be, and it should change for each god. There is a reason it is vague, so that each player can define it themselves. For instance, there is a great Paladin code of Sarenrae that works great for them. But it would not work well for a Paladin of annother god, and not all players/GMs believe it is right.
Part of the problem is that everyone has a different idea of what the code should be, and it should change for each god. There is a reason it is vague, so that each player can define it themselves. For instance, there is a great Paladin code of Sarenrae that works great for them. But it would not work well for a Paladin of annother god, and not all players/GMs believe it is right.
Mine is deliberatly vague for the Druid but it gives, I believe, a good base to start from. And it would be more productive than the hundreds of posts about Gish, why Barbarians don't get Profession Skill...
Part of the problem is that everyone has a different idea of what the code should be, and it should change for each god. There is a reason it is vague, so that each player can define it themselves. For instance, there is a great Paladin code of Sarenrae that works great for them. But it would not work well for a Paladin of annother god, and not all players/GMs believe it is right.Mine is deliberatly vague for the Druid but it gives, I believe, a good base to start from.
Both of you have good points, That's what I want, a base. A general code for them. It can by all means be tailored to suit individual gods and campaigns. But codes weren't the only reason I made this thread. I also wanted everyone who needed help with scenarios liek these to get it.
http://paizo.com/paizo/messageboards/paizoPublishing/pathfinder/pathfinderR PG/general/paladinDevilWhenIsHisCodeBrokenSorry, I have yet to figure out how to post direct links. You can just copy and paste into an adress bar
So, first of all, we need codes of action for the 3 classes.
Nah. What we need, if we need anything, is to make it more clear that these things aren't set in stone. They depend on the character, his deity, his belief, his philosophy, his player, his campaign, his world and his GM.
The day a player comes to me and says "but page 27 of the rulebook clearly states that my paladin is allowed to kill baby goblins* so you cannot tell me I'm wrong!" Is the day I arbitrarily kill him off (him, not his paladin. I won't resolve out-of-character problems in-character)
This game relies heavily on communication and collaboration. That's what makes it so great. So what's so bad about a player and a GM communicating and collaborating to work out a code of conduct for their character?
*I intended to go with "baby kobold", but baby kobolds are kobolds, and under no circumstances is it not allowed for anyone to kill kobolds.
So, first of all, we need codes of action for the 3 classes.
Nah. What we need, if we need anything, is to make it more clear that these things aren't set in stone. They depend on the character, his deity, his belief, his philosophy, his player, his campaign, his world and his GM.
The day a player comes to me and says "but page 27 of the rulebook clearly states that my paladin is allowed to kill baby goblins* so you cannot tell me I'm wrong!" Is the day I arbitrarily kill him off (him, not his paladin. I won't resolve out-of-character problems in-character)
This game relies heavily on communication and collaboration. That's what makes it so great. So what's so bad about a player and a GM communicating and collaborating to work out a code of conduct for their character?
*I intended to go with "baby kobold", but baby kobolds are kobolds, and under no circumstances is it not allowed for anyone to kill kobolds.
Not quite sure if that last part was a joke... but ok. Speaking of which, I am making an anti-paladin core class for a PC who was denied bein a paladin by his evil party... I'm just changing all the lawful stuff to chaotic and all the good stuff to evil.