Start with one artifact, not ten hidden switches
The cleanest no-mod progression systems usually begin with a single identity item: a fang, a gear heart, a class token, a cursed book, or a relic core. That item becomes the visible anchor for the character's path. It can store hidden state in custom_data, carry a readable name and lore, connect to a custom model, and give players one thing to understand instead of a scattered trail of commands.
This pattern also helps staff. When something breaks, you inspect the artifact and its state. You do not need to remember whether the upgrade lived in a scoreboard, a command block, a region flag, and a Discord note at the same time.
Progression needs friction
Permanent free power feels exciting for one week and then becomes background noise. The systems that survive a season usually include some kind of upkeep loop: fuel, charges, cooldowns, repair, corruption, oxidation, exhaustion, hunting trophies, ritual components, or social access. The point is not to punish the player. The point is to keep power connected to the world.
A mechanical class might require copper upkeep. A hunter path might require trophies from specific mobs. A magical book might need ink, sacrifice, or time near a ritual structure. These loops give other players reasons to interact with the class instead of treating it as private menu power.
Make upgrade paths readable
Players should be able to explain their next milestone in one sentence. A good path might be linear, branching, or adjacency-based, but it should never feel like a spreadsheet that only the plugin author understands. Use short upgrade names, visible lore, and a small number of meaningful choices.
- Linear: safer for a first season, easy to balance, easy to teach.
- Branching: better for class identity, but needs stronger limits.
- Adjacency: great for mechanical or ritual systems, but it must have a clear visual map.
Restrictions are part of the fantasy
A class becomes memorable when it says no. If every path can sprint, fly, heal, deal burst damage, and ignore danger, the system loses shape. Restrictions create identity: the machine fears water, the hunter loses progress on death, the mage cannot wear heavy armor, the cursed relic grows stronger at a cost.
Write restrictions as design rules, not as afterthoughts. They tell players how to roleplay the power and give staff a healthier balancing lever than simply reducing numbers after launch.
Build admin controls before launch
The first version should include safety rails. Staff need ways to inspect state, reset a broken item, disable an ability, tune costs, and remove a path from a player without destroying the whole inventory. If these controls do not exist before the first public test, every balance issue becomes emergency surgery.
At minimum, prepare commands or procedures for: granting the artifact, reading its state, changing its level, clearing cooldowns, disabling an ability, and logging major upgrades.
Connect progression to your resource pack
Progression feels deeper when the item changes visually. A first-stage relic can look plain, then gain cracks, symbols, metal parts, color shifts, or animated-looking accents as the path grows. You can build the visual side with the resource-pack generator and command-facing items with the custom item builder.
FAQ
Do I need a mod for a deep class system?
No. Mods can help, but Paper plugins, commands, custom items, resource packs, and careful design can already create a strong progression fantasy.
Should every player path use a custom item?
Not always, but one anchor item makes state, visuals, and admin support much easier to reason about.
What is the biggest balancing mistake?
Giving permanent power with no cost, no downtime, and no staff controls. It feels generous at first and becomes painful later.