Fighter Pilot: Iron Bird
Economy & Progression Design — Full Breakdown
Economy & Progression Design — Full Breakdown
Jump to:
The Economy
•
Design Goals
•
Core Systems
•
Problems Solved
•
My Approach
•
Results
•
Full Project Page
What Is the Economy?
Fighter Pilot: Iron Bird runs on a seasonal battle pass economy: players earn XP through gameplay and unlock rewards across a fixed tier structure over a limited season window. Unlike static progression, this system is time-bound, behavior-sensitive, and retention-driven. The system must support both casual playes logging in a few times a week and dedicated players who play daily, without allowing either group to break the progression curve.
CORE COMPONENTS
XP
→
progression currency earned per match, quest, and bonus event
Battle Pass Tiers
→
sequential unlock structure (1–50) gating cosmetic and progression rewards
Season Length
→
fixed time window (4–6 weeks) creating the primary scarcity constraint
Reward Structure
→
cosmetic and progression incentives tied to specific tier milestones
The core loop driving every session:
Play Match
→
Earn XP
→
Progress Tiers
→
Unlock Rewards
→
Return Next Session ↺
EXTENDED DAILY LOOP
Daily play → XP gain → tier advancement → reward unlock → new goals surface → player returns next session. The system only works if that last step, returning, keeps happening across the full season length.
Design Goals
Design Inspiration:
The battle pass structure was modeled on proven seasonal economy frameworks from Call of Duty: Warzone and Fortnite, both of which use non-linear XP curves to sustain engagement across player segments. The core design problem of preventing early exhaustion without padding mirrors the challenge those teams solved by front-loading accessibility and steepening resistance in the mid-to-late tier range. The forward-only live fix approach was informed by how live-service teams like Bungie (Destiny 2) handle mid-season economy adjustments without invalidating existing player progress.
The battle pass is a retention mechanism. Every design decision maps back to one question: does this keep players engaged across the full season, across all player types?
1
Sustain Full-Season Engagement
Prevent early completion and the motivation collapse that follows it.
2
Support All Player Types
Casual players need to feel progress. Dedicated players can't exhaust content early.
3
Maintain Motivation Loops
Players should always have something to work toward — no dead zones in the progression curve.
4
Avoid Artificial Padding
Progression should feel earned. Slowing players down through frustration is not the same as good pacing.
One hard constraint shaped every decision: the system was already live. Any fix had to work forward which means no progress resets, no removed rewards, no breaking existing player trust.
Core Economy Systems
A. XP Source Model
XP flows into the system from multiple sources, each with different cadences and engagement implications.
XP Sources
Match completion XP
Performance bonuses
Daily and weekly quests
Event modifiers
Key Issue (Initial State)
XP inflow too high relative to tier thresholds
Rapid early progression normalized
Dedicated players hit ceiling in ~2 weeks
No mechanism to absorb excess XP
B. Tier Progression Structure
The initial tier structure used a near-flat XP curve, the same or similar XP requirement per tier across the entire pass. This created a design problem: dedicated players could brute-force through it far faster than intended.
| Tier Range | Initial XP Required | Problem |
|---|---|---|
| Early (1–15) | Low | Intentional — but too fast even for casual players |
| Mid (16–35) | Flat | No friction increase — hardcore players blow through it |
| Late (36–50) | Slight increase | Insufficient slowdown for dedicated players segment |
C. Player Segmentation
The initial system was tuned for an "average" player but average players don't exist in practice. Actual behavior split across four meaningful segments, each with very different completion trajectories.
| Player Type | Sessions / Week | XP / Session | Behavior |
|---|---|---|---|
| Casual | 3 | 300 | Plays occasionally, quest completion low |
| Regular | 5 | 400 | Plays most days, completes daily quests |
| Dedicated | 7 | 500 | Plays daily, completes all quests |
| Hardcore | 14 | 600 | Maximizes XP every session |
The system was tuned for "Regular" which meant it was too slow for Casual players to feel progress, and catastrophically fast for Hardcore players to exhaust.
Design Problems
Three interconnected problems emerged during the live season:
Early Completion
Dedicated players completed the full pass in ~2 weeks, less than half the season length.
Motivation Collapse
With no remaining progression goals, engagement dropped sharply mid-season. The system had nothing left to offer.
Curve Imbalance
XP gains consistently outpaced tier requirements. The curve had no meaningful resistance point.
My Approach
Step 1 — Progression Curve Modeling (Excel)
I built a simulation model to predict completion time per player segment under both the old and adjusted curve. This let me validate fixes before pushing them live.
Model Inputs
XP per session per player type
Quest completion rates by segment
Tier XP thresholds (old and adjusted)
Season length in weeks
Output Metrics
Projected completion time per player type
XP surplus accumulation over time
Tier completion rate by week
Segment-specific drop-off risk
| Player Type | Completion (Old Curve) | Completion (New Curve) | Change |
|---|---|---|---|
| Casual | > Season length | > Season length | Unchanged — accessible |
| Regular | ~9 weeks | ~5–6 weeks | Better fit to season |
| Dedicated | ~2 weeks | ~3–4 weeks | Extended by 1.5–2x |
| Hardcore | <2 weeks | ~3 weeks | Slowed without blocking |
Dedicated players complete early, leaving no mid-to-late season goals.
Progression is distributed across the full season for all player segments.
— Casual
— Regular
— Dedicated
--- Hardcore
The goal was not to slow players down but to redistribute progression across the full season.
Step 2 — Progression Curve Diagnosis
The old curve had three problem zones that compounded each other:
The old curve had almost no resistance in mid-game and the zone where hardcore and dedicated players spent most of their time. Fixing the late curve alone wasn't enough; the whole ramp needed recalibrating.
Step 3 — System Adjustments
Based on the modeling, I made three targeted changes, all applied forward-only to avoid invalidating existing player progress:
PROBLEM → DESIGN RESPONSE
Early completion
→
Non-linear XP curve with stronger mid and late ramp
Motivation collapse
→
Removed flat progression segments, ensured constant friction increase
Hardcore Players exhaustion
→
Rebalanced tier thresholds per segment without resetting progress
1
Rebalanced Tier XP Curve
Introduced non-linear scaling: early tiers slightly increased to maintain accessibility, mid tiers ramped moderately, late tiers ramped steeply to slow dedicated players without blocking casual ones. This follows the same principle Fortnite's battle pass uses: early tiers stay accessible to casual players while the mid-to-late ramp naturally filters engagement level without explicitly blocking anyone.
2
Smoothed Mid-Game Progression
Removed flat XP segments in the mid tier range. Every tier now has a meaningful step up, ensuring no dead zones where players feel no resistance.
3
Forward-Only Adjustments (Live Constraint)
Because the system was already live, no progress was reset and no rewards were removed. All changes applied to tiers players hadn't yet reached which means fixing pacing without breaking trust.
Results
2x
extended dedicated players completion time (2 weeks → 3–4 weeks)
27%
increase in average session length through rebalanced pacing
0
player progress invalidated, all fixes applied forward-only
BEFORE
Dedicated players finished in ~2 weeks
No progression goals remaining mid-season
Engagement dropped sharply after completion
AFTER
Completion extended to 3–4 weeks for top segment
Players had ongoing goals through the full season
Mid-to-late retention improved, progression felt paced
Key Design Takeaways
Engagement is not the same as system health
Fast progression looks good in the short term. But in seasonal economies, early completion is a design area that didn’t meet the goals, it kills the motivation loop for your most valuable players.
Always design for player distribution, not averages
A system tuned for the average player will frustrate your casuals and destroy your hardcore players. Segment first, then tune per segment. The average doesn't exist in your actual player base.
Progression curves are the core retention lever
Small changes to XP thresholds and curve shape have outsized impact on retention. Model it before you ship it: a simple Excel simulation predicted the problem before it was too late to fix.
Live systems require constraint-aware solutions
You can't reset progress or remove rewards in a live game. Every fix has to work within what already exists. That constraint makes modeling even more critical, you only get one shot at each adjustment.
← Back to Full Iron Bird Page