XP vs milestone levelling: which should I use?

Advancement is a reward signal

XP makes progress cumulative and measurable. When the next level's threshold is known, players can see how close they are, and the GM can assign points to the things the characters do. That is useful in player-directed campaigns, but the award rules teach the table what is worth doing. If defeating enemies is the only reliable source, players may reasonably treat combat as the best route to advancement.

Milestones replace a running total with defined events or accomplishments. The GM has more control over when new abilities arrive, and the whole party can advance together if that is the group's rule. The trade is that players need to understand what counts. A level granted after an unexplained stretch of play can feel like a private decision rather than progress they helped earn.

When each method fits

Start with the kind of progress you want players to notice, then account for the work it asks of the GM:

• XP A good fit when play is open-ended, the party chooses its own goals, or incremental progress matters to the group. Decide in advance which accomplishments earn points and how you will treat different routes to the same goal. This takes tracking and consistent awards, but need not mean awarding XP for kills alone.
• Milestones A good fit when the campaign has clear missions, arcs, chapters, or shared objectives and you want to set the pace around them. Tell players which kinds of developments count, and keep the party's advancement rule consistent. This avoids a running XP total, but requires the GM to make progress and delays legible.
• Neither is automatically fairer XP can favour one play style if only some activities earn points. Milestones can favour the GM's planned plot if only expected story beats count. Either method works better when players know the rule and see their choices matter under it.

A decision guide by campaign style

These are starting points, not prescriptions. A system's own advancement rules may also shape the choice:

• Open sandbox Consider XP or objective-based XP so different player-chosen goals can all move the characters forward. Milestones can work too, but make room for accomplishments the GM did not predict.
• Procedural dungeon crawl Consider XP for discoveries, treasure recovered, objectives, or encounters, depending on what you want exploration to reward. A milestone after a major site or dungeon section reduces arithmetic but makes the pace less incremental.
• Strong story arcs Consider milestones tied to clear turning points or completed objectives. If the group wants progress between arcs, show smaller steps towards the next level.
• Published adventure with expected level bands Milestones can keep advancement near the adventure's intended challenges. Structured objective XP is another option if you want more player choice while preserving a planned pace.
• Players enjoy tracking progress Use XP or a visible milestone track. Either lets players judge how their actions contribute without asking the GM for a hidden timetable.
• The group wants little bookkeeping Milestones avoid a running total. Note the next agreed trigger in the campaign record so the rule remains clear without extra arithmetic.
• Exploration should matter as much as combat Award XP for discoveries and exploration objectives, or set a milestone for reaching and resolving a meaningful site. Name the reward before play makes the choice, where practical.
• The party should stay at one level Use shared XP awards or group milestones. XP does not have to be individual, and a milestone does not have to advance the whole party unless you choose that rule.

Make the rule and the progress visible

With XP, tell players what earns it and award comparable accomplishments consistently. You can reward recovered treasure, discoveries, completed objectives, faction goals, resolved problems, or role-specific achievements. The categories matter less than the signal: if negotiation and exploration are supposed to count, make sure the award rule actually recognises them. Avoid changing point values after the fact to steer the party towards a preferred plot.

With milestones, name the kind of accomplishment that advances the campaign and track it openly. A short list of objectives or a progress clock can show that the party is moving towards a level without promising that every session produces one. Do not keep the trigger secret and then present the level as a surprise reward; the surprise is rarely worth the uncertainty about whether the players' choices mattered.

Hybrid approaches and their trade-offs

You can combine a visible reward signal with paced level-ups, but decide which part of the system controls the level:

• Objective or exploration XP Give points for stated goals, discoveries, or problems solved rather than making defeated enemies the default source. This supports varied approaches, but the GM still needs a fair way to value different accomplishments.
• A visible milestone track Mark steps towards a shared level-up as the party resolves agreed objectives. Players can see progress while the GM retains some control over the pace; define what earns a mark so the track does not become XP with hidden values.
• Per-session progress marks Give the group a mark after each session that meets an agreed condition, such as making progress on a chosen objective. This makes progress easy to track, but a fixed mark for attendance alone can reward showing up more than what happened in play.
• A set number of major accomplishments Advance after the party completes an agreed number of significant goals. It is easy to explain, though goals vary in difficulty, so decide whether each goal counts equally or whether some are worth more than one step.
• Shared XP awards Give the same points to every character for a session or objective. This keeps the XP total visible without splitting the party by attendance or individual actions, but it means personal achievements do not change level pace unless separately recognised.
• Small rewards between milestone levels Keep levels tied to campaign events, then recognise intervening play with modest non-level rewards such as a useful contact, access, reputation, or information. These give actions nearer-term consequences without quietly creating a second XP track.
• Personal rewards, shared party level Give a character-specific reward for a personal goal, such as a contact, training opportunity, or favour, while the party's level still advances together. Keep those rewards useful without making one character's mechanical power outpace the rest of the group.

How often should characters level up?

There is no useful session count for every campaign. Level frequency depends on the rules, campaign length, starting and intended ending levels, and how long the group wants to use each set of abilities before learning new ones. Decide what pace suits your table, then make the XP awards or milestone steps match it. The separate question of how often to level deserves its own guide; do not use a fixed schedule just because another campaign did.

Before choosing an advancement method

Agree on the rule before the next level is close:

• What activities should count towards advancement: combat, exploration, objectives, social accomplishments, or some mix?
• Should characters earn progress individually, or should the whole party advance together?
• Can players tell how much progress they have made and what can move them forward?
• How much tracking does the group enjoy doing between sessions?
• If a player solves a problem in an unexpected way, can that still earn the reward the group agreed on?