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

Reply to thread

Message: <blockquote data-quote="Li Shenron" data-source="post: 6130569" data-attributes="member: 1465">Ok, first one clarification on my previous post. I wrote I don't see any problem to multiclassing coming from subclasses, in the sense that they don't change anything IMHO when multiclassing compared to how it already is with just classes (without subclasses), i.e. subclasses will have the same problems as classes when multiclassing, thus if there is no problem with MCing classes there is also no problem with MCing subclasses.Now as for "jobs", my opinion is that 5e started off with the great idea of using Backgrounds to separate your "job" in the fantasy world from your "role" in adventuring. This way, your class doesn't define what you do when living in Waterdeep, it defines what tools you use when adventuring (after all, you advance in your class by gaining XP, and you gain XP while adventuring, not while teaching magic in the Arcane Order Academy!).That said, if you want (especially in a high-fantasy setting such as FR), "Wizard" can also be a job even if you have Backgrounds. All you have to do is pick a Background that either reinforces the image of a Wizard (e.g. Sage) or at least that doesn't imply another job (even if it implies another job, you can still treat the Background as representing strictly your past, and you're fine).Unfortunately, the announced changes to Fighter's subclasses (although they sound nice ideas by themselves) actually break that division, because "Gladiator" is a job, and so is "Knight" (albeit debatable).</blockquote>

Verification