It depends upon how you define "fighting", "skill", and "spell" - but to an extent, yes. However, this is not guaranteed to be an efficient way to deliver class concept. Right now, the gish (fighting-spell) concept (where spellcasting and weapon/melee fighting are expected to be used in combat in significant amounts) exists in just the PHB as: Valor Bard, War Cleric, Moon Druid, Eldritch Knight, Warrior of the Open Hand Monk, all Paladins, all Rangers, and Blade Tome Warlocks. We'll also have Songblade Wizards and other options coming too. Is one base class the best way to deliver what each of these options delivers? Or do they benefit from more specialization? I'd say the organization of the concept works better when we divide these into separate classes....At most you have a fighting class, skill class, spell class; then you add the combinations of each: fighting-skill, fighting-spell, skill-spell, and fighting-skill-spell, for a total of seven "core" classes.
Every class concept can be expressed by one of those seven once subclasses, etc. are added.
That's only because Laser LLama doesn't have to stay true to backwards compatibility.Laser Llama's Ranger class looks a lot better than the 2024 Ranger IMO.![]()
I basically say D&D Goldilocks Class name is about 20.Or when a homebrewer like Laser Llama creates a class whose concept has been talked and implemented about for years but hasn't quite satisfied that itch. I am talking about his Magus class, which is the arcane counterpart of both the Paladin and Ranger classes
Then there is the stuff that homebrewers like Laser Llama come up with such as the Magus and its' 12 archetypes.Right now, the gish (fighting-spell) concept (where spellcasting and weapon/melee fighting are expected to be used in combat in significant amounts) exists in just the PHB as: Valor Bard, War Cleric, Moon Druid, Eldritch Knight, Warrior of the Open Hand Monk, all Paladins, all Rangers, and Blade Tome Warlocks
Most of PF1 classes are subpar and niche and frankly, just bloat. In classed systems, few good classes, where each one covers specific niche and doesn't step on other classes toes is better than dozens of very niche classes with large overlaps and small differences. But it's more matter of taste. Some people like to mix and match diy, some like prebuilt stuff.Currently 5e has fewer classes than PF2, which currently sits at 25 classes (minus their archetypes). PF1 had 36 classes. Level up just has 15 classes.
One class with each of these options (including Paladin and Ranger, really, and probably Artificer?) as subclasses is a great way to deliver a broad range of concepts in a single class chassis with subclasses.It depends upon how you define "fighting", "skill", and "spell" - but to an extent, yes. However, this is not guaranteed to be an efficient way to deliver class concept. Right now, the gish (fighting-spell) concept (where spellcasting and weapon/melee fighting are expected to be used in combat in significant amounts) exists in just the PHB as: Valor Bard, War Cleric, Moon Druid, Eldritch Knight, Warrior of the Open Hand Monk, all Paladins, all Rangers, and Blade Tome Warlocks. We'll also have Songblade Wizards and other options coming too. Is one base class the best way to deliver what each of these options delivers? Or do they benefit from more specialization?
It would just depend on how much detail / depth you feel (as a player) you need to make your concept a reality. Personally, I don't need much so I prefer a simpler design.I'd say the organization of the concept works better when we divide these into separate classes.
Concerns about mechanical balance, or even more about so-called "bloat" are not my primary concern in RPG design, or even my secondary concern.We'll never know if people instead default to more and more classes.
It is harder to balance classes because they are the "everything" picture. If you start with a common chassis, and develop a subclass or whatever to flesh out a concept, balance is far easier to acheive. So, the fewer core classes, the better. If you have too few, of course then the dynamic shifts the power-focus to the subclasses, feats, or whatever is used to create the desired concept.
I agree with the Goldilocks concept. I wouldn't want a single "adventurer" class, but I also don't think a dozen or more classes really is necessary and good design, either. How many posts talk about making this class or that class a subclass of something else??
All of those exist in various 3pp. No need for WotC to "step up".That's only because Laser LLama doesn't have to stay true to backwards compatibility.
I basically say D&D Goldilocks Class name is about 20.
The main classes massing are
Those 6 plus the Artificer.
- Bender/Elementalist - Noncaster who has more fine control of the elements
- Chosen/Exemplar- Warrior version of Warlock
- Gish/Magus - Arcane Counterpart of Paladin/Ranger
- Psion- A caster heavy focused on the mental side of magic and the mental side of the occult
- Summoner- A caster who sacrifices his or her power/actions for their summons
- Warlord/Marshal- The Martial warrior with Tactical, Mental, and Healing effect
then try defining what you think it is then?Which varies A LOT. Sort of my point.
Why more when less works?
LOL I wouldn't dare! My definition is different from yours, and the next definition would be different as well, and the next, and so on.then try defining what you think it is then?
If it functions, it works, doesn't it? I mean, I don't have an entire design team at my disposal to flesh this out, but the concept seems sound to me.we have not established if less works just that the game could function, is such a state