Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*Dungeons & Dragons
Really concerned about class design
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Einlanzer0" data-source="post: 7860705" data-attributes="member: 6788934"><p>So.... I've been feeling this for a while. While, granted, we got the Artificer in the Eberron book, there's been a long term dearth of new classes for 5e. Especially in light of the new UA, it really worries me that it appears to be because WotC thinks they can/should simply turn every new class concept into a subclass for one of the existing classes.</p><p></p><p>I love subclasses, but I think that's a terrible approach, and it really needs to get called out as a problem IMO.</p><p></p><p>First, it attempts to solve the (hypothetical) problem of class bloat by adding clutter within classes, which really doesn't make much sense. 5e already addresses class bloat as a potential problem by having subclasses <em>at all, </em>but when the theme or fantasy represented within a class starts to take you all over the place with subclass options, that's an indicator we've departed from "elegant" and landed at "sloppy". As a practical concern, this makes it <em>more</em> difficult for players to digest what their options really are. They have to reverse engineer a concept or go through a layered path-choosing process.</p><p></p><p>Second, subclasses aren't multi-class friendly, so tying more and more class options to them inhibits the leveraging of multi-class rules to create a unique class concept. In other words, they result in less customization, not more.</p><p></p><p>Third, there are numerous areas where it just doesn't really make thematic sense, either in terms of edition history/lore or in terms of verisimilitude. In these cases, what happens is the idea gets trapped into a set of existing class mechanics & flavor that feels arbitrary at best and cognitive dissonance causing at worst. I <strong>can easily</strong> get on board with Psychic Warrior being a subclass for Fighter - because it's a perfect use of the subclass system to expand options without class bloat. I <strong>cannot</strong> get on board with the base Psion being a "Wizarding tradition" because it is <em>not</em>. One of many reasons for this is the thematic need for psionics to exist as a full-enough system to potentially replace traditional magic in a more sci-fi setting <em>based on precedents established in previous editions</em>.</p><p></p><p>Fourth, it just feels like a lazy way to develop the system that players have weirdly adopted as a good approach when it isn't (sort of a rationalizing-the-status-quo bias). If they had started with only 4 or 5 classes, this approach might have made the most sense, but they didn't & that ship has sailed. So drawing a line now and de-emphasizing classes in favor of subclasses is starting to make the whole edition feel sloppily executed.</p><p></p><p>The bottom line is that if the concept that you're imagining is a.) very interesting, and b.) broad enough that you can easily mentally conjure many different subtypes within that class, there is no reason to not take the time to develop it into a full class instead of band-aiding it as a nonsensical subclass tacked on to an arbitrarily chosen class. My personal favorite examples of this are the witch and the shaman, but there are tons of others.</p></blockquote><p></p>
[QUOTE="Einlanzer0, post: 7860705, member: 6788934"] So.... I've been feeling this for a while. While, granted, we got the Artificer in the Eberron book, there's been a long term dearth of new classes for 5e. Especially in light of the new UA, it really worries me that it appears to be because WotC thinks they can/should simply turn every new class concept into a subclass for one of the existing classes. I love subclasses, but I think that's a terrible approach, and it really needs to get called out as a problem IMO. First, it attempts to solve the (hypothetical) problem of class bloat by adding clutter within classes, which really doesn't make much sense. 5e already addresses class bloat as a potential problem by having subclasses [I]at all, [/I]but when the theme or fantasy represented within a class starts to take you all over the place with subclass options, that's an indicator we've departed from "elegant" and landed at "sloppy". As a practical concern, this makes it [I]more[/I] difficult for players to digest what their options really are. They have to reverse engineer a concept or go through a layered path-choosing process. Second, subclasses aren't multi-class friendly, so tying more and more class options to them inhibits the leveraging of multi-class rules to create a unique class concept. In other words, they result in less customization, not more. Third, there are numerous areas where it just doesn't really make thematic sense, either in terms of edition history/lore or in terms of verisimilitude. In these cases, what happens is the idea gets trapped into a set of existing class mechanics & flavor that feels arbitrary at best and cognitive dissonance causing at worst. I [B]can easily[/B] get on board with Psychic Warrior being a subclass for Fighter - because it's a perfect use of the subclass system to expand options without class bloat. I [B]cannot[/B] get on board with the base Psion being a "Wizarding tradition" because it is [I]not[/I]. One of many reasons for this is the thematic need for psionics to exist as a full-enough system to potentially replace traditional magic in a more sci-fi setting [I]based on precedents established in previous editions[/I]. Fourth, it just feels like a lazy way to develop the system that players have weirdly adopted as a good approach when it isn't (sort of a rationalizing-the-status-quo bias). If they had started with only 4 or 5 classes, this approach might have made the most sense, but they didn't & that ship has sailed. So drawing a line now and de-emphasizing classes in favor of subclasses is starting to make the whole edition feel sloppily executed. The bottom line is that if the concept that you're imagining is a.) very interesting, and b.) broad enough that you can easily mentally conjure many different subtypes within that class, there is no reason to not take the time to develop it into a full class instead of band-aiding it as a nonsensical subclass tacked on to an arbitrarily chosen class. My personal favorite examples of this are the witch and the shaman, but there are tons of others. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Really concerned about class design
Top