In short
To make a Roblox game with AI, open a place in Roblox Studio, connect an AI agent that can edit it (RoCode, Roblox Assistant or another Roblox AI tool), and describe the whole game in one detailed prompt: the genre, the size, what should happen when a player wins or fails, and how it should look. The agent builds a playable first version. Then play it yourself, ask for what is missing as the next round, and publish from Studio when it is ready.
- In our test, a one-line obby prompt built 10 stages and checkpoints but no way back after a fall. A detailed prompt that named the lava and the respawn got both.
- The detailed run used 0.4 credits on RoCode's Pro plan with GLM 5.3 Flash and took 1 minute 52 seconds. Costs change with the model and the size of the build.
- No AI tool publishes your game, sets its price or tells you if it is fun. Those steps stay yours.
On this page
The test: two prompts, two empty places
Both runs used the same setup: a new local place with only a Baseplate and a SpawnLocation, Roblox Studio with the RoCode plugin 3.9.16, a RoCode Pro account on GLM 5.3 Flash (the plan's default model), Build mode and a new chat. Nothing in either place was changed by hand afterwards; only the camera was moved.
| Run 1: short prompt | Run 2: detailed prompt | |
|---|---|---|
| Prompt | “Build an obby by the spawn: 10 stages of harder jumps, with a checkpoint on each.” | “Build a neon obby by the spawn: 10 stages of harder jumps on glowing neon platforms, a few moving platforms, a lava floor under the course that sends players back to their last checkpoint, a checkpoint on each stage, a glowing finish, and night lighting so the neon stands out.” |
| What it built | 10 checkpoint pads, 27 jump platforms that get narrower, a finish sign and a 72-line checkpoint script | 10 checkpoint pads with a glowing beam on each, 27 neon platforms (3 of them moving), a lava floor, a neon finish, night lighting and three scripts |
| Steps and time | 5 steps, 1 minute 6 seconds | 9 steps, 1 minute 52 seconds |
| Credits | 0.2 | 0.4 |
| Its own test | A 25-second playtest: no errors, test robot 4 of 4 checks passed | The same, after it found and fixed its own hidden lava |
| What was missing | Any way back after a fall: you land on the baseplate and walk | Nothing we found in the part we played |
Step 1: describe the whole game in one prompt
Connect Studio first: install the free plugin, open the chat in a desktop browser and connect (the docs have the three setup steps). Then describe the game, not one part of it. RoCode builds a playable first version from a game-sized request and offers the next rounds after it.
The difference between our two prompts is the lesson. The short one said what the course is (10 stages, harder jumps, checkpoints). The detailed one also said what happens when you fail (lava that sends you back), what moves, and how it should look. The AI built what was asked and nothing more: run 1 had no fall reset because nobody asked for one.
- Genre and size. “An obby with 10 stages”, “a tycoon with 6 droppers”.
- Win and fail. What happens at the finish, and what happens when a player falls, dies or runs out of time.
- What moves or changes. Moving platforms, timers, enemies, a shop.
- The look. Neon at night, a candy theme, a snowy island. RoCode builds scenery and lighting when you ask for them.
- Where. “By the spawn” or “on the empty island” keeps it out of what you already built.
No idea yet? The free game idea generator gives you a core loop and the first prompts. Each genre also has a guide with the systems it needs, such as the obby guide.
Step 2: watch what the AI does in your place
The chat lists each step as it happens. In run 2 they were, in order:
- Build Structure “Checkpoints” and Build Structure “Course”
- Set Property on Lighting, three times, for the night look
- Create Script “ObbyManager”, “LavaKill” and “MovingPlatforms”, then Check Script on each
- A playtest. Then it wrote that the lava “is real but hidden”: it sat below the baseplate, so it never showed. It raised the lava, added a beam on each checkpoint, stood the beams upright and ran a second playtest
Its last line was “Ran a 25 s Play test: no errors, and the test robot passed 4 of 4 checks.” The receipt read “Used 0.4 credits · GLM 5.3 Flash · 9 steps · 1m 52s”. Every batch of changes is one undo point in Studio, so Ctrl+Z (Cmd+Z on a Mac) takes a batch back if you do not like it.
The two short scripts, exactly as RoCode wrote them in that run. The lava script sits inside the Lava part:
-- Generated by RoCode AI | https://rocode.app
local Players = game:GetService("Players")
local part = script.Parent
local cooldown = {}
part.Touched:Connect(function(hit)
local character = hit:FindFirstAncestorOfClass("Model")
local humanoid = character and character:FindFirstChildOfClass("Humanoid")
local player = character and Players:GetPlayerFromCharacter(character)
if not humanoid or not player or humanoid.Health <= 0 or cooldown[player] then return end
cooldown[player] = true
humanoid.Health = 0
task.delay(1, function() cooldown[player] = nil end)
end)As RoCode wrote it in run 2, unedited. When a player touches the lava it sets their Health to 0; the checkpoint script then puts them back on their last checkpoint.
-- Generated by RoCode AI | https://rocode.app
local TweenService = game:GetService("TweenService")
local course = workspace:WaitForChild("Course")
local movers = {
{ part = course:WaitForChild("Mover1"), offset = Vector3.new(16, 0, 0), time = 2.5 },
{ part = course:WaitForChild("Mover2"), offset = Vector3.new(-16, 0, 0), time = 2.5 },
{ part = course:WaitForChild("Mover3"), offset = Vector3.new(14, 0, 0), time = 2.2 },
}
for _, m in ipairs(movers) do
local start = m.part.CFrame
m.part.Anchored = true
local tween = TweenService:Create(m.part, TweenInfo.new(m.time, Enum.EasingStyle.Sine, Enum.EasingDirection.InOut, -1, true, 0.4), { CFrame = start + m.offset })
tween:Play()
endAs RoCode wrote it in run 2, unedited. Each mover slides 14 to 16 studs and back for ever, easing at both ends.
The third script, ObbyManager (72 lines), puts a Stage value on the player list, flashes each checkpoint green when reached, shows a “Stage n/10” pop-up and moves a respawning player onto the checkpoint of their stage.
Step 3: play it yourself
The AI's own test checks only what it chose to check. Press Play in Studio and try to break the game the way a player would: miss jumps, go backwards, rejoin.
Run 1. We played to checkpoint 4. The “Stage 3/10” pop-up appeared on pad 3, and after a respawn from the Roblox menu the character came back on checkpoint 4. Then we walked off pad 4: the character landed on the baseplate, alive, and had to walk back. That was the gap. We did not play past checkpoint 4, and one gap after the turn at stage 5 looks wide in the place file and was not tried.
Run 2. We jumped to the first two platforms and missed three times. Each time the character died in the lava and came back on the first checkpoint with the spawn shield. We did not play past the second platform, so the later stages and the moving platforms were only covered by RoCode's own test.
Step 4: ask for what is missing as the next round
Do not start over when the first version misses something. Describe the gap in the same chat, as one round. For run 1 that would have been:
Add a lava floor under the obby course that sends players back to their last checkpoint when they touch it.
- Reads your place first, so it builds on the Checkpoints and Course folders already there
- Builds the lava part and a script that resets a player who touches it, then compile-checks the script
- Can run a short playtest with its test robot and report what it checked
- Sends the change as a batch you can undo with Ctrl+Z
An example prompt written by us for run 1's gap; it was not run. Run 2 shows the same lava built from the first prompt.
After a build RoCode offers next rounds as buttons, or you type your own. Good next rounds for an obby: a timer and a best-time leaderboard, saving each player's stage, a shop, or a skip-stage product. Keep each round to one system, so you can play it and undo it on its own.
Step 5: polish and publish it yourself
This part is not the AI's. RoCode cannot publish or save your place, create game passes or developer products, or spend Robux. Save the place, then follow publishing and releasing a Roblox game, which covers the File menu, the age questions and who can play it. Check your thumbnail and icon with the free thumbnail size checker before you upload them.
Before you release it, get two or three people to play it. Whether a game is fun is the one thing no Roblox AI tool can test for you.
What AI did not do in this test
- Add anything we did not ask for, such as the fall reset in run 1.
- Play the whole course. Its playtests ran 25 seconds each.
- Make meshes, textures or animations: every platform is a Part. RoCode places existing Creator Store models when you ask for ready-made ones.
- Publish, set up monetization or judge difficulty and fun.
The full list for RoCode is on what RoCode can't do. If you want meshes and animations made for you, or no install at all, other tools fit better: see the top 10 Roblox AI tools.
Questions
Can AI make a Roblox game for me?
It can build a playable first version in Roblox Studio from one prompt. In our test, RoCode built a 10-stage obby with checkpoints, lava and moving platforms in under 2 minutes. It cannot make a finished, balanced game on its own: you still play it, ask for fixes and publish it.
Can I make a Roblox game with AI for free?
Yes, to start. Roblox Assistant comes with Studio, and RoCode's Starter plan gives 1 credit a day with no card. Our detailed obby run used 0.4 credits, though that was on a paid model, and costs change with the model and the size of the build.
What should my first prompt say?
The genre and size, what happens when a player wins or fails, what moves, how it should look, and where to build it. Our short prompt left out what happens after a fall, and the build had no fall reset; the detailed prompt named the lava and got it.
Do I need to know how to script?
Not to start: the AI writes the Luau and puts it in the right place. Reading a little helps you spot a script in the wrong place or a missing server check. Roblox scripting for beginners covers the basics.
How long does it take to make a Roblox game with AI?
The first version of our obby took under 2 minutes of build time. Playing it, fixing gaps in later rounds, adding saving and a shop, and testing with real players takes far longer, as it does without AI.
Sources and further reading
- RoCode: AI Roblox game maker, the real run. run 2, with its video at real speed
- RoCode guide: How to make a game in Roblox Studio. building by hand, publishing and releasing
- RoCode docs. setup, Build and Ask modes, undo points and playtests
- Roblox Creator Docs: Assistant for Studio. Roblox's built-in AI (read 29 October 2026)
- Roblox Creator Docs: Create and publish games and places
How the code was checked: the two scripts are shown exactly as RoCode wrote them in run 2 on 22 October 2026, unedited. Both compile with luau-compile and ran in Studio during that run's playtests, and the lava reset was confirmed by hand. They use Luau's default non-strict style, so Luau's strict type checker flags their untyped object lookups; we did not change them. The example prompt in Step 4 was not run.