Stuntin Map Planner

Open this page beside Roblox. Fill the skeleton on paper or in a note. Then build. The long tutorial is how to build maps. This tool is the filter that stops a two-hour tray binge from becoming a D-tier publish on the map list.

Skeleton (copy this)

1. Title (boring, true): __________________
2. Difficulty (easy / medium / hard): __________________
3. Feature count (max 1 on map one): __________________
4. Spawn — wide plate, nose toward piece one.
5. Warm-up — one curve or short flats.
6. Launcher — small kicker unless you already land tall ramps.
7. Landing — at least “two extra flats” longer than you think.
8. Rhythm (optional) — one wave section, not the whole map.
9. Feature (optional) — one loop or one tall kicker.
10. Brake-down — flats so boost drains.
11. Finish — wide, no last gap.
12. Checkpoints — every landing you failed in test.

If you cannot fill 1–3 in one sentence each, you do not have a map yet. You have a pile of blocks.

Block budget

• Map one: S-tier pieces only, plus one A-tier wave or loop.
• Map two: add one B-tier corkscrew if testers asked.
• Never start with C-tier moving plates on a 50-player race — how to race.

Write a max piece count before you open the tray. 40 is plenty. 200 is a museum.

Go / no-go before publish

Tick these in a starter car from getting started:

• I finished the line on the first try after a break.
• A friend who only read how to play could see the first piece from spawn.
• I did not need noclip to exist on my own track.
• Title matches difficulty.
• I retested after the latest alpha notes if a patch dropped this week.

Three or more boxes empty: do not publish. Drive more featured maps instead.

Session timer

• 10 minutes: skeleton on this page.
• 25 minutes: build.
• 10 minutes: test in a mid car from the vehicle list.
• 5 minutes: checkpoints and barriers.
• Publish or delete. Do not “just add one more loop”.

Builders on the builders page who skip the timer ship D-tier dumps at 2 a.m.

After publish

Paste the exact title in lobby once. Ask one person to Join. Watch where they explode. Edit that piece, not the whole line. Then stop for the night.

If you wanted a fancy overlay instead of a checklist, you wanted an executor. You wanted script safety instead. Come back to this planner the next time the tray looks like 200 toys.

Failure notes worth writing down

After a test drive, write one line only:

• “Wave two launches if boost is held” — delete a boost pad or flatten the hump.
• “Loop exit is a cliff” — add flats, then retest in a light car from the vehicle list.
• “Spawn camera faces the skybox” — rotate the plate until a stranger can see piece one.
• “Friend died where I never died” — you were in the wrong class. Retest in a starter body from getting started.

Four lines like that will improve a map more than another hour in the tray. The planner is a conversation with tomorrow-you, who will otherwise add a second loop because the first one looked lonely. Lonely loops are how D-tier happens. How to land is the other half of that conversation when the plate exists and the driver still explodes.

Related tools

Controls cheatsheet for the test-drive. Tools hub for the index. How to land if testers die on a plate that exists.