Boss fight — the gauntlet.
No new code. This is where you prove you can build with what you have.
A friend or family member plays your obby from start to finish, dies at least once, and reaches the trophy.
A mechanic isn't a game. Five mechanics, arranged, is.
Everything on this page is a script you already wrote. The boss fight is composition — arranging your five mechanics into something a real person wants to finish. And the win condition is not code that runs. It's a player who plays.
Construct the course.
The floor is lava — a big Really-red damage brick (Mission 3 script) as the ground under everything. Falling costs 20 HP.
The path — a trail of normal Anchored parts to jump across.
Coin alley — five or more coins along the path (Mission 4). Risky coins off the main path are worth more.
The launch gap — a hole too wide to jump, crossed only by launch pad (Mission 5). Aim it with Vector3.new(0, 50, 100) and rotate the pad to point across the gap.
The trophy — a golden part at the end with a coin script inside, reward = 100.
Every platform Anchored (unanchored parts fall when the game starts) · every damage brick flashes so players know what hit them · the launch pad tested until it reliably lands players on the far side.
Someone else plays it without you touching the keyboard. Watch where they get stuck and where they smile — that's your first playtest, and playtests are how every great game gets made.
600 XP. Quest complete.
You now use, from memory: variables, functions, events, if-checks, debounce locks, FindFirstChild, object creation, Vector3, and two-script systems. Those aren't "beginner tricks" — they're the same primitives every front-page Roblox game is built from.
A checkpoint system (respawn at the last pad you touched), a trap that chases you, a shop that spends your coins.
File → Publish to Roblox. Your game gets a real page other people can visit. That's shipping.
🔧 Stuck on anything, anywhere
The golden rule: add print("got here") lines to your script. If a print doesn't show in Output, the code above it never ran — now you know where the problem is. This is genuinely how professionals debug.
You don't learn a hundred things — you learn ten things and combine them. Go build something nobody asked for.