Hi everyone!

We've been working on a major update for our multiplayer tank shooter, ***DEPLOYMENT***, and this time we wanted to focus less on adding new content and more on improving the overall gameplay experience.

One of the biggest additions is a brand-new game mode called ***Thick Skin***.

Instead of making battles faster, we went in the opposite direction: every tank now has a much larger health pool. This makes fights last longer, gives players more opportunities to react, use abilities, reposition, and recover from early mistakes. Positioning and decision-making become much more important, while random deaths happen less often.

Alongside the new mode, we also spent a lot of time improving systems that players interact with every match:

1.Rebalanced every class to make them all viable choices.

2. Reworked upgrade descriptions to make abilities easier to understand.

3. Improved controller aiming to make it feel smoother and more predictable.

3. Fixed multiplayer lobbies so parties stay together after matches.

4. Changed the ranking system so matches against bots no longer award rating points.

5. Added support for several new languages.

6. Continued optimizing the game and fixing stability issues.

One thing we've learned during development is that improving existing systems often has a much bigger impact than simply adding more content. Sometimes small quality-of-life improvements completely change how the game feels.

We're curious how other developers approach this.

***When working on a multiplayer game, do you prefer adding new content first, or refining the core gameplay until it feels right?***

After listening to player feedback, we decided to rethink combat instead of just adding content