# Describe a game and AI makes it, then you keep describing > Say what the game is in plain words and Summer Engine makes it: a real project you can play in seconds, then reshape by describing what to change next. - URL: https://www.summerengine.com/describe-a-game - Keyword: describe a game and ai makes it - Related: https://www.summerengine.com/text-to-game Describing a game is easy. Making one used to be the hard part. Summer Engine closes that distance: you describe the game out loud the way you would explain it to a friend, and the AI makes it into a working project you can immediately play. The first description is the spark, and then describing becomes the whole way you work. The trick is that you never stop describing. You watch the game run, notice what is off, and say the next thing: faster enemies, a darker sky, a second weapon, a softer landing. Each description edits the same project in front of you. There is no menu to find, no node to wire, no syntax to get right. The words are the controls. What you get back is not a clip or a preview. Summer Engine is a full desktop engine compatible with Godot 4, so the game your description makes is a standard project on your machine. You own the files, you can open the editor whenever you want, and you can export to Windows and macOS. ## How much detail to put in a description You can describe a game in one sentence or in five, and both work. A short line like "a neon racer where you dodge traffic on a rainy highway" is enough for the AI to make a playable first version. A longer description, where you spell out the controls, the goal, and the mood, gets you closer to your exact picture on the first try. Either way you are not locked in. The point of describing is that you can always add more once you see what showed up. ## The describe, play, re-describe loop Making a game this way is a loop, not a single command. You describe the game, the AI makes it, you press play, and you react to what you actually feel rather than what you imagined. Then you describe the fix: the jump is floaty, so ask for a snappier one, the level is empty, so ask for hazards in the gaps. Every pass narrows the distance between the words in your head and the game on the screen, and you see each change land live. ## Describe changes, not just the first game Describing is not only for the opening idea. It is how you grow the game. Add a boss, a title screen, a shop, a new world theme, a second player, all by saying so. Restyle every sprite, swap the soundtrack, or rebalance the difficulty with a sentence. Because each description edits one coherent project, the game stays whole as it grows, instead of becoming a pile of disconnected pieces you have to stitch together. ## Describe any kind of game, in 2D or 3D What you describe decides the kind of game you get. Ask for a flat 2D puzzle and Summer Engine sets up 2D physics and a fixed or side camera. Describe a 3D exploration game and it sets up 3D movement with a follow camera. The same place you type your description makes a pixel-art platformer one day and a first-person prototype the next, because there is a complete game engine underneath the words rather than a single template. ## The game your description makes is yours to keep When the game finally matches what you described, it is a standard project with no lock-in, no royalties, and no revenue share. Export it to Steam, itch.io, the App Store, or your own site and pay Summer no royalties on what you earn. Summer Engine is free to download and free to start, so describing a game and getting a first playable version costs nothing. You only pay later for heavier AI usage as the project grows. ## FAQ ### How does describing a game and having AI make it actually work? You type a description of the game in plain language and Summer Engine makes it into a real project: a character you control, a level, the core loop, and matching art and sound. You press play right away, then keep describing changes. Each description edits the same project, so the game grows from your words without any code or menus to learn. ### How detailed does my description need to be? As detailed or as loose as you like. A single sentence is enough for the AI to make a playable first version, and a longer description with controls, goals, and mood gets you closer to your exact idea on the first pass. You can always add more by describing the next change after you see what was made. ### Is it free to describe a game and have AI make it? Yes to start. The Summer Engine desktop app is a free download, the core engine is open source, and you can describe a game and play the result on the free tier. You only pay for heavier AI usage as a project grows, not to install the app or make your first game from a description. ### Can I describe both 2D and 3D games? Yes. What you describe decides the type. Ask for a 2D platformer or top-down game, or a full 3D scene with cameras, lighting, and physics, and Summer Engine sets up the right movement and camera for each, because it is a complete game engine rather than a single-type tool. ### What if the game does not match my description? That is the normal part of the loop. The first version rarely matches your head exactly, so you describe the difference: make it darker, give the player a dash, make enemies chase instead of patrol. Each description updates the running game, so you close the gap one plain-language change at a time. ### Can I sell the game I describe? Yes. You own everything the AI makes from your description. Export to Windows and macOS, publish on Steam or itch.io, and pay Summer no royalties or revenue share. [Describe your game](https://www.summerengine.com/download) --- ## Machine-readable resources - Site index for agents: https://www.summerengine.com/llms.txt - Full inlined content: https://www.summerengine.com/llms-full.txt - Porting catalog: https://www.summerengine.com/llms-porting.txt - Structured catalog: https://www.summerengine.com/agent-catalog.json - Sitemap: https://www.summerengine.com/sitemap.xml - Developer resources: https://www.summerengine.com/docs