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: 6131627" data-attributes="member: 1465">I totally second this view. This is how it's been working so far but (as I wrote previously) the upcoming Fighter's subclasses are going to break this design principle.As for subclass choice being optional, it won't be, but there is probably going to be a solid simple subclass choice for each class, e.g. the one which grants the smallest amount of fiddly bits, just a couple of strong benefits. The Scholarly Wizard is definitely going to be the default subclass of the Wizard because it just makes you "more wizard" without taking a specific direction. Also, it will always be possible to just look at the Basic book and pick that description of the class, since it will contain the default subclass already built-in, e.g. it will say straight that the Wizard learns 2 spells  per level (unlike the Standard Wizard saying you learn 1 spell + 1 spell if you have the Scholarly tradition).I don't however agree with your preference of having 4 core classes and then have the other classes turned into subclasses for a couple of reasons. First, most of the other classes are very different. If Barbarian was just Rage, Ranger was just Favored Enemy, Druid was just Wildshape, then maybe we can do so, but in the past these classes grew to be archetypes of their own, so it's quite hard to describe them anymore like subclasses, not impossible but it would require to reduce the class "skeleton" a lot because the subclasses packages will be much bigger than currently. Second, the subclasses can be used to deliver alternatives that groups can allow/disallow in their games, depending on fantasy setting and gamestyle: take the Scholarly Wizard again, this can be used to allow rituals to be cast from spellbooks instead of from prepared spells, and if one group does not like the idea, they can just ban the subclass, same thing with non-LG Paladins. Similarly it might be possible to have a Barbarian subclass which has Rage as an encounter-based feature instead of daily, or a spell-less Ranger, or a Rogue without sneak-attack... If Barbarian is a subclass of Fighter, then you can only allow/ban all Barbarians, thus subclasses give more room for customization at group's level, not just as player's level.Multiclassing is not affected by subclasses, it should work like a charm.</blockquote>

Verification