Skip to content
AI Primer
workflow

Meshy says it built 18 AI-asset games in three days

Meshy launched an arcade of 18 games it says were built in three days using Meshy, Claude and GPT. Its accompanying guides document build times and credit costs for browser, pixel-art and match-3 game workflows.

4 min read
Meshy says it built 18 AI-asset games in three days
Meshy says it built 18 AI-asset games in three days

TL;DR

  • Meshy says it built 18 games in three days with Claude and GPT; its arcade announcement puts Snow Globe Workshop at 44 minutes and 592 credits.
  • A first-time game maker built Toy Kart Rally in five hours, using one prompt and no human-written code, according to MeshyAI.
  • The production recipes cover browser 3D, pixel art and match-3 games, with illustrated guides for each.

The chess tutorial packs 24 GLB models into about 3.7MB, while the pixel-art walkthrough logs seven rounds of agent playtesting. Candy Match 3 reached a published web page in about one working day, with a person checking outputs and making the design calls.

Snow Globe Workshop and Toy Kart Rally

Meshy's arcade is free to play in the browser.

In Toy Kart Rally, players race wind-up cars around a messy bedroom, drifting to charge a boost and jumping off a book ramp. A race runs three laps against four rivals, with keyboard and touch controls.

Concept art, rigging and browser delivery

Little Kingdom Chess uses animated characters as chess pieces, including a mounted knight and a wheeled siege tower. In Meshy's browser-game guide, a local coding agent calls the Meshy CLI to generate assets, operates Blender and writes the game code.

Its asset pipeline runs through these stages:

  1. Set the art direction: Generate a concept image, then extract individual characters and props with Image to Image. Humanoids get an A-pose for rigging.
  2. Generate low-poly models: Use Smart Topology with separate budgets. This build targeted 6,000 faces for humanoid pieces and 1,200 for handheld props.
  3. Add movement: Meshy's auto-rigging handles humanoids, with moves from its Animation Library and Text to Motion. An agent scripts Blender to rig the horse and separate the siege tower's wheels.
  4. Compress and publish: Use gltf-transform for meshopt geometry compression and smaller WebP textures, load the assets in three.js, and publish HTML, JavaScript and models as static files.

The rider's sword broke pose detection during auto-rigging. Removing it in Blender and generating it separately let the character rig successfully.

Rescue Raid's real-time pixel art

Rescue Raid renders 20 Meshy-generated 3D models as pixel art in real time, a clever shortcut around hand-drawing directional sprite sheets. Its production guide documents a three.js WebGPU pipeline with a WebGL 2 fallback.

The renderer tackles four problems:

  • Too many colors: Group texture colors into palettes with four shading steps.
  • Weak silhouettes: Add dark outlines and lighter lines between overlapping parts.
  • Texture noise: Absorb stray specks while preserving dark details such as eyes.
  • Shimmer during scrolling: Snap the camera to the pixel grid, then restore smooth movement with a sub-pixel offset.

Playtesting sub-agents opened the game in a headless browser and returned bug reports with reproduction steps and screenshots. One found that portrait-mode phone players were being shot by boss guns outside the visible screen.

Candy Match 3's difficulty bot

Candy Match 3 keeps its board rules in standalone JavaScript, separate from rendering. That lets a bot play each of its 15 levels 200 times without drawing the board, as described in the match-3 guide.

Three controls shape each level:

  • Move allowance.
  • Number of candy kinds: Five on early levels produces more matches and longer cascades than six.
  • Goal: Either a target score or a quantity of particular candies to clear.

The bot ranks every possible swap by how many candies it clears, then randomly picks one of the top three. Meshy reports these win rates after tuning:

| Level | Bot win rate |
| --- | --- |
| 1 | 100% |
| 4 | 100% |
| 6 | 81% |
| 12 | 73% |
| 15 | 67% |

The guide also records a performance bug: resizing the canvas every frame reduced the game to about 3fps. Resizing only when the window changed brought long cascades to about 59fps.

Share on X