airwalkrr
Adventurer
I think Plane Sailing has really hit on something. The more I think about it, the more I love the idea. Using his idea, I think I've finally come up with a system that is simple, elegant, and balanced. Here is how it works:
-A multiclass character gains +1 level to existing spellcasting classes (much like prestige classes grant) for every two character levels other than said spellcasting class. However, this bonus to level of existing spellcasting class can be no higher than half of the character's levels in that spellcasting class. For example, a 6th level paladin who takes two levels of cleric becomes a 6th level paladin/2nd level cleric with 7th level paladin and 3rd level cleric casting ability.
-To calculate base attack bonus, add up all class levels with the same base attack bonus progressions and treat those as levels in one class. Then add the base attack bonuses together. For example, a 5th level cleric/3rd level rogue would have the same base attack bonus as an 8th level cleric or 8th level rogue. If the same character was also a 3rd level wizard, he would add the base attack bonus of an 8th level cleric with the base attack bonus of a 3rd level wizard (or +7).
-To calculate saving throws, add up all class levels with the same saving throw bonus progressions and treat those as levels in on class. Then add the saving throws together. For example, a 4th level ranger/3rd level fighter would calculate his Fortitude and Will saving throws as if he were a 7th level fighter or 6th level ranger. He would add his Reflex saving throw from his ranger levels to that from his fighter levels to determine his Reflex saving throw (or +5).
-Standard multiclassing penalties apply.
This accomplishes the following "fixes."
-Spellcasters are no longer at a terrible disadvantage for multiclassing. They remain behind their counterpart spellcasters in ability, but not to an extent where their spells are useless. A Ftr10/Wiz10 casts as a 15th level wizard and has the BAB of a 15th level fighter which is a fairly decent trade-off.
-Base attack bonuses do not get penalized as much for multiclassing into classes with the same base attack progression. Builds like bard/rogue or cleric/monk are more viable in combat.
-Base saving throws do not skyrocket for multiclass characters like barbarian/fighter/ranger while remaining more balanced overall. Rather than having an obscenely high Fortitude save, such a character would have simply a good Fortitude save. And rather than having an abysmal Will save, such a character would simply have a poor Will save, but not so bad as automatic failure.
There are also some optional variants common to multiclassing that could still be applied to limit or open up possibilities as desired. These can be used at the DM's discretion.
-Prestige classes count towards multiclass XP penalties.
-Only levels in base classes count towards improving a character's levels in existing spellcasting classes. This encourages PCs to stick to base classes unless they have only one base class.
-Instead of adding like base attack and saving throws together, a fractional BAB/saving throw system could be used. This increases viability at the expense of simplicity.
-A multiclass character gains +1 level to existing spellcasting classes (much like prestige classes grant) for every two character levels other than said spellcasting class. However, this bonus to level of existing spellcasting class can be no higher than half of the character's levels in that spellcasting class. For example, a 6th level paladin who takes two levels of cleric becomes a 6th level paladin/2nd level cleric with 7th level paladin and 3rd level cleric casting ability.
-To calculate base attack bonus, add up all class levels with the same base attack bonus progressions and treat those as levels in one class. Then add the base attack bonuses together. For example, a 5th level cleric/3rd level rogue would have the same base attack bonus as an 8th level cleric or 8th level rogue. If the same character was also a 3rd level wizard, he would add the base attack bonus of an 8th level cleric with the base attack bonus of a 3rd level wizard (or +7).
-To calculate saving throws, add up all class levels with the same saving throw bonus progressions and treat those as levels in on class. Then add the saving throws together. For example, a 4th level ranger/3rd level fighter would calculate his Fortitude and Will saving throws as if he were a 7th level fighter or 6th level ranger. He would add his Reflex saving throw from his ranger levels to that from his fighter levels to determine his Reflex saving throw (or +5).
-Standard multiclassing penalties apply.
This accomplishes the following "fixes."
-Spellcasters are no longer at a terrible disadvantage for multiclassing. They remain behind their counterpart spellcasters in ability, but not to an extent where their spells are useless. A Ftr10/Wiz10 casts as a 15th level wizard and has the BAB of a 15th level fighter which is a fairly decent trade-off.
-Base attack bonuses do not get penalized as much for multiclassing into classes with the same base attack progression. Builds like bard/rogue or cleric/monk are more viable in combat.
-Base saving throws do not skyrocket for multiclass characters like barbarian/fighter/ranger while remaining more balanced overall. Rather than having an obscenely high Fortitude save, such a character would have simply a good Fortitude save. And rather than having an abysmal Will save, such a character would simply have a poor Will save, but not so bad as automatic failure.
There are also some optional variants common to multiclassing that could still be applied to limit or open up possibilities as desired. These can be used at the DM's discretion.
-Prestige classes count towards multiclass XP penalties.
-Only levels in base classes count towards improving a character's levels in existing spellcasting classes. This encourages PCs to stick to base classes unless they have only one base class.
-Instead of adding like base attack and saving throws together, a fractional BAB/saving throw system could be used. This increases viability at the expense of simplicity.
