Many children know Roblox as players. Studio can change that relationship: instead of entering someone else's world, the student defines objects, properties, events, rules, and behaviour in a small world of their own. Familiarity helps, but it is not the same as knowing how to build.
The bridge to Lua
A student who has used events, variables, conditions, and state in Scratch will meet them again in Lua. The punctuation changes; the questions do not. What starts this function? Which object changes? Where is the score stored? What prevents one coin scoring twice?
Roblox belongs in a curriculum when it extends those ideas into typed scripts, functions, objects, and 3D coordinates—not as a prize for surviving visual programming.
A map needs systems
A detailed landscape can be an impressive piece of modelling without containing much programming. An obby becomes a coding project when checkpoints preserve state, hazards follow clear collision rules, and the difficulty is tested. A coin world needs reusable collection logic and dependable score rules.
The student should be able to point past the scenery and explain what the world remembers, checks, and changes.
Shared worlds add new questions
One variable may be enough for a single-player Scratch score. A multiplayer world raises harder questions: which information belongs to one player, which belongs to the server, and what can another player change? These ideas need a careful sequence.
The first goal is a dependable small system, not a commercial-scale game. Servers are not impressed by ambition.
Assets have a history
Studio makes it easy to import models and scripts. Students need to know what they created, what the platform supplied, and what arrived from elsewhere. An attractive free model can also contain code the student has never read.
Original work, attribution, and inspection of imported behaviour are part of programming responsibility on a platform built for sharing.
Why the program is listed for later
School of Code needs clear decisions about accounts, privacy, publishing, external models, collaboration, and device performance before Roblox classes open. The curriculum must also teach Lua and system design rather than drift into decoration or copied scripts.
For now, Roblox Studio / Lua is marked Coming later. Scratch and Robotics are active now and teach ideas that will transfer when the account details and course sequence are ready.
Publishing is a separate decision
When the program opens, publishing cannot be treated as an automatic final step. A project can be built and reviewed without making it public. Names, chat, collaboration permissions, and any material borrowed from elsewhere need rules that parents and students can understand before accounts are used.
The eventual course should therefore be judged by what students can explain and change, not by whether the world resembles a popular Roblox genre. A modest obby with sound state logic is a stronger beginning than a vast copied map with an unknown collection of scripts running underneath it.