How should class names change as a class evolves?
They should climb, so readers feel each evolution as a step up. In most LitRPGs a class isn't one name, it's a path: a base class at the start, an advanced class at the first evolution, and something rare or unique once the MC breaks the mold. Readers enjoy that climb, and the names are how they feel it. Plan at least the next step before you name the first one.
A simple rule holds up well: base classes are familiar job words (Archer, Mage, Squire), advanced classes add a theme word (Ember Archer, Grave Knight), and unique classes change shape entirely (Ash Sovereign, Herald of the Last Dawn, Stormbinder). Each step should keep something of the last, so the reader can see where it came from.
What naming patterns fit each class tier?
- Base: one familiar word, sometimes with a rank: Apprentice Alchemist, Spearman, Scout.
- Advanced: theme + base: Blood Mage, Rune Archer, Thorn Warden. The theme word is usually the MC's signature element or trait.
- Compound: Spellblade, Voidwalker, Tidecaller. Good for hybrids that don't fit a single job.
- Unique: title-like: Sovereign of Ash, Paragon of Ten Thousand Blades. Rare by design, so one per major character at most.
What class-naming mistakes do readers notice?
- Evolving into an unrelated name. If the Ember Warden becomes a Frost Duelist, readers will want to know why. Make the reason a story beat.
- Giving every side character a unique class. If everyone is special, nobody is. Most of the cast should have plain base and advanced classes.
- Classes that don't match what they do. A Necromancer who never raises anything will get comments.
- Losing track of who has what. Ten party members across three evolutions is thirty names to keep straight.
How do you keep track of who has which class?
Keep a small table: class, tier, what it unlocks, and the chapter each character took it. When a reader asks in the comments when the MC got his class, you want the answer in seconds, not a reread of sixty chapters.