Beginner’s guide to building a 3D city game
A beginner’s path through CityVibe3D: pick one city game, shape blocks and roads, connect a character, and publish a link friends can play.
Start with one city and one verb
A 3D city game sounds large because a city is large. The games that finish are small. Pick one verb the player repeats: drive, run, fly, or walk. Pick one district, not a whole map of a real city. CityVibe3D builds an editable city environment — buildings, roads, bridges, and regions — and writes the game code that uses that environment. If your first project is “a living metropolis with crime, economy, and day-night jobs,” you will spend the session arguing with the prompt. If your first project is “drive across one bridge before the timer ends,” you can publish something today.
Open the editor from the CityVibe3D site and sign in with Google. The free plan includes one project and does not include monthly AI tokens, so use the free project to learn the screens. Basic and Pro add unlimited projects and a monthly token allowance for generation. You can look at pricing on the home page before you pay. Nothing in this guide requires you to buy a plan to understand the steps.
Learn the city tools by touching them
After a prompt creates a scene, do not immediately prompt again. Click around. The building editor changes floors, facade, and windows. The road tools lay a path with nodes and set width for the road, footpath, and pavement. Bridges have curve height and deck width. Regions group terrain, buildings, and roads so a prompt can fill a block and you can still move pieces with gizmos. These are the same objects the game code drives on. If you delete the road the car is supposed to follow, the game will show you that immediately when you press play.
A beginner mistake is to decorate for an hour before the game has a goal. Place the player’s path first. For a driving game, that is one road from a start to a bridge. For a runner, that is a straight street with a few obstacles. For a flight game, that is a low downtown you can fly over, with one tall landmark so you can tell which way you are facing. Landmarks matter more than density. A player who is lost cannot enjoy the buildings.
Put a character or vehicle in the scene
CityVibe3D connects assets for you. A prompt that says “the player is a car” should drop a vehicle into the scene and wire it to the controls. A prompt that says “the player is a person” should connect a character and its animations. Open the character tools and play the idle or run loop. If the mesh is wrong, swap it. If the material is the wrong color, change it. You are not hunting a separate asset store and writing glue code to spawn the mesh. That wiring is the part the prompt is supposed to do.
Then play. On a desktop, arrow keys or WASD are the controls you should name in the prompt so the generated script matches what you tell players. If the character runs through buildings, the collision or the road placement is wrong. Say that in a follow-up prompt, or move the building off the path by hand. Fixing one intersection by hand is faster than regenerating the whole city and losing the parts you already liked.
Give the game a start, a fail, and a score
Beginners often generate a pretty city and forget the rules. A city game needs a start the player can see, a way to fail, and a number that goes up. Examples: reach the bridge before the timer hits zero; survive as long as you can while traffic increases; collect ten pickups on one block. Put that rule in the prompt and check that the screen actually shows it. If the score only exists in your head, the player will drive around once and leave.
Keep the camera boring on purpose. Behind and slightly above a car. Beside a runner. High and back for a jet. Fancy cameras are the first thing that makes a beginner game feel broken, because the player cannot see the obstacle they just hit. Ask for the simple camera in the prompt, then play on the largest window you have and again on a narrow window.
Publish only after you can explain the game in one sentence
When you can say the sentence out loud — “Steer the car across the bridge and don’t hit the barriers” — publish. CityVibe3D gives you a play link that runs in the browser with no install. Send it to one person who has not watched you build it. If they ask what to do, the game is not ready, and that is useful information. Add a line of on-screen text, or simplify the road, and publish again.
Save the project before you experiment with a wild follow-up prompt. Generation can rearrange a scene you liked. The editor is meant to stay editable after the prompt, so your manual tweaks are part of the project, not a temporary preview. When the link is out, you can still open the project, change a building color, and publish an update. The city is not frozen just because someone has the link.
When you are ready to try it, open the CityVibe3D home page and launch the editor.