Telegram game: server-side battles and game systems
Game progression, digital ownership, trading and the backend had to form one coherent product.
My work covered game logic, backend, product decisions and coordination of development tasks. The server manages turns, action points, effects and damage, sends battle updates over WebSocket and records results. I also worked on launch, promotion and the TON/NFT side of the product.
Player & tanks
Turns & actions
WebSocket updates
Recorded results
A server-side battle coordinates PvP and PvE turns. Tank state includes health, armor, speed, abilities, effects, cooldowns and action points. The loop chooses the next turn, applies actions and damage, then sends available actions and state changes to clients over WebSocket.
Tank access distinguishes an owner from a renter and accounts for cooldowns and rental limits. Crafting checks the input tanks and their ownership, then records a crafting document and the resulting game tank. Wallet links and NFT state are part of the asset model.
The server maintains the active battle state while clients receive updates. Database records link a battle to its tanks and store outcome data, including damage and points. Telegram WebApp authentication connects the player session to the game API.
The game reached 130k users. The independent project brought together game systems, backend development and launch work.
A role, a product, or a technical challenge. Share a little context.
To use the form, enable JavaScript. You can also write to me directly on Telegram.
Write on Telegram