Upgrade your account to a Community Supporter account and remove most of the site ads.
Rocket your D&D 5E and Level Up: Advanced 5E games into space! Alpha Star Magazine Is Launching... Right Now!

Reply to thread

Message: <blockquote data-quote="DEFCON 1" data-source="post: 7067150" data-attributes="member: 7006">Well, it's mainly because of how I see the concepts of class and subclass are designed.  You're coming at it from the angle of having the idea of a flavorful identity and then finding a class to insert it into.  So for instance... you come up with an individual identity of a "ninja", and you then decide how many different ways can you make that ninja (and how many different classes can receive it.)  You start at the subclass and work upwards.Whereas I come at it from the class POV and work downwards.  I start with the class.  Now what are the flavorful variants of that class are there?  And to me that is what the subclasses are... not flavorful identities in their own right, but absolutely part and parcel of the class they fall under.  So no... to me a hunter can't be a fighter or a rogue, because I'm starting with the ranger-- I have the ranger and decide what are the facets of that ranger?  And that is where the hunter falls in... directly as an offshoot of the ranger that it is a part of.  The hunter isn't its own thing, it is specifically a subset of the ranger class.  And that's why to me it's considered a subclass.Truth be told... we already DO have a mechanic in the game that applies a flavorful identity across multiple classes, and that are the Backgrounds.  I think that's where having a particular flavor that goes along with any or all classes really shows its head in the game.  So if you thought a ninja could and should apply to multiple classes, then I'd suggest that perhaps the ninja should be a background more than anything else.  And by the same token back to your point about why couldn't fighters, rogues, and wizards be hunters... in a way they already are, in that an Outlander (ie "hunter") can be any of those classes.  Of course... mechanically the background grants much less to your PC than a subclass does, so I can certainly understand why that might not do it for you... but at least for me that's where the "one flavor across multiple classes" really seems to be best suited to appear.But again... these are just my thoughts on the matter of where I think the demarcation should be between class, subclass, and background.  Obviously if you don't agree, you can (and should) do whatever you'd like.  And if you can get it to work for you, then that's awesome!  I personally wouldn't (due to my own POV), but my opinion really shouldn't matter to you in the least.  LOL!  <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink    ;)"  data-smilie="2"data-shortname=";)" />  You do what you do and I hope it works well!</blockquote>

Verification