Back to Blog Game Design

Battle Pass Pacing: Getting Players to the Final Reward

58% of buyers of Scout Horizon's first battle pass never reached the final reward. Sales were healthy, and week-one completion looked reasonable. The failure showed up in weeks two and three: progress slowed sharply, buyers stopped engaging, and the pass began to feel unrewarding. They had not stopped caring about the game. They had lost momentum in the pass.

We rebuilt the track for the second version, and completion rose meaningfully. The first design failure was structural. It was not caused by weak rewards.

Where Dropout Starts, and Why Rewards Were Not the Cause

When completion is low, the usual diagnosis is that the final reward is not attractive enough. Our Scout Horizon results pointed elsewhere. Buyers who dropped out in weeks two and three consistently described slow progress, a distant next reward, and daily sessions that felt like work instead of play.

Those complaints describe milestone cadence and perceived distance, not reward quality.

The first Scout Horizon pass had genuinely strong rewards. Its final tier was a cosmetic set players had requested. The issue was the track layout: milestones 14 through 22 of the 30 total milestones contained no rewards. Players still earned XP in that section, but the system gave them no reward acknowledgment across the entire stretch. In a progression track, that creates a psychological desert.

The XP Curve and Milestone Cadence Mismatch

A fixed XP requirement per milestone is straightforward to build and explain. It becomes problematic when player session frequency naturally falls during the second and third weeks of a season.

During week one, buyers are exploring seasonal content, highly engaged with the pass, and playing more often. XP income is high, milestones arrive quickly, and frequent rewards establish a positive first impression.

By weeks two and three, session frequency settles near the player's natural baseline. On Scout Horizon, the median player's week-one frequency was 40% higher than baseline. XP income therefore fell, while milestone requirements stayed unchanged. By week two to three, time-to-milestone was 2.5x longer than in week one.

That experience does not tell the player that their play frequency declined. It feels as if the pass became harder. The player has not rejected the game or decided that the rewards are poor. The reward rate has slowed without a clear signal, so ordinary play appears to stop producing progress.

The Mid-Track Gap Problem

The reward-free span from milestones 14 through 22 was not intentional. It came from how we filled the 30-milestone track. We concentrated the strongest rewards at the start, middle, and end: dense early rewards to establish value, premium cosmetics near the finish, and insufficient spacing in the remaining middle section.

At week-one pace, the gap is tolerable because milestones pass quickly. At natural week-two pace, moving through that section takes nearly two weeks of normal play. Internal Bold Games measurement of milestone-at-churn data from the first pass season showed that this was where we lost most of the dropout cohort.

The obvious fix was to add intermediate rewards. The design constraint was choosing rewards that mattered in the moment without competing with the premium end rewards or making the total reward volume so high that the pass lost its specialness.

The Fix: Mid-Track Reward Injection

For the second pass, we placed three intermediate rewards inside the former dead zone, at fixed positions 15, 18, and 21. They were useful consumables, including event energy refills and currency bags, rather than premium cosmetic items. Their purpose was utility without competing with the cosmetic rewards on aesthetic value.

The change worked mechanically and psychologically. In the middle of the track, a player could now see a reward within one to three milestones of their current position. Perceived distance changed from "I am 8 milestones from the next reward" to at most "I am 2 or 3 milestones away." The track responded to effort again.

We also tuned XP for the period when session frequency normally declines. Milestones 11 through 22 require approximately 15% less XP than milestones 1 through 10. Players do not see this as a tuning rule. It offsets the frequency drop and keeps actual time-to-milestone roughly constant across the season for the median player.

What Changed After the Redesign

The second pass had a substantially higher completion rate than the first, and dropout during the week-two and week-three window fell significantly. Internal Bold Games measurement of buyer behavior across consecutive seasons also showed that players who completed the second pass were more likely to purchase the third pass at launch. Completing the pass made the purchase feel worthwhile, which supported the next purchase.

We also saw fewer support contacts from players who believed they could not finish in time. The first pass produced a steady stream of messages from buyers who felt behind and frustrated. The second pass produced almost none.

Completion Rate Is Not the Only Metric

We are not saying every studio should optimize a battle pass only for completion rate. A pass that is trivially easy to finish can lose its sense of occasion, and the final reward can lose value if nearly every buyer receives it. Lower completion can be a valid design choice when players who stop short still feel that the value they received matched what they paid and played.

We are saying the specific problem is not low completion in isolation. It is the buyer who plays regularly, reaches the middle of the track, and concludes that the pass failed to reward that effort. These players did not simply choose to stop. They encountered a structural pacing problem and read it as a failure of the game to recognize their play. That interpretation can damage spending sentiment regardless of the final completion rate.

For Scout Horizon, the practical lesson was to measure time between meaningful rewards, not just the final completion percentage. The middle of the track was the failure point, and fixing its cadence addressed the problem.