How to build a Roblox obby with AI

An obby, short for obstacle course, is one of the best first Roblox projects. The rules are simple, the content is repeatable, and the whole thing is easy to test: can a player get from the start to the end? An AI agent is a good fit because so much of an obby is repeated structure with small variations.

What an obby needs

At minimum:

A spawn and a finish.
A series of stages, each with obstacles.
Checkpoints so players do not restart from the beginning.
Hazards such as kill bricks, moving platforms, and spinning bars.
Some progress feedback, such as a stage counter.

Everything else, including shops, trails, and speedrun timers, comes later.

1. Write the concept

Give the agent a short brief:

Build a 10 stage obby with a grass theme. Stage 1 is easy jumps. Each stage adds one new obstacle. Add checkpoints at the start of every stage and a stage counter in the UI.

Naming a theme and a difficulty curve helps. Without one, you tend to get ten similar jumps.

2. Build the first stage and test it

Start with a single stage to confirm the basics: spawn, a few platforms, a checkpoint, a finish pad. Run it. Is the jump distance fair? Can you reach the checkpoint? If the base is solid, the rest is variation.

3. Add checkpoints properly

Checkpoints are usually SpawnLocations or touch parts that record the stage on the server. Ask for:

A server script that stores each player's current stage.
Respawning at the stored checkpoint.
Persistence between sessions only if you want it, since that needs a DataStore.

4. Add obstacles one type at a time

Describe each obstacle and let the agent build it:

Kill bricks. Parts that reset the player on touch.
Moving platforms. Parts that tween between two positions.
Spinning bars. Parts rotated by a script or a constraint.
Disappearing platforms. Parts that fade and return after a delay.
Conveyor belts. Parts that push a player along a direction.

Test each one before adding the next, so a bug has only one suspect.

5. Tune the difficulty

Distance and timing decide whether a jump is fair. Roblox characters jump roughly the same height, so you can ask the agent to keep every gap within a safe range and widen the margin on mobile. Then play it yourself. If you cannot clear it in a few tries, players will quit.

6. Add UI and feedback

A stage counter, a timer, and a short message when a stage is cleared make the course feel finished. Ask for a simple UI and keep it clean. See how to build Roblox UI with AI.

7. Playtest with the agent

Ask Kiwari to run the course and walk the character to a checkpoint, then report anything unexpected in the console. It cannot judge fun, but it can catch broken checkpoints, parts that are unreachable, and scripts that error.

Common obby problems

Players fall through the checkpoint. The touch part is too thin. Make it taller.
Checkpoints do not save across stages. Check that the server stores the highest stage, not the latest touched.
Exploiters skip stages. Validate progress on the server by checking that stages are cleared in order.
Lag on phones. Too many moving parts. Use fewer scripts that each move many parts.

Ideas to make it yours

A theme per world: lava, ice, candy.
Rotating daily obstacles.
A shortcut that rewards skilled players.
Cosmetic trails as rewards.

Start for free and build your first stage.

All posts