Checkpoint: start again after failure

Learning route

Prepare first, then do it; after seeing the result, remember to save it.

Every time a small step is completed, it is tested. Say what you expect to see first, and then use Play and Output to check it. Don't rush to write all the code at once.

Step by step

01 · SpawnLocation must be used

Ordinary Part can be used as a visual mark, but cannot be directly assigned to RespawnLocation. You need two real SpawnLocation objects.

In order to avoid randomly selecting checkpoints at the first birth, set the starting point Enabled=true and checkpoint Enabled=false. Enable checkpoints when players activate, and give each new player an explicit StartSpawn.

1. Rename the existing SpawnLocation to StartSpawn and set the Position to 0, 0.5, 0.
2. Insert the second SpawnLocation, name it Checkpoint, and set the Position to 0, 0.5, -30.
3. Both Anchored=true, Neutral=true, AllowTeamChangeOnTouch=false; Checkpoint.CanTouch=true, Enabled=false.
4. Create CheckpointManager in ServerScriptService.

Step by step

02 · Mark the checkpoint on the player

player.RespawnLocation saves a spawn point object reference. It belongs to this player and not to the Workspace shared by all players.

Scripts also specify a starting point for new players. So even if someone else has turned on Checkpoint, the player that entered will start with StartSpaawn.

1. Paste the complete script.
2. Don't go to the checkpoint after playing, reset the character once, and confirm that it is still at the starting point.
3. Go to the Checkpoint again and see if the Output displays the activation message.

local Players = game:GetService("Players")
local startSpawn = workspace:WaitForChild("StartSpawn")
local checkpoint = workspace:WaitForChild("Checkpoint")

local function setupPlayer(player)
    player.RespawnLocation = startSpawn
end
Players.PlayerAdded:Connect(setupPlayer)
for _, player in ipairs(Players:GetPlayers()) do setupPlayer(player) end

checkpoint.Touched:Connect(function(hit)
    local character = hit:FindFirstAncestorOfClass("Model")
    local player = character and Players:GetPlayerFromCharacter(character)
    local humanoid = character and character:FindFirstChildOfClass("Humanoid")
    if not player or not humanoid or humanoid.Health <= 0 then return end
    if player.RespawnLocation == checkpoint then return end
    checkpoint.Enabled = true
    player.RespawnLocation = checkpoint
    print(player.Name, "Checkpoint activated")
end)

Step by step

03 · Distinguish between personal progress and shared appearance

If you turn the checkpoint green on the server, everyone will see the green color. This does not mean that everyone has it activated. When determining personal progress, look at the corresponding Player.RespawnLocation.

Therefore, this lesson does not regard the entire scene turning green as evidence of "I have saved". Read Output and Player Properties first; once you learn LocalScript, you can create prompts that are only visible to you.

1. View your own RespawnLocation from the server's perspective while running.
2. Before activation it points to StartSpawn and after activation it points to Checkpoint.
3. The checkpoint is not an immediate transfer button. After assignment, it will only be used in the next rebirth.

Step by step

04 · Take a short road between two spawn points

Now add three more wide platforms and place the checkpoint after completing the first challenge. Make sure the solo respawn feature is reliable before making the level difficult.

There should be space above the spawn point, not against a low roof or caught in a wall. The character needs to stand safely when it appears, and cannot fall down immediately after being born.

1. Adds three mechanisms between the starting point and the check point.
2. Test that you can at least stand and turn around safely around checkpoints.
3. Baseplate is retained in this lesson and tested by resetting the character without creating a dangerous gap first.

Step by step

05 · Try "two people with different progress"

Multi-person inspection can best detect the error of "writing one person's progress as a global variable". A activates the checkpoint and B is still at the starting point. The two should respawn at different locations.

This is just a record of this session. Stop re-enters after it, and the new Player continues to start with StarSpawon; this is similar to the life cycle of the 10th class gold coin.

1. A resets after activation and should appear in Checkpoint.
2. B Direct reset without activation, should appear in StartSpawn.
3. Stop the test and start again, confirm that the starting point rule is restored.

Exit questions

Answer it yourself first, and then expand on it.

Explore further

This is where we start when we need to check the data.

The text code can be copied directly. First confirm the script type, placement, and whether this code is a complete version or a small experiment; do not run multiple versions of the same script superimposed. The source of the interface reference picture has been marked. The object names in the picture may be different from those in this lesson. Please refer to the operation steps.

• Player.RespawnLocation ↗
• SpawnLocation ↗