Which tools do browser game makers say they used? A count across 498 games

By Slop Outlet ·

Games made with AI and the tools behind them: of the 498 games on the Slop Outlet shelf, 138 have a maker-stated tool or library. Claude, Codex, Grok and Gemini show up, and three.js is the most named library by a wide margin.

Many of the games on this shelf were built fast, and many of their makers say how. We went through the notes we keep for every game, which come from the maker's own post or from the game page, and counted which tools and libraries makers say they used. This is a count of what makers chose to say, so treat it as a rough picture and not as a survey of the whole industry.

The headline numbers

As of November 11, 2026 there are 498 games on the shelf. For 138 of them the maker names at least one tool or library, and for 360 they name none. Of those 138, 96 mention an AI tool or say the game was vibe coded. A game can name more than one tool, so the figures below overlap.

AI tools and assistants

  • Claude and Opus models: 58 games. This includes Claude Code, Claude Opus 5.5 and plain Claude.
  • OpenAI tools: 18 games, covering Codex, ChatGPT and GPT models.
  • Grok: 13 games, including Grok Build and Grok Bot.
  • Google tools: 5 games, covering Gemini, Antigravity and AI Studio.
  • DeepSeek: 1 game.

The lean toward Claude is partly a story about timing: a lot of the games on the shelf were shared in October 2026, when several makers posted about building a whole game from one prompt with Opus 5.5.

Libraries and engines

  • three.js: 41 games name it. Another way to see the same thing: 154 of the 498 games are tagged 3D, and 53 are tagged three.js.
  • GDevelop: 5 games.
  • HTML5 Canvas: 4 games.
  • Godot: 3 games.
  • Unity: 2 games.
  • WebGPU: 2 games.
  • Phaser and PixiJS: 1 game each.

The pattern is that three.js is how most makers get 3D into a browser tab without a heavy engine, while the engines with browser exports, Godot, Unity and GDevelop, show up in a smaller number of games.

A few examples

  • Hippo Heist: its maker says they rebuilt an older game from scratch with Claude Code on Opus 5.5.
  • Tidelight: the maker asked Claude Opus 5.5 to build the game and then its launch trailer.
  • Pale Hours: a multiplayer horror game built with Opus 5.5, Three.js and Go WebAssembly.
  • Àyò Journey: a West African seed game built in Unity with the free tier of Claude Sonnet 5.5.
  • Faster: a platform runner made with GDevelop.
  • Hamster Village: a cozy town builder made with Godot.
  • Dystopia: a noir cyber-city that runs on WebGPU.
  • Space Invaders 3D: a Godot WebAssembly build that its maker says Gemini generated.
  • ChronoCards: an Indian history card game built with Claude.
  • Tsuribito: a feudal Japan fishing game that its maker says came from one prompt.

What this does not tell you

The counts come from what makers say. We do not verify those claims, and most makers say nothing, so a game that names no tool might be hand-coded or might be AI-assisted. A named tool also says little about quality, since a good game can be built in many ways. What we can say is that every game here is credited to its maker, and that every game is checked in a real browser before it goes live.

Enable JavaScript for the full page.