Roblox obby generator: stages, checkpoints and a finish line from one prompt

An obby lives or dies on its difficulty curve. The first stages should be almost free: wide platforms, short gaps, no traps, so a new player learns how far the avatar jumps and feels progress within seconds. Around the middle, the course starts mixing ideas, a narrow beam followed by a moving platform, a jump onto a part that disappears. The last stages combine everything and ask for precise timing. Players quit when one stage is suddenly far harder than the one before, so the generator raises the challenge step by step instead of in spikes.

Distances matter more than decoration. With the default settings a Roblox character jumps roughly 7 studs high and about 12 studs forward with a running start. A gap of 8 or 9 studs feels comfortable, 11 feels risky, and anything past 12 cannot be cleared without help. The generator keeps every required jump inside that envelope and uses height, width and moving parts to add difficulty, which is how experienced obby builders work too.

A course is more than platforms in the sky. The generated place carries the systems players expect from an obby, each one placed where Roblox runs it:

The AI works best with a short brief that answers four questions. How many stages, and should they be grouped into worlds or sections? What is the theme, a candy land, a lava cave, a city rooftop run, a course floating above the clouds? Which obstacles do you want and which ones should stay out? What happens at the end: a badge-style win, coins, a teleport back to the lobby?

Say how hard the game should be and who it is for. "Easy obby for younger players, 20 stages, no disappearing blocks" gives a very different layout than "hard tower obby, 40 stages, narrow beams and spinning bars after stage 25". You can also ask for a Skip Stage button, a lobby with a leaderboard board or a second difficulty path. Anything you leave out gets a sensible default you can change later in the editor.

Download the .rbxlx, which is free on every plan, and double-click it with Roblox Studio installed. Press Play (F5) and run the course yourself: check that each gap feels fair, that every checkpoint catches you after a fall and that the timer stops at the end. Play Here, Run and a local server with several players all work, since the file is a regular place. If a stage is too punishing, ask the AI in the Spaleforce editor to widen it or slow the moving part, and download the updated file.

To ship the game, use File > Publish to Roblox in Studio, which creates the experience on your own account. Once it exists, you can also add a Roblox Open Cloud API key in the Spaleforce editor, link the project to that experience and publish later versions without leaving the browser, as a live update or a draft. The obby, its name, its icon and any Robux it earns stay yours.

Popular obbies grow in updates: a new world every few weeks, a harder secret path, seasonal decorations. Each of those is a plain-language request in the editor, for example add ten stages after the finish with an ice theme, or move the checkpoint on stage 14 closer to the jump. The scripts are checked with the same Luau type checker after every change, so a new trap cannot quietly break the stage counter.

Because the course is built from parts and Neon rather than uploaded meshes, the place stays light, which helps players on phones. You can still add your own meshes, decals and music in Studio once the layout is final.