Guides
Learn Roblox Scripting in a Week
The whole free course, one day at a time. Roughly 5 hours of guided lessons spread across 7 days — with lighter days built in so you don't burn out.
Meet Studio
Light · ~32 minInstall Roblox Studio, find your way around, write your very first script, and make your first bug-hunt fixes. No code experience needed.
Speak Luau
Full day · ~47 minThe core vocabulary of every script: variables, types, numbers, strings, booleans, and functions that return answers.
Control the flow
Full day · ~44 minMake your code decide and repeat: conditionals, loops, for loops, tables, timing, comments, and events. Ends with a bug hunt.
Data that persists
Full day · ~49 minLeaderboards, saving between visits with DataStores, and why the server — never the client — is the source of truth.
- Recap — the Luau toolbox
- leaderstats — the player leaderboard
- Players — who is in your game
- UserId — the permanent key
- DataStores — saving between visits
- Loading a player's data
- The save loop and autosave
- Data security — never trust the player
- RemoteEvents — the client asks, the server decides
- Bug hunt — player data
Build game systems
Full day · ~56 minTurn clicking into coins: GUIs, UDim2, styling, the clicker loop, idle income, upgrades, the shop panel, and ModuleScripts.
- Recap — player data and trust
- GUIs — building interfaces in code
- UDim2 — sizing and placing GUI
- Making GUIs look good
- The clicker game — clicks become coins
- Idle income — coins without clicking
- Upgrades — spending coins with the server checking the bill
- The shop panel — a frame full of buttons
- ModuleScripts — organizing your code
- Bug hunt — game systems
- Drag and drop — the shop
Bring the world to life
Medium · ~45 minPlayers and their characters, building the world in code, attributes, sounds, and smooth tweens. A slightly lighter day — finish it with a bug hunt.
Ship it
Finish line · ~56 minPublish your game and switch on real saves, then level up your debugging skills and build the complete final project — one playable game.
- Recap — the world and the players in it
- Publishing — getting your game online
- Permissions and sharing
- Testing saves — the live persistence loop
- Recap — taking your game live
- Debugging — reading errors like a pro
- Print debugging — narrating your code
- The classic errors — and their smell
- Next steps — the map of what you've learned
- Recap — everything you've built
- The final project — one complete game
How to use this plan
- Do the lessons in order, and don't rush — the recap and bug-hunt lessons are where the learning sticks.
- On the full days, take a short break between every two or three lessons.
- Type every example out yourself instead of copying. You'll hit typos — that's good practice, not a failure.
- Use the Luau playground to experiment with anything that feels fuzzy.
Behind by a day?
The plan has slack built in: if a day runs long, skip nothing from that day but keep your pace. The recap and arrange (drag-and-drop) lessons are the easiest to compress if you're truly pressed for time.
Why this order works
Each section builds on the last: you learn the language before touching data, data before GUIs, and GUIs before the client-server bridge. By day 7 you've assembled every system into one complete, publishable game — see the final project.