5e Mistakes: Spells and Classes

Storyline (what the video covers)

• The video is not about a specific in-game storyline. Instead, it discusses D&D 5e system design and how a particular design choice affects gameplay and balance over campaigns—especially at high levels.
• The “plot,” so to speak, is the historical shift from:
  • Earlier editions (AD&D/basic), where spell power and design intent differed greatly by class (cleric vs. wizard), to
  • 5e’s approach, where spell level is treated as the main balancing factor, reducing differences between spell lists.

Gameplay highlights / what the mistake impacts

Older design model (AD&D/basic)

• Cleric spells skewed toward passive/utility/control:
  • problem-solving, buffs, and situational tools.
• Wizard/magic-user spells were damage/combat-turning “glass cannon” options:
  • Examples include Fireball, Lightning Bolt, Magic Missile, and Shield—often strong enough to swing encounters.
• Wizards were also more vulnerable:
  • earlier rules punished being interrupted mid-cast.

5e design “root mistake”

• The argument is that 5e effectively treats “a spell is equal to any other spell of the same level”.
• In practice, the “level slot” becomes the balancing unit—meaning spells of the same level are assumed to be interchangeable.
• This assumption is later exploited by new mechanics (e.g., feats) that let characters access spells typically associated with other classes.

Where the system breaks in practice

• The speaker points to modern design (example: a new book Arcana Unleashed) that includes feats allowing casters to gain access to spells from typically “legacy wizard lists” (e.g., Shield, Fireball).
• Problem: even if the design assumes third-level = third-level, historical precedent suggests some spell lists contain “broken” legacy options that are disproportionately powerful.

Key examples mentioned

• Problematic “legacy wizard” high-level spells called out include:
  • Force Cage
  • Wall of Force
• The speaker contrasts:
  • a cleric-style buff spell (example mentioned: Prayer granting bonuses)
  • versus wizard-style combat-ending power (example: Fireball)
• The claim: if players can access both using the same spell slot level, they’ll almost always prefer the wizard option.

Strategies / design advice (what to do instead)

The speaker doesn’t offer a player “build guide” so much as design principles and balance strategies:

• Don’t treat all spells of the same level as equal across classes, especially when some classes historically receive more encounter-warping options.
• Better long-term design would be to either:
  • Rebalance legacy spells if they remain interchangeable, or
  • Make spell lists fundamentally different, so “wizard brokenness” can’t be swapped onto every class.

A suggested re-design approach (conceptual)

• Wizard-like classes
  • Keep the “vulnerability” identity, but accept that wizard spells are consistently the most powerful.
• Sorcerer
  • Make it lower-risk in feel, with more distinctive “casting style”:
    • more randomness or more attack-roll–centered casting,
    • emphasizing “lashing out” rather than procedural spell outcomes.
• Warlock
  • Prefer at-will identity (no daily power tracking in the proposed concept).
  • Improve distinctiveness through exclusive mechanics and subclass-pact–flavored cantrips/features:
    • e.g., Eldritch Blast as one option rather than the default funnel-all.
• Cleric
  • Lean into “warrior priest” fantasy.
  • Example proposed default: cleric spells as bonus actions, enabling “bashing with a mace” as the primary feel.

Alternative risk model (from another game)

• The speaker cites Shadowed Arc, where casting uses a success roll / risk model:
  • you might fail to cast and do nothing,
  • or lose access for the day.
• The point: if spells are inherently powerful, some form of casting risk can reduce free exploitation.

Additional gameplay consequence the speaker dislikes

• If spell pools become too universal:
  • more characters effectively become spellcasters, and
  • campaigns can become less fun when “everyone can take the same powerful control/broken spells.”
• The speaker describes a prior experience:
  • a player intentionally chose unusual but strong control spells that shut down enemies repeatedly (examples implied include conditions like being unable to move, blinding, etc.).
  • it was funny at first, but became boring because fights turned into the same control-lock routine.

Final takeaway

• The central lesson: 5e’s spell interoperability model (“slot level = spell power”) collides with the reality that spell lists include historically unbalanced legacy options, leading to problematic builds and DM reluctance to run high-level content.
• The speaker argues that separating class identities more strongly would have produced:
  • more distinct, replayable classes, and
  • a longer-lived edition.

Mentioned gamers / sources (at the end)

Sources / referenced games & materials

• Arcana Unleashed (new D&D book mentioned)
• Shadowed Arc
• Wizardry: Proving Grounds of the Mad Overlord (and sequels mentioned)

Named individuals

• No individual “gamers” were explicitly featured by name in the subtitles.
• The only explicit “gamer” reference is a general statement like “I used to play Overwatch,” with no specific person credited.
• The “Wizardry” reference includes “the version I played back in the ‘80s,” with no author/developer named.