How to Make a Track in PolyTrack: Editor Guide for Beginners (0.6.3)

The PolyTrack editor is a building tool: you lay the road, set its height, place the checkpoints and then test drive the result. A track only counts as finished when someone can drive from the start to the finish without getting stuck.

What the editor screen gives you

The editor puts the build tools on screen:

• Test — drive the track you have built.
• Generate — present in 0.6.3; this guide does not cover what it produces.
• Load and Save — keep a track and reopen it.
• Export — produce the code you share.
• Help — the editor's own instructions.
• Undo and Redo — step back when a layout goes wrong.

The piece palette sits on the right. The height readout sits in the corner with its own up and down controls, and Shift + scroll changes height while you build.

A build order that avoids rework

1. Place the start and finish first. Everything else is judged against whether the car can get from one to the other.
2. Add a short straight and test drive it. If the first ten seconds do not work, a longer track will not fix it.
3. Build corners with room to steer. Tight corners are a difficulty choice; blind corners with no run-off are usually a mistake.
4. Place checkpoints as you go, not all at the end. A checkpoint after a hard section keeps the rest of the track testable.
5. Add height and jumps last. Changing height changes landing distances, so do it before the final test, not after.
6. Test drive from the start. Testing from the middle hides the first problem on the track.

If a piece is in the wrong place, X deletes it and R or Space rotates it. Undo is faster than deleting a chain of pieces, so use it before you rebuild.

Editor controls

The same shortcuts are listed in the full controls guide, alongside the driving keys.

Checkpoints, finish and jumps

A track that cannot be completed is not ready to share. Check these before exporting:

• Start, checkpoints and finish are connected. A missing checkpoint can leave the finish unreachable.
• Every jump has a landing. A jump that drops the car into nothing is a dead end, not a shortcut.
• Gaps are clearable at racing speed. A gap that only works from a perfect run is too tight for a shared track.
• Hard sections have a checkpoint after them. Otherwise one mistake sends the player back to the start of the whole track.
• The finish is reachable from the last checkpoint. Test that last segment on its own, then test the whole run again.

Export and import track codes

Player-made tracks travel as track codes, not files.

1. In the editor, choose Export to produce the code for your track.
2. Send the code to the other player.
3. They open track selection, choose Import, and paste the code.

Current-format codes start with PolyTrack2. Older codes may start with PolyTrack1 or v3.

Do not assume an old or copied code will load. The format prefix tells you which generation of code you are looking at; if an import fails, check the prefix and ask the creator for a current code.

Beginner checklist

• The start, every checkpoint and the finish are present and connected.
• Test drive from the start reaches the finish.
• No jump drops the car with no landing.
• The hardest section has a checkpoint after it.
• The track is saved before you export.
• The exported code has been pasted back into Import once to confirm it loads.

Read next

• PolyTrack controls: driving keys and the full editor shortcut table.
• PolyTrack download and platforms: where the editor is available, and why there is no Steam version.
• PolyTrack hub: all guides and the 0.6.3 changelog summary.