Lesson 15: Monetization & In-Game Economy

Your battle royale is playable and secure; next you need a sustainable way to earn revenue and keep players progressing. This lesson covers how to design and implement an in-game economy: currency, battle pass, item store, and pricing that feels fair and supports live operations.

By the end of this lesson you will have a clear economy design, a plan for currency and rewards, and practical steps to implement a battle pass and store in Unreal without breaking balance or trust.

Fish - Dribbble

Image: Fish by Dribbble Artist

What You'll Learn

By the end of this lesson, you will be able to:

Define your economy pillars – premium currency, earnable currency, battle pass, and store
Design a battle pass – tiers, progression, free vs. premium track, and season cadence
Plan an item store – rotations, pricing, and how it ties into currency and analytics
Implement economy in Unreal – server-authoritative currency, purchases, and rewards
Balance fairness and revenue – avoid pay-to-win and keep progression satisfying

Why This Matters

A well-designed economy keeps players engaged and funds ongoing development:

Retention – Battle pass and daily rewards give reasons to return; currency and unlocks create medium-term goals.
Revenue – Premium currency, battle pass, and store items generate income without forcing pay-to-win.
Live ops – Seasons, store rotations, and limited-time offers give you levers for events and content drops.

Poor economy design (e.g. pay-to-win, grind that feels unfair, or confusing currencies) drives players away and hurts both retention and revenue.

Prerequisites

Before starting this lesson, make sure you have:

Completed Lessons 1–14 in this course
A battle royale project with matches, combat, and (optionally) analytics in place
A backend or service that can store player progression and process purchases (e.g. PlayFab, custom API)
Basic familiarity with replication and server authority from earlier lessons

Step 1: Define Your Economy Pillars

Decide the main pieces of your economy before implementing.

Premium currency (e.g. coins, gems)

Bought with real money only.
Used to buy battle pass, store items, or convenience (e.g. rerolls).
Never earned in-match in a way that would unbalance combat.

Earnable currency (e.g. credits, XP)

Earned by playing: match completion, challenges, battle pass free track.
Used to unlock cosmetics, battle pass tiers, or non–pay-to-win items.
Lets non-spenders still progress and feel rewarded.

Battle pass

Seasonal progression with free and premium tracks.
Rewards at tiers (cosmetics, earnable currency, premium currency).
Time-limited (e.g. 10–12 weeks) to create urgency and a clear season cadence.

Item store

Rotating or permanent offers: skins, emotes, bundles.
Purchased with premium or earnable currency.
Can include limited-time offers to support live ops.

Pro Tip: Start with two currencies (premium + earnable) and one battle pass. Add store rotations and more reward types once the core loop is stable.

Mini-Task: Economy One-Pager

Write a one-page doc: names of each currency, how they are earned or bought, what they can purchase, and one sentence on how the battle pass and store fit in. Share it with your team (or future you) before coding.

Step 2: Design the Battle Pass

Tiers and progression

Define total tiers (e.g. 50–100).
Progression: XP or “battle pass points” from matches, challenges, and daily/weekly goals.
Same progression fills both free and premium tracks; premium unlocks extra rewards per tier.

Free vs. premium track

Free track – Earnable currency, some cosmetics, maybe a small amount of premium currency so free players can eventually buy the pass.
Premium track – Exclusive cosmetics, more currency, and a clear “premium only” identity.
Premium is unlocked with a one-time purchase (e.g. 1,000 premium coins) per season.

Season length and cadence

Typical: 10–12 weeks per season.
Plan overlap: when one season ends, the next starts (or a short off-season).
Use seasons to tie into events and store rotations.

Pro Tip: Avoid making the battle pass feel like a second job. Cap daily/weekly gains if needed so committed players can finish without requiring unhealthy play time.

Step 3: Plan the Item Store

What you sell

Cosmetics only (skins, emotes, weapon charms) keeps the game fair.
Optionally: battle pass tier skips, XP boosts (cosmetic or progression only, not combat power).

Store structure

Featured – Rotating or limited-time items.
Permanent – Always available (e.g. core skin set).
Bundles – Multiple items at a discount to increase average order value.

Pricing

Price in premium currency.
Use price points that encourage using full currency packs (e.g. 500, 1,000, 2,500) while avoiding obvious “leftover” frustration.
Reference similar games and your target audience; test and iterate.

Rotation cadence

Weekly or biweekly rotations give something new and support live ops.
Limited-time items create urgency; use sparingly so they stay special.

Common mistake: Selling power (e.g. stronger weapons or stats). In a competitive battle royale, pay-to-win quickly kills trust and retention. Keep monetization to cosmetics and convenience.

Step 4: Implement Economy in Unreal (Server-Authoritative)

All currency and purchases must be validated and applied on the server.

Currency storage

Store per-player currency (premium and earnable) in your backend or persistent store (e.g. PlayFab, custom DB).
Cache in memory on the game server for the session; sync from backend on login and write back on change.

Granting currency

Earned – After match end or challenge completion, server calculates reward and calls backend to add currency.
Purchased – Payment runs through platform (Steam, Epic, etc.) or your payment provider; webhook or callback notifies your backend; backend adds premium currency and confirms to client.

Spending currency

Client requests “purchase item X” or “unlock battle pass tier Y”.
Server checks balance, deducts currency, grants reward (e.g. item unlock, battle pass tier), and returns success/failure.
Replicate result to client; update UI from server response.

Battle pass progression

Server tracks “battle pass XP” or “season points” per player.
After each match (or challenge completion), server adds points and then computes current tier from total points.
When tier increases, server grants free-track rewards; if premium unlocked, grants premium rewards too.
Store tier and claimed rewards in backend so they persist across sessions.

Pro Tip: Never trust the client for balance or purchase validation. Always validate and apply on the server and persist in a durable store.

Step 5: Balance Fairness and Revenue

Fairness

No purchasable combat advantage.
Progression (battle pass, earnable currency) should feel achievable for free players, even if slower.
Clear rules: what is premium-only, what is earnable, and what is limited-time.

Revenue

Battle pass and cosmetics are the main levers.
Limited-time and “must have” cosmetics can drive spikes; don’t overuse or players tune out.
Use analytics (from Lesson 14) to see what converts and what drives retention.

Communication

In-game and in store: show prices in premium currency and what each purchase grants.
Explain battle pass: how progression works, what’s free vs. premium, and when the season ends.

Troubleshooting

Issue	What to check
Currency not updating after match	Server granting logic and backend write; confirm client is reading from server response or replicated state.
Purchase not granting item	Payment callback and server-side grant; idempotency so double callbacks don’t double-grant.
Battle pass tier wrong	Formula for points-to-tier; persistence of points and tier in backend; cache invalidation on server.
Players report “pay-to-win”	Audit all purchasables; remove any combat advantage; communicate clearly.
Store or pass feels grindy	Tune XP/points and rewards per tier; cap daily gains so completion is feasible without burnout.

Summary

Economy pillars – Premium and earnable currency, battle pass, and store; document in a one-pager before implementing.
Battle pass – Tiers, free vs. premium track, progression source (matches, challenges), and season length; keep completion achievable.
Store – Cosmetics and convenience only; featured and permanent sections; pricing and rotation cadence.
Implementation – Server-authoritative currency and purchases; persist in backend; never trust client for balance or grants.
Fairness – No pay-to-win; clear rules and communication so players trust the economy.

In the next lesson you will focus on Testing & Quality Assurance: test plans, automation, and release checks so your battle royale is stable and ready for launch.

Bookmark this lesson and refer back when you add new currencies, store items, or battle pass seasons. For deeper reading, see PlayFab Economy and platform-specific purchase docs (Steam, Epic) for your target stores.

Frequently Asked Questions

Should I use one currency or two?
Two is standard: premium (real money) and earnable (play time). It keeps real-money purchases clear and gives free players a path to earn rewards and sometimes premium content.

How long should a battle pass season be?
10–12 weeks is common. Shorter can feel rushed; longer can drag. Align with your content and event schedule.

Is it okay to sell XP or progression boosts?
Yes, if they only affect non-combat progression (e.g. battle pass XP). Never sell combat power in a competitive battle royale.

How do I prevent duplicate or fraudulent purchases?
Process payments and grants on the server/backend only. Use idempotency keys for purchase callbacks so the same payment event doesn’t grant twice. Validate amounts and items server-side.

What if players hoard currency and don’t spend?
Offer desirable limited-time items and clear value in battle pass and bundles. Avoid pressuring spend; focus on making purchases feel worthwhile and fair.