Machinations

Balancing a battle pass

Learn how to balance a Battle Pass- we will only be considering the balance between the battle pass’ duration and player level progression.

For the purpose of this example, we will be using the following generic battle pass model.

When balancing a battle pass, there are several factors that need to be considered. For a detailed description of the battle pass mechanic and how to model and balance it, please refer to the Battle Passes and how to balance them article our resident Diagram Architect, Cezar Cocias, wrote on Gamasutra.

Warning

In this example we will only be considering the balance between the battle pass’ duration and player level progression.

The Model

The initial (unbalanced) battle pass model in Machinations looks like this:

Open the diagram: Interactive diagram for Balancing a Battle Pass

Hit Play in the embedded diagram above to follow along.

  1. We have 3 different Daily Quests: Quest Type 1-3 represented by the purple, red and brown Random Gates with Chance outputs. The probable outcome on the Resource Connection for each Gate represents the Quest’s chance of being completed. If completed, each Quest yields a reward: the construction made up by the Converters labeled Rewards Tier 1-3 and their respective Resource Connections.
  2. It takes 100 points for one battle pass level (the Pool Battle Pass Level), and the maximum level is capped at 25 – the State Connection labeled Level Cap
  3. The battle pass lasts for 40 days, regardless if the player hits the level cap or not. This condition is verified by the State Connection labeled Expiry Condition, which will activate the End Condition labeled Battle Pass Expires, as soon as the Days Pool reaches 40.

Battle Pass Duration

There is no single rule that dictates how long a battle pass should last. Most of them opt for a duration between one or two months (Genshin Impact for instance has a 40-days battle pass), while some extreme cases opt for longer cycles (like Dota 2’s battle pass that can go up to half a year).

As battle passes do have a cycling system (when one ends, a new one begins, even if not immediately), it is important to determine how long you want your own battle pass’s cycle to be. A lower duration increases the chance of individual purchases, as players can have a month where they are more active in-game and choose that month as a good time for a battle pass, while a longer period can give you better prices and better retention for those players that do opt to make the commitment.

Balancing player level progression

Open the diagram in your Machinations (use the Open in my Machinations button on the embedded diagram), and open up the Chart. Pressing Forecast with the number of Plays set to 20 will make 20 Plays of the model and we can quickly have a look at the Chart and see how our player is doing.

A Forecast of 20 Plays of the battle pass model, 40 days each: the Battle Pass Level rises from 1 to a median of 19 on day 40, and every Play ends between level 17 and level 21A Forecast of 20 Plays of the battle pass model, 40 days each: the Battle Pass Level rises from 1 to a median of 19 on day 40, and every Play ends between level 17 and level 21

We can see here that our player averages a level of about 19 when the battle pass ends (40 days pass).

There is a multitude of ways in which we can adjust that. We could:

  1. Increase the chances of quests being completed, which translates into making those quests more accessible in-game
  2. Increase the rewards that each quest gives out
  3. Add extra quests, or make the level requirement lower

Let’s first double the rewards, by modifying the Labels on the Resource Connections going out of the Rewards Converters.

The battle pass model with its three Quest gates and Rewards Tier converters after the rewards are doubled: the Grant connections now pay 30, 50 and 110 points into Battle Pass PointsThe battle pass model with its three Quest gates and Rewards Tier converters after the rewards are doubled: the Grant connections now pay 30, 50 and 110 points into Battle Pass Points

Making a Forecast of 20 Plays with the adjusted parameters, we can see our average player now takes about 28 days to get to the max level, and the final 12 battle pass days are wasted. Normally that wouldn’t be a problem but for a 40-day battle pass, that’s almost a third of the total time.

A Forecast of 20 Plays after the rewards are doubled: the median Battle Pass Level reaches the cap of 25 around day 28 and stays there for the rest of the 40 daysA Forecast of 20 Plays after the rewards are doubled: the median Battle Pass Level reaches the cap of 25 around day 28 and stays there for the rest of the 40 days

Depending on each game, battle passes usually have two approaches. Either it’s fairly easy to hit the level cap, provided you are an engaged player, and you can finish some days before the pass ends (not a third of the total time though) or it is made so only the most active players can reach the level cap.

But instead of fiddling with the quest rewards, we can also have a look at the level cap. The way rewards are now we are going way over the limit, but if we increase the level cap that won’t be an issue. Let’s try a level cap of 40.

Battle Pass Points converts 100 points into a level through the Level Up converter, and the Level Cap state connection now enables Level Up only while the level is below 40Battle Pass Points converts 100 points into a level through the Level Up converter, and the Level Cap state connection now enables Level Up only while the level is below 40
A Forecast of 20 Plays with the level cap raised to 40: the median Battle Pass Level climbs steadily to 37 on day 40, with every Play between level 33 and 39A Forecast of 20 Plays with the level cap raised to 40: the median Battle Pass Level climbs steadily to 37 on day 40, with every Play between level 33 and 39

Now our player reaches level 37 on average, which is very close to where we actually want it to be. Great success!

Though there are many ways in which we can address the length, quest reward system, or level requirements, they all kind of fall in the same part of the balancing process, which is battle pass length (and quests since we are also talking about the likelihood of them being completed).

It’s also a matter of iteration: Forecast, change parameters, Forecast again, make changes again. One of the Machinations features that support this heavily iterative process is the list of Plays and Forecasts on the left of the chart panel. It saves the Forecasts performed on a model, grouped by scenario (each edit of the model starts a new one), and enables you to compare Forecast outcomes for different versions of your diagram and to see the one that yielded the best outcome for your purpose. This also works collaboratively for diagrams shared with your teammates: the list for shared diagrams can also display the Forecasts performed by other team members.