Build a Mini Race Track with Checkpoints
Build a Mini Race Track with Checkpoints
Do you like racing fast cars in Fortnite? You can build your own track!
We will use special devices called Race Checkpoints. These help players know where to go.
You will learn how to set up a start line and finish line. Then, you can race your friends.
What You'll Learn
- What a Race Checkpoint device is.
- How to place checkpoints in order.
- How to rename devices to keep things tidy.
How It Works
Think of a race track like a treasure hunt. You need clues to find the prize.
Race Checkpoints are those clues. They tell the game where the path goes.
When a player drives through a checkpoint, the game knows they are on track.
If they miss a checkpoint, they might not get a fair score.
We will place three checkpoints. One for the start. One in the middle. One for the end.
This makes a simple loop. Players can drive around it again and again.
Let's Build It
We will use the Event Browser to find our devices. The Event Browser is like a toolbox.
It holds all the devices you can use. We will look for "Race Checkpoint."
First, place your first checkpoint. Call it "Start."
Next, place a second checkpoint. Call it "Middle."
Finally, place the last one. Call it "Finish."
Now, we need to connect them. We use Events. An Event is a signal.
It says "Hey game, this happened!" We will send a signal from Start to Middle.
Then, we send a signal from Middle to Finish.
Here is the code to make it work. It is simple and short.
# This code connects the checkpoints
# It tells the game what happens when a player passes them
# First, we define the devices
# These are the boxes we placed in the world
Start_Checkpoint := Race_Checkpoint_Device
Middle_Checkpoint := Race_Checkpoint_Device
Finish_Checkpoint := Race_Checkpoint_Device
# This function runs when someone hits the Start
On_Start_Hit := func():
# Tell the Middle checkpoint to get ready
Middle_Checkpoint.Set_Active(true)
# Show a message to the player
Print("Go! Drive to the middle!")
# This function runs when someone hits the Middle
On_Middle_Hit := func():
# Tell the Finish checkpoint to get ready
Finish_Checkpoint.Set_Active(true)
# Show a message to the player
Print("Great! Drive to the finish!")
# This function runs when someone hits the Finish
On_Finish_Hit := func():
# Stop the race timer
Race_Manager.Stop_Timer()
# Show a big message
Print("You won! Race complete!")
Let’s look at the code.
The first part names our devices. It is like giving names to your toys.
The On_Start_Hit part waits for a player. When they hit the start, it wakes up the middle checkpoint.
The On_Middle_Hit part waits for the next spot. It wakes up the finish line.
The On_Finish_Hit part is the best part. It stops the timer.
It tells everyone the race is over.
Try It Yourself
Can you add a fourth checkpoint? Try adding a "U-Turn" checkpoint.
Make the player drive around a big circle.
Hint: You just need to add another line for the new checkpoint.
Then, add another On_U-Turn_Hit function.
Recap
Race Checkpoints guide players through a track.
They help the game know where the player is.
You can rename them to stay organized.
Now you can build fun race tracks!
References
- https://dev.epicgames.com/documentation/en-us/fortnite/using-race-checkpoint-devices-in-fortnite-creative
- https://dev.epicgames.com/documentation/en-us/fortnite-creative/using-race-checkpoint-devices-in-fortnite-creative
- https://dev.epicgames.com/documentation/en-us/fortnite/make-your-own-ingame-leaderboard-in-verse
- https://dev.epicgames.com/documentation/en-us/uefn/make-your-own-in-game-leaderboard-in-verse
- https://dev.epicgames.com/documentation/en-us/fortnite-creative/using-devices-in-fortnite-creative
Verse source files
- 01-fragment.verse · fragment
Turn this into a guided course
Add using-race-checkpoint-devices-in-fortnite-creative to your free study plan — we'll suggest related pages and stitch the lot into one compile-checked, self-guided lesson with worked examples and quizzes.
References
Original tutorial generated by Verse Island from the Verse/UEFN knowledge base, with references to the Epic Games sources above. Code is validated against the knowledge base.