Prompting
What to put in the first sentence, and how to iterate after.
The first sentence
Write the game the way you would pitch it in one breath. Include:
- Who the player is, and what they do every few seconds.
- The place: night market stall, alpine courtyard, felt desk, dungeon floor.
- How a round starts, fails, and ends, plus a restart.
- The feeling of the art, in words a painter could use.
A prompt that only says "make a cool 3D game" produces a thin world. A prompt that names the verb, the camera, and the fail state gives the plan something to lock.
2D or 3D
Say which one. Clevoir will not silently swap engines mid-build. 2D and 3D both run on Godot in the browser. If you want friends in the same world, say that in the sentence.
Follow-ups
After the first playable version, ask for one job at a time: controls, HUD, a missing mesh, a win screen. Attach what you saw. "It is broken" is slower to fix than "the labels cover New Game in the footer."
What not to ask
- Console, phone-store, or native installers. Clevoir publishes browser games.
- Hundred-hour open worlds. Ask for a complete loop you can finish in a sitting.
- Someone else's characters, logos, or trademarked worlds.
- A snack-length first build. Plan on time inside an hour.