How to Choose How to Make Games with AI: The Scope of AI Delegation and Differences in Production Tools｜ぷりω l AI研究室
This article is for people with little to no programming experience who want to try making games using AI. By reading this, you will understand the scope of what to delegate to AI and how to choose production tools, making it easier to decide on a starting method that suits you.
When you search for “making games with AI,” you will find a mix of stories about making games while consulting with AI and stories about AI creating games for you when you give it text instructions. It is easy to get confused about which one to start with.
In this article, to help you think about how to get started, we will organize the usage into the following two categories. Some actual tools may have features of both.
■ What you will learn in this article
・The differences when organizing how to delegate to AI into two usage methods
・”Writing with code vs. assembling with events,” which is a different axis from “how to delegate to AI”
・A decision flow to narrow down candidates based on the target platform
・A checklist of items to confirm before you begin
The descriptions of each service are based on information confirmed on their respective official pages as of October 13, 2026.
■ The conclusion first: How to choose AI game production
Game production using AI is easier to organize if you first think about it by dividing it into the following two usage methods based on “how much you delegate to the AI.”
A. Operate the production tool yourself and ask the AI for consultation or implementation assistance
B. Give instructions in text and have the AI proceed with generating the game or its mechanics
Neither is superior to the other. Choose based on the target platform and the operation method that you find easiest to continue with.
▼ Things to grasp first
→ Think about delegating to AI using the two methods A and B
→ Think about code versus events as a separate axis
→ Narrow down tools based on their support for your target platform
■ How to delegate to AI and how to assemble are separate axes
The other axis is whether to write game movements “with code” or “assemble them with events.”
Code is a method of writing game movements using programming text. Unity and Godot are primarily used this way.
Events are a method of assembling combinations of conditions and actions, such as “if this happens, do that,” by selecting them on the screen. GDevelop is a game engine (production software for making games) that uses this method.
These two axes should be considered separately. For example, if you consult with AI while writing code in Godot, that is usage method A. Even if you consult with AI while assembling with events in GDevelop, it is still usage method A.
Note that even with methods that do not involve writing code, there are still things to learn. Conditional branching (changing movements based on conditions), variables (containers for remembering scores, remaining lives, etc.), game rules, and tool operations are necessary even when assembling with events.
■ Comparison of the two usage methods
Based on the information confirmed on the official pages, we have organized the two usage methods.
◆ Your Role
・A. Operate the tool yourself and consult with AI: You operate the tool to assemble the game and decide whether to use the AI’s suggestions.
・B. Give instructions in text and have the AI handle the generation: You convey what you want to create in text, play the result, and ask for revisions.
◆ AI’s Role
・A. Operate the tool yourself and consult with AI: Answering questions, suggesting code or events, and consulting on the causes of bugs.
・B. Give instructions in text and have the AI handle the generation: Proceeding with the generation of the game and its mechanics. The extent of this depends on the service.
◆ Examples of Assembly Methods
・A. Operate the tool yourself and consult with AI: Code (Unity, Godot, etc.), events (GDevelop, etc.)
・B. Give instructions in text and have the AI handle the generation: Text-based instructions (Rosebud AI, AI Game Builder, etc.)
◆ Things to Check First
・A. Operate the tool yourself and consult with AI: Does it support exporting to your target platform? Can you fix the AI’s suggestions yourself?
・B. Give instructions in text and have the AI handle the generation: Does it support exporting to your target platform? Can you fix what is generated? What are the conditions for commercial use (using it for the purpose of earning money)?
From here on, I will separate the service descriptions from the suggestions in this article.
◆ Service Descriptions (from official pages)
Rosebud AI
https://rosebud.ai/ai-game-creator
It explains that if you describe the game you want to make in text, it will create the code, art, and sound.
It states that there is no need to write code, and that you can also open and edit the generated JavaScript. According to the official page description, there is also a feature to share via a playable link.
AI Game Builder (WillBooster)
https://www.willbooster.com/ai-game-builder/
It explains that when you input instructions in Japanese, the generative AI automatically performs the programming and creates the game.
The official page states that “no programming knowledge or software is required.” It also mentions that you can title and publish the games you create. Note that the official page focuses primarily on recruiting people to use it as educational material.
GDevelop
https://gdevelop.io/en-gb/game-makers
It explains that you can build games using no-code events (creating without writing programs) that combine conditions and actions.
It states that you can have an AI agent help you create mechanics or ask it how to build things.
It supports publishing to Steam, iOS, Android, and the Web, and states that you can create events or extensions using JavaScript. However, the pricing page indicates that the number of times you can publish and the publishing destinations differ depending on the plan.
Like GDevelop, some tools have both the ‘A’ style of building it yourself and the ‘B’ style of having the AI create the mechanics.
◆ Things Not Verified in This Article
In this article, I have not actually tested any of the tools. The speed of production and the differences in the quality of the finished games have not been confirmed.
The scope of what the AI can create and the conditions for plans that allow the use of AI features also differ by tool. The GDevelop pricing page lists the number of AI credits (usage quota for using AI features) for each plan. However, it does not state how much can be used per credit, and this has not been verified in this article.
Before using, please check the latest information on each official page.
■ Decision flow for narrowing down candidates based on the publishing destination
From here on, narrow down your candidates by applying them to your goals. Please answer in order from the top.
-
Have you decided on the publishing destination and the required export format?
・Decided → Export the necessary formats, such as a Windows version for Steam or a Web version to be played in a browser
・Not yet decided → Make a small prototype for others to play via a shared link as your first goal, and check if you can create a shared link in Step 2 -
Does the candidate tool support that publishing destination and format?
・Confirmed support on the official page → Proceed to the next question
・Cannot confirm → Check the official help or remove it from your candidates -
Can you implement and modify the features you want to create with that tool?
・Seems possible → Proceed to the next question
・Don’t know → Look for examples of similar features in the official documentation or samples -
Which operation method is easiest for you to work with: code, event editing, or text-based instructions?
・Selected one → Proceed to the next question with a tool using that operation method
・Cannot decide → Start with the easiest method to try, and re-select after Step 5 -
Were you able to create a small prototype and continue modifying and verifying its operation yourself?
・Was able to continue → Build it up little by little with that tool
・Was not able to continue → Return to Step 4 and re-select an operation method
▼ Important points in the flow
→ First, decide on the publishing destination and export format
→ Check support on the official page
→ Test if you can continue with a small prototype
■ Example of combining tools
You do not have to choose only one between A and B.
For example, consult with a chat AI to briefly organize the game rules. Next, try it out on a small scale using a tool that takes text instructions. Based on the results of playing it, decide whether to continue as is or re-select a method of building with code or events.
If you switch to another tool midway, caution is required. You cannot always move your project as is. Depending on whether you can export code, assets, and data, you may need to start over.
■ Checklist before starting
Checking the following items will make it less likely that you will think, “This isn’t what I expected,” later on.
【Things to check before starting】
□ Decided on the publishing destination (or a prototype for others to play via a shared link)
□ Confirmed on the official page that the candidate tool supports that publishing destination and export format
□ Confirmed that the tool is compatible with the device (PC, smartphone, browser) you will use for production
□ Confirmed the conditions (plans, usage limits) for using AI features on the official page
□ If you plan to sell it, confirmed the conditions for commercial use of generated content and assets
□ Decided on one operation method to try first out of code, event editing, or text-based instructions
“Being able to create games that can be played on a smartphone” and “being able to create them using only a smartphone” are different. Don’t forget to check the device you will use for production as well.
■ Caution: Check the conditions for AI services, tools, and assets
When publishing or selling a completed game, check the conditions for each item you used.
The first is the AI service you use. The handling of generated content and the terms for commercial use differ for each service. For example, the official Rosebud AI page explains that commercial usage rights are required to sell games, and those rights are included in the paid plan. Please check the official page for the scope and conditions of these rights before using the service.
The second is the production tool. Check the plans that support exporting and the conditions for each publishing platform.
The third is assets. If you use images or sounds created by AI, or distributed assets, check the terms of use for each.
■ Summary: What to do today
Game production using AI becomes easier to choose when you consider two axes: “how much to leave to AI” and “whether to write code or build with events.”
You don’t have to choose perfectly from the start. It is enough to make a small prototype, see if you can continue, and then re-evaluate your choice.
There is one thing to do today. Decide where you want people to play the game you want to create (the publishing platform). If you can’t decide yet, make “having friends play it via a shared link” your first goal.
