Playing Non-Standard Character Classes and Archetypes

Non-standard character classes and archetypes sit at one of the most interesting fault lines in tabletop RPG play: the gap between what a game's rulebook officially supports and what a player actually wants to explore. This page covers what non-standard options are, how they function mechanically and narratively, the situations where they appear most often, and how players and Game Masters can make smart decisions about whether to allow or adapt them.

Definition and scope

A "non-standard" class or archetype is any character option that falls outside a game's core rulebook and has not been officially playtested and approved for the specific edition or campaign in question. The category is broader than it first appears.

In Dungeons & Dragons 5th Edition, Wizards of the Coast publishes official expansions — Xanathar's Guide to Everything, Tasha's Cauldron of Everything, Mordenkainen Presents: Monsters of the Multiverse — that introduce subclasses beyond the Player's Handbook. These are technically non-core but are considered official. Then there is the vast landscape of third-party content: Kobold Press's Tome of Heroes, MCDM Productions's Flee, Mortals!, and thousands of individual designers publishing on the Dungeon Masters Guild. Beyond official third-party, there is homebrew: rules written by players or GMs themselves, ranging from a paragraph scribbled in a notebook to elaborately formatted PDF supplements.

Pathfinder 2nd Edition (published by Paizo) handles this through its Archives of Nethys — a free, comprehensive rules database that makes the line between "core" and "supplemental" nearly invisible for players who know where to look. Paizo releases classes, archetypes, and ancestry feats across hardcover books and free web supplements, and the Archives consolidates all of it.

The scope of "non-standard" depends entirely on table context. A GM running a published adventure module with strict source restrictions may consider anything beyond the Player's Handbook non-standard. A homebrew campaign with permissive rules might treat every official Paizo or WotC product as baseline.

How it works

Mechanically, non-standard classes and archetypes work the same way standard ones do — they define hit dice, proficiencies, feature progression, and (where applicable) spellcasting. The difference is in vetting. Official classes have been through internal playtesting pipelines. Third-party and homebrew options have not been filtered through those same processes, which means the balance assumptions may diverge from what the core game expects.

Three factors determine how a non-standard option performs at the table:

1. Power curve alignment — Does the class's damage output, survivability, or utility spike above or below the party at the same character level? A Fighter with the Action Surge feature hitting twice at 5th level is the baseline D&D 5e designers calibrated around. A homebrew class granting three attacks plus a full spell slot at the same level almost certainly exceeds that envelope.
2. Narrative integration — Does the fiction behind the class make sense in the campaign's setting? An Artificer (character creation basics covers the broader concept) is mechanically fine in the right world but breaks immersion in a low-magic setting where gunpowder doesn't exist.
3. Rule interaction surface — Complex options with many moving parts (multiclassing, feats, conditional triggers) create more opportunities for unintended combinations. Simpler homebrew tends to cause fewer table disputes.

Common scenarios

Non-standard classes appear most often in three contexts.

Setting-specific campaigns are the most common driver. A GM building a campaign around a specific genre — maritime adventure, body horror, political intrigue — may find that core classes don't represent the fiction well. Third-party publishers like Ghostfire Gaming (Grim Hollow) and EN Publishing (Level Up: Advanced 5th Edition) have built entire product lines around filling these gaps.

Player expression needs are the second driver. A player who wants to play a gunslinger in a Renaissance-era setting, a symbiote-bonded warrior, or a devoted priest of a homebrew deity may find no satisfying official option. This is where resources like the Dungeon Masters Guild become practical tools rather than curiosities.

System conversion is the third. Players migrating from one edition to another — 3.5 to 5e, for instance — sometimes want to replicate a beloved character concept that didn't survive the transition intact. The Pathfinder RPG community developed an entire conversion culture around this, partly because Pathfinder 1st Edition was itself a conversion fork of D&D 3.5.

Decision boundaries

The most useful framework for deciding whether to allow a non-standard option distinguishes between mechanical risk and narrative risk — and recognizes they require different mitigation strategies.

Mechanical risk is managed through a trial period: allow the class for 2–3 sessions and flag obvious power outliers before they become entrenched. Comparing the option's features against a same-level character from a system-adjacent official class is a fast diagnostic. If a homebrew Warlord class is doing what a Battlemaster Fighter does, plus three additional features, the gap is probably unsustainable.

Narrative risk — the risk that the character concept disrupts the table's shared fiction — is managed through conversation before session one, not rule adjustments during play. The tabletop RPG safety tools framework, developed by designers including Beau Jágr Sheldon (the X-Card) and Dr. John Stavropoulos, addresses player-to-player comfort, but the same principle applies to concept compatibility.

The tabletoprpgauthority.com homepage is a useful starting point for players who want the broader context of how character options fit into the full arc of tabletop play — from system selection to long-term campaign management.

One structural reality worth internalizing: no class is inherently broken, and no class is inherently safe. Every option exists in relation to a specific group, a specific GM style, and a specific set of expectations. The decision boundary isn't "official vs. unofficial" — it's "does this serve the table?"