• Professional Project ~5
  • Published
  • Mobile Game
  • 2D Survivors-like

Mercenary Syndicate: Survival

Timeframe:
May 2024 - Dec 2025 (1 year 7 months)
Role:
Gameplay Developer and Designer, User Interface Programmer
Tools:
  • Unity
  • JetBrains Rider
  • Spline
  • CodeMagic
  • Firebase
  • Jira
Skills:
  • C#
  • GitLab
  • Dependency Injection
  • Reactive Programming
  • User Interface Design
  • CI/CD

A 2D survivors-like shooter mobile game released for iOS and Android as the first project of a startup team. Players can build a squad of mercenaries to take into battle, where their unique weapons and abilities can shine and be upgraded further to deal devastating damage. Then, they continue to upgrade the mercenaries in their squad out of combat with each level's rewards and navigate branching world maps with increasing difficulty and more permanent upgrades. The team size for this project started with only 5 members and 3 core programmers (including me), but grew slightly larger over time. The idea behind this project was to take the foundation of the existing game Heroes Vs Hordes and design new systems around correcting its weaknesses and preserving its strengths. These efforts resulted in a focus on shorter gameplay sessions, more characters in gameplay, and better control over the types of weapons and upgrades received in gameplay. Ultimately, though, after an unsuccessful launch and trouble retaining players in the following months, the game was removed from stores at the end of 2025.

My role in the project was primarily gameplay engineer, but I also took on the roles of gameplay designer and user interface programmer throughout development. We had the foundation of an existing codebase to start from, but the first main task I had was to rework the player controller from featuring a single hero character with direct movement controls to 3 characters active at once, with new auto-follower movement for the 2 characters not being directly controlled. This was the first challenge, as we wanted the following squad movement to be natural-looking but also controlled so it still felt responsive and didn't place the backup characters too far forward or behind. This extensive work with the player characters led to me becoming the main engineer behind the implementations of 15 of the 20 mercenaries we had in the game. This involved programming their weapon behavior, creating their configurable stats, and setting up their animations and VFX. Soon after starting, I became the feature owner of the mercenary characters, so I handled the design of each new mercenary's weapon type, upgradeable stats via level up, and overall balancing. Finally, I created and implemented many of the UI menus in the game with Unity's UGUI and custom scripts.

While working on this project, I not only gained experience with mobile game development, but I also learned many new skills and industry practices. Due to the nature of the existing codebase, I had to become familiar with dependency injection and reactive programming frameworks before I could even understand or add any code myself. Plus, I developed a deeper understanding of C# from the use of the model-view-presenter, strategy, and factory design patterns and more advanced language use cases like asynchronous methods, LINQ, data transfer objects, and null conditionals. Aside from my direct contributions, I learned at the project level the value of data-driven development, server authentication and user data storage, addressables memory management, analytics, and continuous integration and deployment. With my time spent on this project, I now have a better understanding of how large-scale games need to be set up and maintained.

Throughout this game's development, there was a struggle to fully capture players and hit desired retention metrics. While the major game design decisions were backed by data and made with the intention of improving the player experience, they were often put in the hands of players or playtesters when their implementations were not fully completed or polished. This, in tandem with the free-to-play economy not hitting expected metrics, resulted in many attempts to refresh core game aspects that would continually fail to meet the KPI requirements. Additionally, these reworks were landing in the mid to late development cycle, many months after the prototyping phase, which was passed and assumed to do well all too quickly. Nearing the end of 2025, after the game was fully released for a short time, it was announced the project would be sunset and internal resources would be allocated to other projects. I was assigned to be the last developer working on a final gameplay rework for one more market test. It would change the core game mode from surviving multiple enemy waves in a single level with power-ups based on dropped enemy XP, to a multi-room-based level with a single enemy wave in each room and branching options when determining which room to enter next. While this project wasn't a success, it was a great learning experience, especially from trying so many different game mechanics and seeing first-hand their strengths and weaknesses.

Challenges:

  • Nailing the feel of player movement with indirectly controlled characters that need to naturally move alongside the leader while keeping up, not becoming stuck, and reacting to quick direction changes
  • Planning over 20 unique mercenary characters with multiple abilities and stats then creating formulas to calculate their overall effectiveness and balance accordingly
  • Managing to improve the player experience and new content through multiple large-scale core gameplay reworks
  • Directing an outsourced team of artists on character animations, character VFX, and UI mock-ups to achieve consistent and technically viable results

What I did well:

  • Learned the patterns and frameworks present in the existing codebase quickly, so that there was little downtime after starting the project before I could contribute
  • Led core gameplay development and undertook work on the game's movement, weapons, upgrades, and progression systems resulting in a satisfying game feel
  • Defined the method for out of combat map progression and designed each map with interesting choices and rewards that must be replayed for full completion
  • Took on all remaining roles in the final weeks of development, including level design, enemy wave design, and game balance, to complete and publish a final major gameplay rework

What I would change/improve:

  • Prevent the project from moving past the prototype phase without more in-depth testing of various different gameplay options with positive feedback and analytics from actual playtesters
  • Place more emphasis on the quality of systems over achieving quotas for a quantity of systems based on what a mature live service game would have but all at launch
  • Take more time to playtest my own changes and game design ideas so that I would only be implementing and recommending the best features through experience and trial and error
  • Tailor mercenary character designs better for the simplified combat experience so that each one feels more unique, or adjust the combat elements themselves so that the differing stats of each mercenary become prominent
Previous project Next project