My players really aren't digging on multiclassing due to the low HP and glacial levelling so I thought of using this instead.
Once you reach enough XP to reach a new level in your current class, you may decide to multiclass instead. You must have XP = to that needed to move into the second level of that class, but, in effect you are moving from level 0 to level 1 and only gain level 1 abilities.
After taking a second class, you must decide at the point you reach the next level, whether to continue earning XP for that class or start earning it for your other class instead. You must always compeltely earn a new level in your current class before you can switch back to earning XP for your other class.
Ex. Dakkas the Asssassin, upon gaining enough XP to move to third level decides, instead, to hold that XP and wait until he has earned another 850 more (2601 total) so that he can become a Lvl 1 Wizard.
Once he has earned enough experience in his Wzard Career to move to level 2 (another 2601), he is free to continue earning experience towards Wizard 3 or to continue along his Assassin career. Whichever he chooses, he will be stuck with that decision until he manages to reach the next level in whichever class he chose.
Your actual level is equal to the combined levels of all your character classes. Saves are the same as usual, with your level determining your save bonus. Once you earn a level in a class, you gain all the privileges of that class.
As for training, that's up to your individual DM to handle how much time he wants you to spend on that.
The idea is based on the OD&D concept of the Elf, who must decide to be a fighter or a mage before each adventure, and is stuck with that decision until the end. I just made it more long term and open to everyone.
Opinions...?
_________________
IMHO, AFAIK, YMMV.
Multiclassing idea...
-
Jonathan of White Haven
- Hlobane Orc
- Posts: 185
- Joined: Tue Nov 13, 2007 8:00 am
re: Multiclassing idea...
I understand the "difficulties" that players have with most multiclassing systems. There are always tradeoffs--weapon/armor limitations, keeping track of XP, HP modifications, und so weiter. Your proposed system is interesting.
A few questions come to mind:
1. Is the PC required to have the necessary primary stat for the class he wishes to add? For example, would your ASN need to have both DEX and INT selected as his primary stats if he were to become a WIZ?
2. Upon gaining the second class, is the PC allowed to use the weapons and/or armor allowed by his original class? (This could be a problem for a FTR/WIZ.)
3. Is the PC allowed to use the *abilities* of both classes at any time?
I note that your system doesn't allow for multiclassing from the git-go. Perhaps it would be more accurate to call such a thing "dual-classing", instead. In a player-limited campaign (shortage of players, not a shortage of player ability), being able to have two classes melded into a single PC at the start can be a game-saver. I know this from experience.
_________________
"You don't understand, Beaufingle", said Lungwort cryptically. "You ARE dinner." -- M.M. Moamrath
A few questions come to mind:
1. Is the PC required to have the necessary primary stat for the class he wishes to add? For example, would your ASN need to have both DEX and INT selected as his primary stats if he were to become a WIZ?
2. Upon gaining the second class, is the PC allowed to use the weapons and/or armor allowed by his original class? (This could be a problem for a FTR/WIZ.)
3. Is the PC allowed to use the *abilities* of both classes at any time?
I note that your system doesn't allow for multiclassing from the git-go. Perhaps it would be more accurate to call such a thing "dual-classing", instead. In a player-limited campaign (shortage of players, not a shortage of player ability), being able to have two classes melded into a single PC at the start can be a game-saver. I know this from experience.
_________________
"You don't understand, Beaufingle", said Lungwort cryptically. "You ARE dinner." -- M.M. Moamrath
Re: re: Multiclassing idea...
Jonathan of White Haven wrote:
I understand the "difficulties" that players have with most multiclassing systems. There are always tradeoffs--weapon/armor limitations, keeping track of XP, HP modifications, und so weiter. Your proposed system is interesting.
A few questions come to mind:
1. Is the PC required to have the necessary primary stat for the class he wishes to add? For example, would your ASN need to have both DEX and INT selected as his primary stats if he were to become a WIZ?.
Yes.
Quote:
2. Upon gaining the second class, is the PC allowed to use the weapons and/or armor allowed by his original class? (This could be a problem for a FTR/WIZ.).
A good question and one I hadn't thought of since I'm using Weapon Mastery rules at the moment.
My answer would have to be you get to use the most beneficial weapons and the least beneficial armour in much the same manner as normal mutliclassing.
Quote:
3. Is the PC allowed to use the *abilities* of both classes at any time?.
Yes. The penalty is that you cannot improve the abilities in both classes simultaneously, so while you're hiking up the ladder towards WL3, you are not able to improve your Fighter abilities.
Quote:
I note that your system doesn't allow for multiclassing from the git-go. Perhaps it would be more accurate to call such a thing "dual-classing", instead. In a player-limited campaign (shortage of players, not a shortage of player ability), being able to have two classes melded into a single PC at the start can be a game-saver. I know this from experience.
In the case of small parties, I would be inclined to give the PCs a level or two in compensation, so a 1st level party for two players would, in my games, consist of two 2nd level characters, which means they could easily multiclass if they so choose and, unlike the normal mutliclassing rules, they are allowed the full hit dice from each level, not an average, which was the biggest complaint of our resident L2 Ranger/Cleric with 15 HP...
_________________
IMHO, AFAIK, YMMV.
I will tell you this, I find allowing them to stack their class levels to be very unbalancing, and unfair to the single class PC's.
I suggest you do not allow stacking, or only allow them to add/stack 1 out of every 3 or 4 levels obtained in their additional classes.
Plus their levelling is not "glacial", in my high level game, where the highest is a 17th level Paladin, the other dual/multi class PC's are only 2 to 3 levels behind. Considering the power their diversity gives them, such a level difference is more than fair. The Thief being one of the classes can throw this off though.
Personally, I tell them if they don't like it, don't do it. This is an iconic game, so single classed PC's is not only encouraged, but preferred.
_________________
The Ruby Lord, Earl of the Society
Next Con I am attending: http://www.neoncon.com/
My House Rules: http://www.freeyabb.com/phpbb/viewtopic ... llordgames
I suggest you do not allow stacking, or only allow them to add/stack 1 out of every 3 or 4 levels obtained in their additional classes.
Plus their levelling is not "glacial", in my high level game, where the highest is a 17th level Paladin, the other dual/multi class PC's are only 2 to 3 levels behind. Considering the power their diversity gives them, such a level difference is more than fair. The Thief being one of the classes can throw this off though.
Personally, I tell them if they don't like it, don't do it. This is an iconic game, so single classed PC's is not only encouraged, but preferred.
_________________
The Ruby Lord, Earl of the Society
Next Con I am attending: http://www.neoncon.com/
My House Rules: http://www.freeyabb.com/phpbb/viewtopic ... llordgames
Since its 20,000 I suggest "Captain Nemo" as his title. Beyond the obvious connection, he is one who sails on his own terms and ignores those he doesn't agree with...confident in his journey and goals.
Sounds obvious to me! -Gm Michael
Grand Knight Commander of the Society.
Sounds obvious to me! -Gm Michael
Grand Knight Commander of the Society.