Reply to thread

Message

<blockquote data-quote="Shin Okada" data-source="post: 4132676" data-attributes="member: 1956">When a player try to take a cohort in my playgroup, that player usually does not do that for his gain. It is usually done to complement the lacking ability in the party (say, no rogue) or to balance the party out (say, a party is very strong in offense but has only one healer). &quot;unbalanced&quot; party may be composed when a player or two come or leave a play group. That is what actually happening in my play group now. A member, who was playing a single-class Paladin left the group due to graduate from a university and went back to his home town. As his PC was not only the best tank in the party but a second-healer (don't underestimate lay on hands and paladin's spell list), now our party is very strong in offense but rather weak in defense and healing power.So, we are using Leadership rules to either make a small party playable (actually, I say at least 5-men party is the minimum &quot;balanced party&quot; in 3.0e/3.5e, though the core book suggesting 4 as a default), or, to allow each players to play more variety of characters or simply what he/she want to play. And also for RP purpose (apprenticeship and such).And there is another problem in current RAW. A PC can &quot;fire&quot; and &quot;replace&quot; his cohort without much problem if he has high enough charisma and reputation anyway. PC Sorcerers, Paladins and such are so charismatic that penalty caused by &quot;cohort death&quot; or others can be easily absorbed. And actually, a cohort who is too low in the level comparing to other members become simply a burden.In my opinion, It is much better to have a way to let the same cohort catches up, than to let PCs replace his cohort because the cohort is now too weak comparing to the others and cannot adventure with PCs any more.But anyway, through this thread we already know that by RAW, PCs can replace a cohort almost freely but there is no way to let the cohort catches up to the useful level. So, this should be a house rule area already.</blockquote>

[QUOTE="Shin Okada, post: 4132676, member: 1956"] When a player try to take a cohort in my playgroup, that player usually does not do that for his gain. It is usually done to complement the lacking ability in the party (say, no rogue) or to balance the party out (say, a party is very strong in offense but has only one healer). "unbalanced" party may be composed when a player or two come or leave a play group. That is what actually happening in my play group now. A member, who was playing a single-class Paladin left the group due to graduate from a university and went back to his home town. As his PC was not only the best tank in the party but a second-healer (don't underestimate lay on hands and paladin's spell list), now our party is very strong in offense but rather weak in defense and healing power. So, we are using Leadership rules to either make a small party playable (actually, I say at least 5-men party is the minimum "balanced party" in 3.0e/3.5e, though the core book suggesting 4 as a default), or, to allow each players to play more variety of characters or simply what he/she want to play. And also for RP purpose (apprenticeship and such). And there is another problem in current RAW. A PC can "fire" and "replace" his cohort without much problem if he has high enough charisma and reputation anyway. PC Sorcerers, Paladins and such are so charismatic that penalty caused by "cohort death" or others can be easily absorbed. And actually, a cohort who is too low in the level comparing to other members become simply a burden. In my opinion, It is much better to have a way to let the same cohort catches up, than to let PCs replace his cohort because the cohort is now too weak comparing to the others and cannot adventure with PCs any more. But anyway, through this thread we already know that by RAW, PCs can replace a cohort almost freely but there is no way to let the cohort catches up to the useful level. So, this should be a house rule area already. [/QUOTE]

Verification