Roblox Obby Maker: plan an editable obstacle course

Name the starting area, the finish line, and the sequence of challenges between them. For a first course, three beats are enough: a safe jump that teaches movement, a middle section that introduces one new hazard, and a final section that combines familiar moves. A theme such as candy or sky islands gives the route character, but it should not hide the landing surfaces, checkpoint markers, or direction of travel.

In the prompt, explain what a player sees after each successful jump and after each fall. Ask for wide early platforms if the audience is new, or tighter timing if the course is intended for experienced players. These decisions make the plan review useful: you can spot an impossible gap or an unreadable turn before spending credits on a Build. You can also change the route while the plan is still a proposal.

Checkpoints make failure recoverable. Place one before a difficulty spike so a new player does not replay the whole course after one missed jump. Ask for clear hazard boundaries and a safe landing after moving platforms. Coins can reward exploration without blocking the main path. A finish reward gives the run a visible conclusion, but its trigger still needs a Studio test. If you want a change to any of these, state the affected section and expected player behavior.

The Roblox Obby Maker can turn those choices into a reviewable configuration and a downloadable Draft. It does not infer perfect difficulty from adjectives like 'fun' or 'hard'. Say whether the target is a quick first success, a longer practice course, or a route with optional coin detours. In review, check checkpoint spacing, hazard placement, platform motion, reward conditions, and retry clarity together rather than judging each feature in isolation.

After you continue, sign in and inspect the proposed scope, blueprint, and Build plan. The plan should make the route, major obstacles, intended checkpoints, and finish condition legible. You can ask for a specific adjustment during review; the Agent should distinguish a suggestion from a change that has actually been applied. Only confirm a Build when the playable loop described by the plan matches the game you want to test.

The resulting .rbxlx is an editable Roblox Studio starting project. Keep its Build ID and the previous version when you request another pass. A useful follow-up is narrow: 'move checkpoint two before the moving platform and widen the next landing' is easier to implement and verify than 'make it better'. The new Build can be compared with the old one, while any earlier Studio runtime result remains evidence for its own version only.

Open the downloaded file in Roblox Studio and run from a fresh spawn. Follow the intended route without editor shortcuts, deliberately fall near every checkpoint, and confirm where the player respawns. Test moving platforms from both an easy and a late arrival, touch each hazard, collect and miss coins, and reach the finish twice. Note the Build ID with your findings so later edits do not inherit untested claims.

If a jump feels unfair, report the precise section and what happened. You can then revise the generated project and retest the new Build. Device controls, actual physics, asset rights, and publication still require their own checks in Studio and Roblox workflows. This page offers a starting route to an editable Draft; it does not promise browser play, an automatically published Experience, or a guaranteed player-retention result.