🔫 4v4 Tank Shooter — Project Case Study

This project is a real-time 4v4 team-based mobile shooter built in Unity, focused on robust multiplayer architecture, scalable gameplay systems, and long-term player progression.

My primary responsibility was designing and implementing core gameplay and multiplayer systems—ensuring the game remained fair, extensible, and maintainable as complexity increased.

The goal was to deliver fast, competitive team-based combat on mobile while supporting:

• Real-time multiplayer fairness
• Deep gameplay systems (abilities, inventory, tank stats)
• Meaningful progression and retention mechanics

Rather than building features in isolation, the project emphasized system-level design that could scale as new content and modes were added.

• Designing a multiplayer architecture that stayed fair under mobile network conditions
• Avoiding shallow, repetitive gameplay in team-based matches
• Building scalable systems for abilities, inventory, and tank customization
• Supporting progression and retention without bloating gameplay logic

The Problem

Early multiplayer prototypes exposed issues common to real-time mobile shooters:

• Players appearing out of sync
• Delayed actions under poor network conditions
• Inconsistent combat outcomes

The Solution

I focused on architecture first, not quick fixes:

• Implemented a server-authoritative model for all combat-critical logic
• Used client-side prediction to keep controls responsive
• Applied interpolation for smooth remote player movement
• Optimized network messages to send only essential state changes
• Added lag compensation and periodic validation to maintain consistency

This approach ensured fairness while preserving a smooth player experience.

The Problem

Without strong systems, tank customization risked becoming:

• Hard-coded
• Difficult to balance
• Painful to extend

The Solution

I designed gameplay systems as data-driven, modular components:

• Tank Stats System
  • Speed, Attack, Defense, Critical Chance
  • Stats modified through upgrades, abilities, and progression
• Ability System
  • Abilities applied temporary or conditional modifiers
  • Designed to stack predictably without corrupting state
• Inventory System
  • Managed unlocks, loadouts, and upgrades
  • Separated gameplay data from UI representation

This allowed new tanks, abilities, and upgrades to be introduced without rewriting core logic.

The Problem

Playtests showed that raw shooting mechanics weren’t enough to sustain engagement.

The Solution

I introduced clear tank roles to promote team strategy:

• Assault → High damage, frontline pressure
• Support → Buffs, survivability, team utility
• Scout → Speed, flanking, information advantage

Each role interacted differently with abilities and stats, encouraging cooperation and varied team compositions instead of mirror matches.

The Problem

Without progression, matches felt isolated and disposable.

The Solution

I integrated progression systems that complemented gameplay instead of overpowering it:

• XP-based progression tied to performance
• Stat tracking for transparency and feedback
• Unlockable upgrades that expanded playstyle options
• Matchmaking aligned with progression to maintain balance

Progression rewarded mastery and experimentation without turning matches into pay-to-win scenarios.

While not the main focus, performance considerations were integrated to support the above systems:

• Optimized asset loading to reduce match startup time
• Adaptive performance targeting stable 30 FPS on low-end devices
• Match logic allowing players to enter as soon as they finished loading

This ensured gameplay systems weren’t undermined by technical friction.

• Fair and consistent real-time 4v4 multiplayer battles
• Scalable gameplay systems for abilities, inventory, and stats
• Increased strategic depth through roles and progression
• Faster match starts and stable performance on low-end devices
• Architecture capable of supporting future modes and content

With additional development time:

• Expand server-side validation for competitive modes
• Add deeper meta-progression and seasonal systems
• Introduce advanced matchmaking based on playstyle and role preference

The existing architecture supports these extensions without major refactoring.

• Multiplayer fairness starts with architecture, not tuning
• Data-driven gameplay systems scale better than hard-coded logic
• Strategic depth drives retention more effectively than raw mechanics
• Progression systems should reinforce gameplay, not replace it