Reply to thread

Message

<blockquote data-quote="Fighter1" data-source="post: 2787373" data-attributes="member: 39381">Here are my top five hose rules (usually applies to PrC's more than anything):Pre-Approval#1 All PrC’s and non-core book core classes require pre authorization by the DM; period.#2 One PrC per PC: PrC’s are supposed to be just that; PRESTIGE classes; there is an organization, club or very specific attribute to the class that makes it special in some way. You can’t have two of those. #3 You have to be of a certain levelIn mind to achieve a PrC one must elevate oneself to a “master” or sorts; that does not come easily. Level 8 to 10 is a good starting point before allowing any PrC’s (many already require BAB’s of that or skill point levels that require that level anyways).#4 RelationshipAll classes a PC takes must have a theme; in other words the player has to give me a reason why his PC would do such a thing. For example why would a fighter want to take on Legendary Leader as a PrC. There are lots of reasons but the player needs to tell me, in writing, and I’ll hold him to that logic.#5 Enforce the rulesMost PrC’s have an organization, code, etc. that they are answerable to. Enforce those rules be they mechanical or role playing. Many munchkins take on PrC’s with role playing requirements because they think it is a cheap way to maximize and they won’t really have to follow the PRing rules; in my game they would be very wrong. Kensai is a fine example as is Knight Protector; enforcing those rules as you would a Paladin’s code. Those classes with an organization; most organizations ask something of their members at times…that comes into play as much as is reasonable – and the PC is obligated to comply (or be cast out!).</blockquote>

[QUOTE="Fighter1, post: 2787373, member: 39381"] Here are my top five hose rules (usually applies to PrC's more than anything): Pre-Approval #1 All PrC’s and non-core book core classes require pre authorization by the DM; period. #2 One PrC per PC: PrC’s are supposed to be just that; PRESTIGE classes; there is an organization, club or very specific attribute to the class that makes it special in some way. You can’t have two of those. #3 You have to be of a certain level In mind to achieve a PrC one must elevate oneself to a “master” or sorts; that does not come easily. Level 8 to 10 is a good starting point before allowing any PrC’s (many already require BAB’s of that or skill point levels that require that level anyways). #4 Relationship All classes a PC takes must have a theme; in other words the player has to give me a reason why his PC would do such a thing. For example why would a fighter want to take on Legendary Leader as a PrC. There are lots of reasons but the player needs to tell me, in writing, and I’ll hold him to that logic. #5 Enforce the rules Most PrC’s have an organization, code, etc. that they are answerable to. Enforce those rules be they mechanical or role playing. Many munchkins take on PrC’s with role playing requirements because they think it is a cheap way to maximize and they won’t really have to follow the PRing rules; in my game they would be very wrong. Kensai is a fine example as is Knight Protector; enforcing those rules as you would a Paladin’s code. Those classes with an organization; most organizations ask something of their members at times…that comes into play as much as is reasonable – and the PC is obligated to comply (or be cast out!). [/QUOTE]

Verification