AI Game Maker 3D: Build With Boxes, Then Add Objects

A 3D game from AI works best in two steps: first let the AI build the rules with plain boxes, then swap in generated 3D objects one at a time. Doing it the other way round gives you a pretty scene that does not play.

Why does 3D need its own approach?

In 2D, a picture is mostly just a picture. In 3D, an object has a size, a direction, a weight on your computer and a shape that things bump into. Any of those can be wrong while the object looks perfect.

"AI game maker" also hides three separate jobs:

• The rules and the world. A coding AI working with an engine or with three.js.
• The objects. A 3D generator, such as Meshy, that makes a 3D object from text or an image. Some engines build this in: Roblox Assistant generates meshes, and Unity's AI makes 3D objects for about 8 to 13 credits each by its own estimate, as of 2 November 2026.
• The check. That one stays with you, because only you can tell whether the room is fun to move through.

Boxes first: a worked example

Attic Drone is an invented game: you fly a tiny drone through a dusty attic to find a lost key. Here is a sensible order.

1. The room, from boxes. Grey boxes for walls and beams, a brown one for the crate.
2. Flying and the camera. Spend most of your time here. A bad 3D camera ruins a good idea.
3. The goal. A yellow cube is the key.
4. Play. Is the room fun in grey? If not, more art will not save it.
5. Swap one box. The crate becomes a real object.
6. Play again, then move on to the next box.

Before step 5, decide how big things are. If the crate is half a metre wide in the box version, say so. Generated objects often arrive at a random size, facing the wrong way, or with their centre point somewhere odd. They can also be heavy enough to make the game stutter.

Write down where each object came from

Licences differ by plan, and you will not remember them later. Meshy's docs, as read on 2 November 2026, say the Free plan includes 100 credits a month and that objects made on it are licensed under CC BY 4.0, which allows commercial use with attribution. Paid plans include commercial-use rights without that condition. So a free object can mean a line of credit in your game, for every object.

Keep a file called credits.md from the first swap on. Do not put names of real characters or brands into your prompts, and look at what comes out, because a clean-sounding licence does not settle whether an object resembles something else. Can you copy game mechanics? has more on what to look out for.

Swapping sounds harmless, but the crate may be load-bearing: the drone bumps into it, and the key may hide behind it. So let your AI draw that first. It writes the drawing in Mermaid, and you can look at the result on mermaid.live.

Paste this to your AI

This is a 3D game made of plain boxes, built with [engine or three.js]. The drone flies through an attic. Replace one box, the crate, with this new 3D file: [file].

First draw a small Mermaid diagram of the crate's role: what can touch it, how it blocks the drone, and what else in the game depends on it. Read this from the project, then show it to me. Nothing on that diagram may change.

Match the size and position of the box, and keep the bump area the same size.

Then report numbers you read from the project, not estimates: the file's size on disk and its size in the scene compared with the old box. Add a line to credits.md with the object's name, the tool that made it, my plan, the licence as I told it to you, and today's date. If I have not told you the licence, write "unknown", stop and ask me. Do not fill it in from memory.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP

How to check it worked

• Fly into the crate from four sides. The drone should stop where it did before.
• Look behind it. Generated objects often have a muddy back.
• Play for two minutes. If the game stutters now and did not before, the object is too heavy.
• Open credits.md. Could a stranger tell where the object came from?