POLYGON

Fixed an issue where Weapon XP was not being awarded; This is an experimental fix implemented on the game backend. We are continuing to monitor the situation. If you experience any issues related to this, please let us know through any available channel. We apologize for the temporary inconvenience. — Polygon Team

Hello, friends.Right now I am focused on developing POLYGON // - a new version of the project with large-scale maps, vehicles, and a full-fledged destruction system.Developing a game of this level requires serious resources. I continue to work as an indie developer and handle most of the tasks myself: programming, networking, optimization, destruction systems, vehicle mechanics, and much more.But to accelerate development, bring in specialists, pay for servers, and maintain technical infrastructure, I need additional support.If you would like to help the development of POLYGON // and become part of its history - you can support the development of POLYGON //.I have also published an extended version of the development diary dedicated to the destruction system.In it, I go into much greater detail about the technical implementation, network synchronization issues, CPU optimization, and all the difficulties I faced during development. The post includes a large number of videos with tests and prototypes.In addition, the first look at the new character has already been published on Patreon. You can support the development here: https://www.patreon.com/redaster_polygonhttps://boosty.to/redaster_studioThank you for your support ❤️! It is truly very important for the development.

Hello everyone :)It’s been almost two years since I announced the new installment of Polygon. Since then, I’ve maintained radio silence.Not because the project was frozen. And not because I had nothing to show.The reason is simpler: I didn’t want to present the game in a “raw” state.Polygon // is being built entirely from scratch.A new foundation. New systems. A new architecture.In the early stages, it didn’t look like a step forward, It looked like a step backward. And I didn’t want it to feel like a downgrade compared to the first game.My goal has always been to move toward a larger-scale experience, but the original Polygon had limitations that made that impossible.So I made the difficult decision to start over. No shortcuts. No legacy solutions.It was important for me to reach the point where the project no longer looks like a rough prototype, but begins to show its true direction.And I feel that moment has finally come.This is the first entry in a new development diary series, where I’ll be talking in detail about the core mechanics of Polygon //.And today, we’re starting with destruction:Destruction in Polygon // is part of the gameplay.During combat, the environment gradually changes. Familiar cover disappears. Buildings lose their shape and reveal new sightlines.This makes every situation less predictable.You don’t just move through the map. You reshape it.I wanted the environment to stop being a static backdrop.Every instance of destruction is generated procedurally. There are no pre-recorded animations and no predefined patterns.The shape of a breach depends on the impact point, force, and conditions at the moment of the explosion. Because of this, each match unfolds differently.You can create new paths where none existed before. Or deny your opponent their usual route.Destruction becomes a tactical tool — one that directly influences the battlefield. In most shooters, moving objects and physics calculations are processed on the client side, meaning on you...