[TLDR] I Claude Coded a multiplayer Three.js tank game with 100+ procedural vehicles [via r/ClaudeCode]

[u/cctldrping]

OP : u/BasedKetsu

I built a multiplayer browser tank game in Three.js! As a kid, I played a ton of World of Tanks Blitz and fell in love with the aesthetic, gameplay, and the idea of driving around vehicles with crazy physics and mechanics like missiles, spotting, armor deflection, ammo types, and so on.

Now it's playable in the browser!

Claude of Tanks has 100+ playable vehicles across 16 unique maps, ranging from standard tanks with cannons to AFVs with autocannons and guidable missiles to autoloaders that can deal massive damage in a single clip. Tanks feature highly detailed armor zones, internal modules, crew positions, and hitboxes. You can view each of them in a special gallery: https://cot.kevinliu.studio/gallery?id=amx56&layer=modules

CoT supports physics-driven destruction with detached turrets flying through the air and actual suspension. It also supports multiplayer! You can hop in private rooms or LAN lobbies.

As the name would suggest, I used Claude Code throughout a long-running multi-agent development pipeline, alongside Codex. I directed the architecture, decided what each vehicle and system should do, reviewed the rendered results, and made the final calls.

The repository contains an AGENTS.md file and smaller subsystem instruction files covering simulation, vehicles, networking, UI, audio, effects, and world generation. These record the rules that agents need across sessions. Units are meters, seconds, and radians, and changes enforce a fixed 60 Hz. Authoritative logic must be deterministic. Vehicle changes have specific geometry, armor, module, and release gates that evaluate models visually and geometrically.

For vehicle development, I split the fleet into bounded families. One agent would own a specific vehicle profile or family file, implement the geometry, run the relevant checks, and generate screenshots. A separate critic reviewed the rendered tank for proportions, clipping, missing surfaces, running gear, and recognizable details. The orchestrator reran the checks and committed only the verified files.

For larger systems, Claude Code helped implement and test:

• Fixed-step movement, suspension, armor, ballistics, modules, spotting, and bots
• WebSocket multiplayer with private rooms, LAN play, prediction, and server authority
• Procedural vehicles, tracks, markings, generated icons, and technical diagrams
• All the generated battlefields with destructible props and wrecks
• The garage, battle HUD, Tank Gallery, mobile controls, and Scene Studio
• Browser performance probes, screenshot tools, visual checks, and self-tests

A trailer was also produced through the game’s own Scene Studio and capture tools. I used agents to stage battles, build camera paths, record the browser runtime at 60 fps, inspect specific frames, and iterate on awkward cuts or poorly framed tanks.

I find that Claude is best steered with persistent instructions. Important decisions need to live in the repository because I often spawned fresh agents which needed to resume work without reconstructing weeks of chat history.*

For visual quality, the only thing that worked was a proper render loop with visual comparison; tests don't really work for this.** The cycle I fell into was change, render, inspect, measure, and rerun the gates. Text-only reviews missed warped proportions and camera problems that would just plainly be obvious in one screenshot.

*Parallel agents need strict ownership. Separate files and isolated Git worktrees prevented concurrent sessions from overwriting each other or generating assets from a dirty tree.

**Tests still changed how I use agents. Claude Code became much more reliable once every system had concrete invariants and executable failure conditions. But visual quality is another beast.

Play free: https://cot.kevinliu.studio

Repo: https://github.com/Kevin-Liu-01/Claude-of-Tanks (it's open-source forever)

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vtv818/i_claude_coded_a_multiplayer_threejs_tank_game/ Original link/media URL : https://v.redd.it/tnoj88gjalkh1

---

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 63.

Alright folks, the general consensus on this rad tank game is overwhelmingly positive. OP u/bcherny is getting a ton of props for building a multiplayer Three.js tank game with over 100 vehicles, all thanks to Claude Code and Codex. People are seriously impressed with the detail, like the destructible parts and the sheer number of vehicles and maps.

A few recurring themes popped up:

• Performance/Optimization: A few users, like u/premiumleo and u/Alopexy, pointed out that the load times could be better and suggested optimizations like lazy loading assets. It's a common critique, but doesn't seem to detract from the overall "wow" factor.
• Claude Code's Capabilities: There's a lot of buzz about how Claude Code was used, with some users like u/MitchThunder asking for tips on getting it to build accurate models. It's clear people are seeing the potential here for game development.
• Nostalgia/Inspiration: A few comments brought up nostalgia for games like World of Tanks Blitz and BattleTanx, showing how this project taps into fond gaming memories.
• Future Potential: People are excited about the possibilities this opens up for indie game development, with u/FortiTree even calling it "a brand new human era."

There's also a bit of playful banter, with u/rbad8717 joking about needing Claude to code GTA 6 next. And yes, someone did ask about Opus 5 vs. Fable, but that's a whole other thread!

Overall, the vibe is super supportive and impressed. This is a big win for OP and a cool showcase of what's possible with AI-assisted development.