Roblox Luau Tutorial for Beginners

What you will build

By the end, you'll understand the code behind a simple disappearing platform and be able to rebuild it in Roblox Studio.

Open full Studio project →

How to use this guide

1. Read
2. Try
3. Change
4. Run
5. Observe
6. Challenge yourself
7. Build it in Studio

What is Luau?

If you want to build games on Roblox — not just play them — you need scripting. Roblox uses Luau, and you write it inside Roblox Studio.

Official Roblox documentation describes Luau as derived from Lua 5.1, with Roblox-oriented enhancements such as optional typing and generalized iteration. In practice, many Lua beginner habits still apply, while Studio and the engine give you game objects, services, and events to control.

You write Luau in the Script Editor. Scripts live in the Explorer tree as Instances — the same hierarchy that holds Parts, Folders, GUIs, and services. Scripting is what turns a static place into a game: doors that open, coins that save, UI buttons that respond, and rounds that start on a timer.

Try your first Luau

What do you need / your first Studio script

Before your first line of Luau in Studio, set up: a Roblox account, Roblox Studio signed in, a Baseplate place, Explorer visible, and the Output window open (View → Output). Script Analysis is optional but helpful.

Beginner checklist: create a place → open Output → insert a Script under ServerScriptService → press Play → watch Output. Stop Play when you edit, then Play again so Studio reloads scripts cleanly.

print("Hello from BloxBuzz!")

Luau variables

Variables store values you reuse. In normal Roblox scripting, prefer local variables and functions — clearer scope and typically faster lookup. Names should be readable (coins, not c). If Output shows nil, the name is wrong, the value was never set, or you are reading outside its scope.

Change it: set 10 → 100, Run, and observe.

Data types

Luau functions

A function is a reusable action. Games call functions when a round starts, when a player joins, or when a purchase succeeds. Name functions after actions (giveCoins, resetRound), not vague labels like doStuff.

Challenge: create a heal() function that prints Healed!.

If / else — door lab

Interactive BloxBuzz simulation

if coins >= 10
    print("Reward")
end

Luau loops

Also learn while with a yield in Studio:

local countdown = 5
while countdown > 0 do
    print(countdown)
    task.wait(1)
    countdown -= 1
end

What happens if? Change 5 → 10 in the Browser Luau lab and Run.

Tables — inventory lab

Challenge: Add "Bow", sync the visual, then Run.

Events

Interactive BloxBuzz simulation

part.Touched:Connect(function(hit)
    print("Something touched the part!")
end)

Part property lab

Interactive BloxBuzz simulation — CODE → PROPERTY → VISUAL

What happens if? Transparency = 1, or CanCollide = false.

Script hierarchy

Script vs LocalScript vs ModuleScript

Server / game logic (fair rules, scoring). Place in server containers like ServerScriptService.

Exact behavior depends on type, location, and RunContext — these are beginner defaults, not absolute laws.

Where should my script go?

Click a location to learn what usually belongs there.

Client vs server

Interactive BloxBuzz simulation

Flagship project: disappearing platform

Build this in Roblox Studio

Difficulty: Beginner · Time: 10–15 min · Skills: variables, functions, properties, loops, timing

1. Create Part · Anchor · Rename DisappearPlatform
2. Insert Script as child
3. Understand script.Parent
4. Function changes Transparency + CanCollide
5. task.wait · restore · loop · test · change timing · debug

local platform = script.Parent

local function disappear()
    platform.Transparency = 1
    platform.CanCollide = false
    task.wait(3)
    platform.Transparency = 0
    platform.CanCollide = true
end

while true do
    task.wait(5)
    disappear()
end

Project challenges: disappear faster · stay invisible 5 seconds · change the behavior.

Predict the output

local coins = 10
coins = coins + 5
print(coins)

Fix the code

How to debug

1. Error
2. Read Output
3. Find line
4. Understand
5. Check object / location
6. Fix
7. Run again

Use Output, Script Analysis, print, warn, and Explorer before rewriting everything. When an error mentions a line number, jump there first — “attempt to index nil” almost always means something you thought existed is missing.

Common beginner mistakes

• Forgetting local — prefer local variables/functions.
• Wrong Explorer location — Script under ServerScriptService for server practice; LocalScript under client starters for UI.
• Infinite loop without task.wait() — Studio freezes.
• Missing then / end — parse errors; use Script Analysis.
• Not checking Output — the error usually explains the fix.

You learned

• ✓ Luau basics
• ✓ Variables
• ✓ Functions
• ✓ Events
• ✓ Conditions
• ✓ Loops
• ✓ Tables
• ✓ Script types

Next: practice in the Playground, try Challenges, then build Studio projects.

Deep-dive lesson pages will publish when each topic is fully written — no placeholder links.