A free browser game — play it in your browser, no install. Which build setup should an AI coding loop use? Seven setups built the same three.js tank game twice each: cost, time, lines and hidden checks, with every game playable.
Vote and save it — continue with GitHub or sign in free
Made this, @cocodedk? See how many people played it → or use email
Best with a keyboard.
GitHub asks to share your profile and email with us. We never post anything.
No account needed to save ♥ or react 🔥: they’re under the game. Or vote with email.
Open the live demo Source on GitHubWhich build lifecycle should graph-loop use? (issue #463.) Each setup below builds its own copy of the same game, Tank Duel (spec.md): a three.js arena where you and the computer drive tanks and shoot shells that bounce once off the walls. Every version is kept in this project, under runs/-/.
runs//run.json holds the numbers (dollars per call and per model, minutes, cache-read share, rounds, the suite and review per round, the hidden checks), runs//game/ the game, runs//log/ what each call said, and runs//screenshot.png its first frame.
Built something like this? Submit your vibe — free account, takes a minute. How listing works.
Claim it: create a free account, then press CLAIM THIS in the cruiser. Put the badge below in your README or on your demo page first; that link is how we know it's yours.
Your project is on the cruise, loaded live from your own site. Put the badge in your README or on the demo page: it shows your live play count, it links back to this page, and everyone who lands here is one click from running the real thing.