Fighter Pilot: Iron Bird
Systems Design — Full Breakdown

Description: 
A live-service progression system where interconnected mechanics like XP, rewards, upgrades, and difficulty are tuned to sustain player engagement across multiple sessions.
Discipline: 
Systems Design, Progression Design, Live Service Architecture
Engine: Unity (Mobile)Tools: 
Unity Analytics, Microsoft Excel, C#


Jump to: The System • Architecture • System Breakdown • Interdependency • Failure Case • My Approach • Results • Full Project Page
What Is the System?
Fighter Pilot: Iron Bird is a live-service progression system designed to sustain player engagement across multiple sessions through XP pacing, unlock cadence, and reward distribution. Unlike simulation systems, this is about controlling player momentum over time by ensuring early progression feels rewarding, mid-game introduces meaningful investment decisions, and late-game avoids exhaustion or completion burnout.
The defining feature:  The system adapts progression pacing to different player behaviors, preventing both early burnout from rapid completion and long-term disengagement from slow progress.
CORE DESIGN PHILOSOPHY
Progression is a pacing tool, not a reward system. The goal is sustained engagement across the full season, tuned differently for every player type.
System Architecture
Every session feeds into a multi-session feedback loop where player performance, rewards, and progression are continuously recalibrated:
Player Performance
missions completed, combat outcomes, quest completion
↓
XP & Currency Rewards
earn rates modulated by performance and engagement level
↓
Unlocks & Upgrades
weapons, aircraft, battle pass tiers — gated by XP thresholds
↓
Increased Combat Capability
access to higher difficulty content and expanded loadout options
↓
Adjusted Progression Speed ↺
reward efficiency recalibrated — loop continues into next session
Retention is a multi-session problem. Each loop must leave the player with a visible next goal, not a completed system.
Design Inspiration:  The progression architecture was informed by live-service battle pass systems in Call of Duty: Warzone and Fortnite: both of which use non-linear XP curves to sustain engagement across player segments. The core design challenge they solved of preventing early exhaustion without artificial padding directly shaped how I approached Iron Bird's tier structure and reward pacing.
System Breakdown
A. XP & Progression Curve System - The Backbone
Controls how quickly players move through content and unlock rewards. The curve shape is the most critical variable in the entire system: too flat and high-engagement players exhaust content early, too steep and casual players feel stalled.
SYSTEM TRACKS
XP Earn Rate → base XP per mission, scaled by difficulty tier and performance bonuses
XP Scaling → rate at which tier thresholds increase across the progression curve
Session Velocity → projected completion time per player segment per session length
Design intent: XP is a pacing control variable. The curve must feel earned and progress should slow as players invest more, not stay constant.
B. Battle Pass System - The Retention Layer
A time-bound progression system designed to drive repeat sessions. The battle pass creates a seasonal urgency that gives every session a forward-facing objective with expiration pressure and players are always working toward something that disappears if they stop.
KEY COMPONENTS
Tier Thresholds → XP required per tier, scaled non-linearly across the pass
Reward Distribution → cosmetic and progression incentives distributed across all 50 tiers
Completion Targets → modeled for 3–4 week completion across all player segments
Design intent: Encourage sustained engagement without forcing grind or enabling rapid completion.
C. Upgrade & Loadout Economy
Players invest currency into aircraft upgrades and weapon systems. The upgrade system is the primary long-term investment layer because it creates strategic decisions that extend beyond single sessions.
System Tracks
Upgrade costs vs income rate balance
Power scaling curves across tiers
Build diversity and viability spread
Design Goal
Meaningful choices between immediate power and long-term investment
Multiple viable loadout paths to prevent dominant strategy
Upgrade costs that scale with city progression to prevent early maxing
Design intent: Create meaningful choices between immediate power and long-term investment.
D. Reward Distribution System
Controls how rewards are granted across missions and sessions. Poor reward distribution was the root cause of front-loaded engagement: if the best rewards come early, players have no reason to return.
Reward TypeTriggerDesign Purpose
Mission Completion XPEvery missionConsistent baseline progress regardless of performance
Performance BonusesHigh-skill outcomesRewards mastery without punishing casual play
Daily / Weekly QuestsSession cadenceCreates daily return incentive beyond mission replay
Event ModifiersSeasonal eventsTemporary earn rate boosts to sustain late-season engagement
Design intent: Balance short-term satisfaction with long-term progression pacing and rewards should pull players forward, not front-load the experience.
E. Difficulty & Encounter Scaling
Enemy encounters scale in complexity and difficulty over time, matching player power growth to maintain engagement. If enemies scale faster than upgrades allow, players feel blocked. If upgrades outpace enemy scaling, encounters feel trivial.
VariableWhat It Controls
Enemy AI Difficulty TiersComplexity of patrol, pursuit, and attack patterns per zone
Encounter PacingNumber and density of enemies per mission stage
Combat DurationAverage time-to-completion per mission, affects XP earn rate
Design intent: Match player power growth with increasing challenge, the system should always feel like it's keeping pace with the player.
System Interdependency
No single system controls retention, it emerges from the alignment of all systems.
XP Curve
earn rate & scaling
Battle Pass
tier thresholds
Rewards
distribution pacing
feeds into ↓
gates ↓
motivates ↓
Progression State
player position across all systems — the shared retention variable
↓ unlocks
↓ challenges
Upgrades
loadout economy
Difficulty Scaling
encounter pacing
CASCADE EXAMPLE — XP TOO HIGH
XP earn rate too high → Battle pass completes in 2 weeks → Players exhaust progression goals → No long-term motivation → Engagement drops mid-season  
CASCADE EXAMPLE — XP TOO LOW
XP earn rate too low → Players feel stalled → Upgrade system feels inaccessible → Early-mid game drop-off increases → Casual player segment churns  
System Failure Case: Premature Progression Exhaustion
The system failed when players optimized it instead of engaging with it. The clearest signal of that failure: players completing all content early and disengaging, not because the game was bad, but because the system gave them nothing left to pursue.
What Players Did
Completed battle pass in under 2 weeks
Maxed out upgrades before mid-season
Stopped engaging with progression systems
Dropped off sharply after early sessions
Why It Happened
XP earn rates scaled too aggressively
Battle pass tier thresholds were too low
No differentiation between player segments
Rewards were front-loaded into early tiers
ROOT CAUSE → FIX → RESULT
XP scaling too high → Rebalanced earn rates across session lengths - stabilized progression velocity across all player types
Battle pass exhaustion → Modeled 3–4 week completion targets in Excel - increased tier thresholds and redistributed rewards across full pass
No player segmentation → Tuned XP curves separately for casual vs high-engagement cohorts - reduced churn risk across both segments
Front-loaded rewards → Redistributed key rewards across mid-to-late tiers - improved retention beyond early sessions
After the fix: the dominant completion strategy collapsed. Players could no longer rush progression and engagement was sustained across multiple sessions instead of front-loaded into the first two weeks.
My Approach
I approached progression as a predictive system by modeling player behavior before pushing fixes live rather than adjusting after the fact.
Step 1 — Modeled Progression as Multi-Session Behavior
Instead of tuning for single sessions, I built a simulation model in Excel across four player types to predict real completion behavior before pushing fixes live.
Player TypeSessions / WeekXP / SessionOld CompletionNew Completion
Casual3300> Season> Season
Regular5400~9 weeks~5–6 weeks
Dedicated7500~2 weeks~3–4 weeks
Hardcore14600<2 weeks~3 weeks
Modeling across segments revealed that the system had been tuned for the "Regular" player which meant it was too fast for Dedicated and Hardcore players, and too slow for Casual players to feel consistent progress.
Step 2 — Designed for Player Segmentation
Recognized that no single curve works for all player types. The fix was per-segment tuning that ensured neither group broke progression pacing.
Casual Players
Needed consistent early progress to feel motivated
Early tier accessibility preserved
Completion beyond season length is acceptable
Hardcore Players
Needed meaningful resistance in mid-to-late tiers
Non-linear curve steepens in late tiers
Completion target: 3 weeks minimum
Step 3 — Balanced Through Telemetry + Playtesting
Used Unity Analytics session length data and completion rate telemetry to identify the exact drop-off points, detect progression spikes, and validate adjustments before shipping them live.
Step 4 — Treated Progression as a Retention System
The reframe that changed everything: progression is not reward distribution. It is a tool to control engagement over time. Every tuning decision was evaluated against one question: does this keep players returning across the full season?
Results
27%
increase in average session length through rebalanced pacing
19%
improvement in mid-game level completion rate
3–4 wk
battle pass completion window stabilized across all player segments
PLAYER BEHAVIOR INSIGHT
After rebalancing, players stopped rushing progression and began optimizing playstyles instead:

Experimenting with loadout combinations across missions.
Replaying missions for performance improvements rather than XP farming.
Engaging with the upgrade system over multiple sessions rather than front-loading purchases.

This indicated a shift from completion-driven play to engagement-driven play and the system was no longer something to finish, it was something to play within.  
BEFORE
Players completed progression too quickly
Rewards felt front-loaded into early tiers
Mid-to-late game lacked motivation
High churn after early sessions
AFTER
Progression sustained across full season window
Reward pacing distributed effectively across all tiers
Mid-game engagement improved measurably
Players remained invested across multiple sessions
Key Design Takeaways
Progression is a pacing problem, not a reward problem
The goal is to give rewards at the right time and frequency. Adding more content doesn't fix a pacing problem. Changing when and how content is surfaced does.
Retention emerges from system balance
No single system controls engagement. XP, rewards, difficulty, and goals all have to be in alignment and fixing one without adjusting the others creates new imbalances downstream.
Player behavior reveals system failure
When players rush, stall, or disengage, that's a system design problem. The behavioral data tells you exactly where the pacing breaks and what kind of fix is needed.

← Back to Full Iron Bird Page