How to Make a Roblox Obby: Studio or AI

Open Studio and choose the Baseplate template, which starts with a baseplate and a SpawnLocation. Move the spawn to your starting area and use simple blocks to mark the main sections and the finish. Roblox’s guide to creating games lists the starting templates.

Use the Part button on the Home or Model tab to insert a block, then move, scale and rotate it into your first landing. Set Anchored to true on platforms that should stay still, or gravity will pull them down when the game runs. Duplicate platforms to extend the route, keeping early landings wide and easy to see. Roblox’s parts guide covers the part types and properties.

To try it, choose Test in the playtest menu on the left of the mezzanine and click Play (or press F5). Adjust one jump at a time. How far a player can jump depends on your movement settings, height changes and landing size, so test each gap rather than copying one measurement everywhere. Add moving platforms only after the still route works.

A kill brick sends a player back to their spawn by setting the character’s health to zero. Insert a Script inside an anchored hazard Part and replace the default code with this:

local lava = script.Parent

local function kill(otherPart)
	local partParent = otherPart.Parent
	local humanoid = partParent:FindFirstChild("Humanoid")
	if humanoid then
		humanoid.Health = 0
	end
end

lava.Touched:Connect(kill)

Give the hazard a distinct look, such as the Neon material and an orange color, and leave a visible safe path around it. Roblox’s deadly-lava tutorial explains each line. Test the hazard before you copy it across the course.

One way to save progress uses Teams, so each player belongs to the checkpoint they touched last. Roblox’s SpawnLocation checkpoint example shows the full setup. Keep these settings together:

1. Create a starting Team and one Team for each checkpoint, each with its own TeamColor.
2. Set AutoAssignable to true only on the starting Team.
3. Give each Team an anchored SpawnLocation. Set its Neutral property to false and match its TeamColor to the Team.
4. Set AllowTeamChangeOnTouch to true on checkpoint spawns and false on the starting spawn.

Play from the start, reach a checkpoint and fall on purpose. Then repeat with a second player to check that progress is individual. This setup tracks the current run; keeping progress after a player leaves is a separate system to build and test.

Give the end a landmark players can recognize and add feedback when they reach it. If you add a timer or a restart button, decide what each does after a death and after a finished run. Keep decoration away from landing spots and leave room for the camera. Save the place, then work through the playtest checklist below.

Open Create. Build levels are not plans, but your plan decides which levels you can choose: Free and Lite use Light, Pro adds Medium, Max adds High, and Ultra and Ultra+ add Ultra. Light works well for a short course. Builds and edits draw on your weekly usage allowance, shown in your account.

Say where players start, how the route climbs, what happens after a fall and how the course ends. For example:

Build a beginner-friendly forest canopy obby. Start at a campsite facing a route of broad wooden platforms and branches. Lead players upward to a lantern lookout they can see through the trees. Put a glowing checkpoint on a resting platform halfway up; after a fall, each player returns to their own checkpoint. Give the finish a celebration and a restart option. Use warm lanterns, mossy bark and clear space around jumps and the camera.

If you have a reference picture for the canopy or the lookout, add it to guide the look.

PromptBlox makes one concept image as the visual reference, then builds the course while you follow the Activity feed and a 3D preview. You can send notes while it works. Look for a clear start, a connected route and a visible finish. The preview is for judging layout and looks; the real gameplay test happens in Studio.

Name the part of the course, the change you want and what should stay the same:

Widen the first landing after the canopy checkpoint and lower it slightly so the final climb starts with a forgiving jump. Keep the earlier platforms, the checkpoint behavior and the lantern lookout.

After a Studio playtest, describe what you saw: “Touching the canopy checkpoint still sends me to the start after a fall. Fix the respawn for that checkpoint.” Each change is saved to the project, and History keeps earlier versions.

Download the .rbxlx file and open it in Roblox Studio to inspect the parts and scripts and play the course. Roblox’s place file documentation explains how these files work. Edits you make by hand in Studio do not sync back into PromptBlox, so keep track of which file you tested.