Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="DEFCON 1" data-source="post: 7167664" data-attributes="member: 7006">I don't know if you've ever tried this idea or if your DM has ever seen this idea done, but it might give both of you what you want.The issue seems to be that your DM doesn't like the idea of a single class character suddenly gaining a level in some "new" class for absolutely no reason.  Because he's seeing classes as confined packages of ability and story.  When you take a level from a new class, you are taking on the entirety of that story all at once, seemingly out of nowhere.  "You were this Cleric of Light when suddenly you "broke bad" by becoming a Rogue all of a sudden?  Nuh uh!  There needs to be an event and a training and a reason for that to be happening all at once!"So what I think needs to happen is that your DM needs to see your character's class as ONE full story, with its own set of abilities and features.  Probably with its own class name too.  The difference of course being that the abilities and features of the class will come out of two different PHB classes.  But you need to actually write up this new "class" with its own name and its own leveling chart, and quite possibly a solid story why this new class exists.So for example, you could decide to create a "Skald" class.  And you should write up this "Skald" class just as every other PHB class is written up, with all the proficiencies, the leveling chart, the class features all written out.But where is this information coming from?  Pulled directly from the Bard and Barbarian classes with each level taken based upon how you are splitting up the multiclassing.  So let's say for your Skald, you see it as a 2 to 1 Barbarian/Bard split.  So your 1st level of your Skald chart and features matches the 1st level of Barbarian.  The 2nd level of the Skald matches the 2nd level of Barbarian.  The 3rd level of Skald matches the 1st level of the Bard chart.  The 4th level matches the 3rd level of Barbarian, the 5th to the 4th Barbarian, the 6th to the 2nd Bard, so on and so forth.  So what you end up with is a Skald class that LOOK like its own thing with its own features and such, only if you were to take it apart you'd see things matching those two other classes.Dragon Magazine did this exact thing during the 3E era, where they created a whole heap of "new" classes that were basically just multiclasses with the names stripped off and given to the new class identifier.  While it might not solve all of your DMs problems in terms of whether they are too powerful or not powerful enough (and that's going to come on a case-by-case basis)... at least if you can package your multiclass at the beginning as its OWN class (and not looking like a multiclass)... he might be able to get past the "story" part of it that he has a problem with.I mean after all... if this "barbarian skald" you were creating would get a random mechanical ability at 3rd level as part of its leveling process-- like the ability to 'Frenzy' (the Path of the Berserker feature), or the ability to gain additional feet on his long and high jump (the Path of the Tiger Totem feature)-- why is that any different than gaining a random mechanical ability to inspire his compatriots through the songs of their ancestors (Bardic inspiration)?  They are ALL just random new abilities that are given to the class as part of the leveling chart because they theoretically "make sense"... so just create an entirely new chart for this new class where these abilities are spelled out in order so that they too just "make sense".</blockquote>

Verification