Skip to guide
DocumentationProject guides
Project guides

Make a game

Build a playable loop before expanding the world.

Reviewed 6 October 2026 · 2 min read

Import example project ↗Two named conversations, shared files, revisions and a preview.

Before you start

Choose an engine for target and scope: Godot, Unity, Unreal, Roblox or a browser framework. Blender helps produce assets; it is not the game runtime.

Engine installation, matching SDKs, licenses and distribution accounts are prerequisites. New structured engine adapters still need release/native verification.

Step by step

  1. Define the player action, objective, failure condition and target devices.
  2. Create a small scene with movement, camera, collision and restart.
  3. Add UI, audio and licensed assets; use placeholders until mechanics work.
  4. Run gameplay tests, inspect logs and profile a representative slow scene.
  5. Package for each target and test the actual input method.

Try this

Example request

Build a tiny 3D obstacle course in Godot. The player moves, jumps, falls and restarts. Use simple shapes first. Add a finish condition and pause menu. Test movement, collision and restart, then show gameplay evidence and name the platforms actually tested.

Check the result

  • The game starts, can be played, reaches win/loss and restarts.
  • Keyboard/controller/touch works as intended.
  • Frame-time issues are measured.
  • Screenshots and compilation are not mislabeled gameplay tests.

If something goes wrong

Resolve two editor instances owning the same project before saving.

An MCP bridge needs compatible editor components and an open project. A connection alone proves no gameplay behavior.

Keep going

Unreal Engine projectsUnity and Godot projectsRoblox Studio projectsAssets, audio and 3DTest real user behavior
Your screen may differ by platform and version. Check availability or get help.