Guide · 24 October 2026
Building a Roblox Studio Obby: Obstacle Course with Checkpoints and Lava
By Liska, has been playing Roblox and Murder Mystery 2 for almost three years
An obby is made of anchored platforms, SpawnLocations as checkpoints and dangerous surfaces. Here is how to build one in Roblox Studio, write a short lava script and test everything with F5.
Contents
An obby is an obstacle course: you jump across platforms, dodge hazards and make your way to the goal step by step via checkpoints. In Roblox Studio you build it from anchored parts, SpawnLocations as checkpoints and a hazard surface with a short script. This guide is the fourth part of our Studio series. You should have read Roblox Studio for Beginners. You can add landscape and lighting later: Terrain and Landscape and Lighting for Day and Night go well with an obby. What Roblox actually is, we explain in What is Roblox?.
As of 24 October 2026. On that day we checked five pages of the Roblox documentation (Parts, SpawnLocation, Teams, testing modes, tutorial “Deadly lava”). Our own tips are marked as such.
What an obby is and how to plan one
An obby has a start, several sections and a goal. Each section is a row of platforms. Between the sections there is a checkpoint. Our tip: draw the route on paper first. Three to four jumps per section are enough to begin with. That is not a rule from Roblox, just a recommendation from us.
Building platforms
Platforms are parts. According to the documentation on Parts, the Part button in the Home or Model tab inserts a new part into the Workspace. Using the small arrow at the corner of the button, you choose the shape: Block, Sphere, Wedge, Corner Wedge or Cylinder. For platforms you will mostly use blocks.
Here is how to do it:
- Insert a block and turn it into a platform with the tools for size and position.
- In the Properties window, enable the Anchored property. According to Roblox: “Anchored controls if physics affects the position of the part.” Without Anchored, the platform would fall away due to gravity after the start.
- Duplicate the platform and place the copies one after another with some space between them.
Testing the gaps
The documentation does not say how wide a gap can be for a jump to still work. You have to try it out. Our tip: build the first gaps rather small, run through them in a test and widen them step by step. Test every jump yourself in Test mode (F5). That way you quickly notice which jumps are too hard.
Checkpoints with SpawnLocation
A checkpoint is a SpawnLocation. According to the documentation on SpawnLocation, SpawnLocations determine “where a Player respawns when they die”. The same page says they can be used “as checkpoints, such as in an obstacle course”. Four properties matter:
- Neutral: If set to true, any player from any team can spawn there. If false, only players whose TeamColor matches the TeamColor of the SpawnLocation may start there.
- TeamColor: It determines which team the SpawnLocation belongs to.
- AllowTeamChangeOnTouch: If set to true and a player touches the SpawnLocation, their TeamColor is set to the TeamColor of the SpawnLocation.
- Duration: This is how long (in seconds) a newly spawned player gets a ForceField. According to the documentation, the default value is 10 seconds. At 0, no ForceField is created at all.
For this to work, every checkpoint needs its own team. The SpawnLocation page describes the setup this way, and its code example “SpawnLocation Checkpoints” creates a start team and checkpoint teams for it:
- Create teams: According to the page on Teams, you hover the mouse over the Teams service in the Explorer, click the ⊕ sign and insert a new team (“Insert a new Team object under the Teams service”). In the Properties window, give it a name and its own TeamColor. Do this for the start and for every checkpoint.
- Only the start is automatic: According to the SpawnLocation page, “only the first Team” should have AutoAssignable turned on, “else players will not start at the first checkpoint”. For all other teams, untick AutoAssignable.
- Set up the SpawnLocations: Every SpawnLocation gets Neutral = false and the TeamColor of its team. At the start, AllowTeamChangeOnTouch is set to false, at every further checkpoint to true.
- Each colour only once: If several SpawnLocations match a player, the documentation says “a random one” is chosen. Then you might end up at the wrong checkpoint.
Teams are sometimes created automatically when you insert a SpawnLocation with Neutral = false. But Roblox advises to “always set up their teams manually”, that is, by hand.
Also pay attention to Enabled: if a SpawnLocation is disabled, nobody can spawn there, and AllowTeamChangeOnTouch does not work.
A dangerous surface: lava
The Roblox tutorial Deadly lava builds lava like this: a part named LavaFloor, material Neon, orange colour, and inside it a script named Kill. The code comes from this tutorial:
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)
What happens here? “Every part has a Touched event that fires when something touches it.” Every body part of your character belongs to the Character model, which you find with otherPart.Parent. There you look for the Humanoid. If there is one, you set Health to 0. Then the character dies and reappears at the last touched checkpoint, provided the teams are set up as described above. The tutorial itself suggests: “Try using your lava as an extra challenge in an obby, or as a boundary for a world.” So place the lava underneath the platforms.
Testing with F5 and Stop
According to the page on testing modes, you choose the mode in the dropdown and then click Play. F5 starts Test mode, in which your avatar appears at a SpawnLocation (if there is none, roughly at the coordinates 0, 100, 0). Run (F8) starts without an avatar. Stop (Shift+F5) ends the test, and Stop “resets all objects and instances to how they were before the playtest”.
Check three things in every test: Can you make the jumps? Do you reappear at the last checkpoint after falling into the lava? Does every platform stay in place?
Where the information comes from
All facts come from the English-language Roblox documentation in the Creator Hub:
- Parts: inserting a part, shapes, Anchored.
- SpawnLocation: Neutral, TeamColor, AllowTeamChangeOnTouch, Duration, Enabled, checkpoint setup with teams.
- Teams: inserting a team, name and TeamColor.
- Deadly lava: lava part, script, Touched, Humanoid.
- Testing modes: Play, Run, Test (F5), Stop.
Conclusion
An obby needs anchored platforms, SpawnLocations as checkpoints and a hazard surface with a Touched script. Build in small sections and test after each section with F5. You will only find the right gaps by trying them out. That way your course grows step by step.
Frequently asked questions
What does Anchored do on a platform?+
According to the Roblox documentation: “Anchored controls if physics affects the position of the part.” If the platform is anchored, it stays in place. The page advises anchoring most parts, because otherwise gravity and physics move them after the game starts.
How does a checkpoint with SpawnLocation work?+
According to the documentation, SpawnLocations can be used “as checkpoints, such as in an obstacle course”. For this, every checkpoint, including the start, gets its own team with its own TeamColor. Only the start team has AutoAssignable turned on. All SpawnLocations are set to Neutral = false and carry the colour of their team. At the checkpoints, AllowTeamChangeOnTouch is on: whoever touches the pad switches to that team and reappears there after a fall.
How do I make a lava surface defeat a character?+
You need a script inside the part that listens for the Touched event. The Roblox tutorial “Deadly lava” finds the character via otherPart.Parent, looks up the Humanoid with FindFirstChild and sets its Health to 0. Then the character dies: “If you set its Health property to 0, the associated Character dies.”
How do I test my obby?+
According to the Roblox page on testing modes, you start with Play and stop with Stop (Shift+F5). Stop “resets all objects and instances to how they were before the playtest”. So your changes from the test do not stick in your build.