About Tanks Playground

Tanks Playground is an indie tank game made by a single developer, Alexey. Development started in early 2024 and the game is over two years old; 42,596 accounts own vehicles, there are clans and a live community on Telegram and Discord. The project is now moving to the Godot engine: battles become online (7v7), and vehicles and progress transfer to the new version via an open registry.

Facts

DeveloperIndie: one developer, Alexey (BlitzPlay Games)
Development startedEarly 2024
Project ageOver two years in active development
Accounts with vehicles42,596 (August 2026)
Vehicle classesLight, medium, heavy, tank destroyers, artillery; rocket launchers later
Vehicles27 machines, tiers I–XI: researchable, premium and collectible
NationsUSSR, Germany, United Kingdom, USA, Finland
StyleLow-poly: minimalism and stable performance
PlatformsAndroid (Google Play) is primary; App Store in a second wave; APK and Windows build on Telegram
ModesOnline 7v7 (bots fill the team after 60 seconds), versus bots, offline, special event modes
ProgressionContainers and lotteries, boosters; clans up to 30 players (creation costs 10,000 gold), seasons with prizes for clan experience
CommunityTelegram and Discord: tournaments, tactics, feedback goes straight into patches
StatusOpen beta; moving to Godot — combat, driving, bots, sound and meta screens already live in the new version
PlannedArtillery and rocket launchers, daily tasks, battle passes, special modes (gun game), PC build
EconomyShared BlitzPlay star balance, no mandatory payments

Project history

Early 2024Development starts, first combat and vehicle prototypes
2024First Google Play release, core game and vehicle park
2025Clans, seasons, containers and bosses; community growth
2026Move to the Godot engine: 7v7 online battles, vehicle and progress transfer, single BlitzPlay account

FAQ

What is Tanks Playground?

A low-poly tank shooter: session-based 7v7 battles, 27 vehicles, clans and containers. Made by a single developer.

Who makes it?

One person, Alexey. Everything from the game to the websites is his work; some assets are purchased. The goal is to build a team and grow the project for years.

How is it different from big tank games?

Player involvement: the community directly shapes what appears in the game. Suggestions from Telegram and Discord land in patches, not in a years-long backlog.

How many vehicles are there?

27 machines from the Pz. II C to the T-90 — researchable, premium and collectible, tiers I through XI. The park keeps growing.

Is the game free?

Yes. In-game purchases and BlitzPlay stars are not required for progress.

Are there clans and competitions?

Yes: clans up to 30 players with seasons and prizes for clan experience, leaderboards with star rewards.

What is changing right now?

The project is moving to the Godot engine: 7v7 online battles, server-side meta, vehicle transfer via an open registry. The beta continues, builds ship regularly.

Will I lose progress when the engine changes?

No. Accounts, vehicles and progress transfer; the transfer status of each vehicle is shown on its page on this site.

Where can I download it?

Google Play, plus an APK and a Windows build on the Telegram channel.

Where the data comes from

nakama-tanks

The richest data set: vehicle catalog, clans, seasons, public profiles. Every game has its own Nakama instance with its own schema — the site has no shared data model and talks to the instance of whichever game hub is open. The BlitzPlay account and star balance live separately, in the platform database, and are the same for every game.

Player profilestorage: player_profile · account.metadata
Weekly top / leaderboardleaderboards: weekly_xp, season_clan_xp
Tank pagesstorage: tanks_catalog + battle aggregates (public, indexed)
Clansgroups + storage: clan_season
Player searchusers.search by nickname and custom_id
Containers and boostersstorage: inventory, containers_log

Machine-readable version

This same page is served to assistants: JSON-LD (VideoGame + FAQPage) in the markup, a text digest in /llms.txt, hreflang for every site language. Texts go through the same localization system as the rest of the interface.

/llms.txtapplication/ld+json · VideoGameapplication/ld+json · FAQPagesitemap.xml
Languages:entrpt-bridru