Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 37 ยท Studio and Basics

The Explorer, Instances and Properties

Learn how Roblox organises a place as a tree of instances, how classes, properties, names and parents work, and how scripts find, clone and destroy instances.

Everything in a Roblox place is an instance: a part, a light, a sound, a script, even the camera. Instances are arranged in a tree, and the Explorer window shows that tree. Once you understand instances, classes, properties and parents, scripting becomes mostly a matter of finding the right instance and changing the right property.

Classes, instances and properties

A class is a blueprint such as Part, PointLight or Sound. An instance is one object made from that blueprint. Every instance has:

  • a ClassName, such as "Part" (read-only).
  • a Name, which you choose; two siblings may share a name, but avoid it.
  • a Parent: the instance it sits inside. An instance with no parent does not exist in the world.
  • Properties: values that depend on the class. A Part has Color, Size, Position, Anchored and Transparency. A Sound has SoundId and Volume.
  • Children: instances parented to it.

Classes can inherit from one another. For example, Part and MeshPart share the base class BasePart, which defines Size, Position, Anchored and more. The official Creator Documentation lists every class and its properties, methods and events.

The tree of the world

When you open a place, the Explorer shows the top-level services. The ones you use first:

TEXT
Workspace             the 3D world: parts, models, terrain, camera
Players               the connected players
Lighting              sky, brightness, time of day
ReplicatedStorage     shared things both server and clients can see
ServerScriptService   server-only scripts
ServerStorage         server-only assets
StarterGui            interface copied to each player
StarterPlayer         scripts and settings copied to each player

The services lesson describes each. In this lesson we focus on the Workspace and the generic skills you use everywhere.

Working in the Explorer

  • Insert an object: hover a parent, click +, then choose a class.
  • Rename: select and press F2.
  • Reparent: drag an item onto another to move it.
  • Group parts into a Model with Ctrl+G, so you can move or script them together.
  • Expand all: click the arrow next to a parent; hold Shift for the whole subtree.
  • Filter: type in the box at the top of the Explorer to search by name or class.

A Model is a container for parts that act as one object (a car, a tree, a house). A model can have a PrimaryPart, the part it pivots around. A Folder is a pure organiser with no position, ideal for tidying large places.

Properties in the Properties window

Select a part and the window lists its properties. Click a value and type, or use the colour picker. Some useful ones now:

Property Meaning
Anchored If true the part never moves from physics
CanCollide Whether other parts bump into it
Transparency 0 is solid, 1 is invisible
Material Plastic, Wood, Neon, Glass, and more
Size Width, height, depth in studs
Position Where its centre is in the world

Hold Shift while selecting properties to edit several parts at once. You can multi-select parts in the viewport or Explorer, then change one property for all of them.

Reaching instances from a script

Scripts use the same tree. These Luau snippets are real Roblox code; to run them, paste one into a Script in ServerScriptService and press Play.

LUA
-- Dot syntax: parent.ChildName
local block = workspace.Block
print(block.ClassName, block.Name, block.Parent.Name)

-- Properties are read and written with a dot
block.Color = Color3.fromRGB(255, 80, 80)
block.Transparency = 0.25

-- Safe lookups when you are not sure the child exists
local maybe = workspace:FindFirstChild("Coin")
if maybe then
	maybe:Destroy()
end

-- Walking the tree
for _, child in workspace:GetChildren() do
	print(child.Name)
end

Important functions on every instance:

  • instance:FindFirstChild("Name") returns the child or nil, without erroring.
  • instance:WaitForChild("Name") pauses until the child appears (essential for client code, where things stream in).
  • instance:GetChildren() returns the direct children; GetDescendants() returns every nested one.
  • instance:Clone() makes a copy. The copy has no parent until you set one.
  • instance:Destroy() removes it permanently and disconnects its events.

The dot lookup workspace.Block errors if Block does not exist. When in doubt, use FindFirstChild.

Set Parent last when you build instances in code. Every property change on a part that is already in the world is replicated and simulated; setting the parent after configuring is faster and safer.

Attributes and tags

Not every setting is a built-in property. Attributes are custom named values you attach to any instance: add them in the Properties window (Attributes section) or in code.

LUA
block:SetAttribute("Health", 100)
print(block:GetAttribute("Health")) --> 100

Attributes appear in the Properties window and replicate to clients. Tags (via CollectionService) are labels you attach to many instances so a script can find them all, such as every instance tagged "Hazard".

A stand-in for the instance tree

Here is the idea in JavaScript: instances with names, parents, children and the main tree methods. It is a model, not Roblox itself. Try changing the tree and the searches.

JS Stand-in: FindFirstChild, Clone and Destroy (JavaScript)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that the clone has no parent until you assign one, and that destroying a model destroys its children too, exactly as in Studio.

Searching with a predicate

A common job is "find every instance of a kind". Real Roblox gives you GetDescendants() plus a loop with IsA (a class check that also accepts base classes). Here is the idea:

JS Stand-in: find all parts of a kind (JavaScript)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In real Luau the call is if descendant:IsA("BasePart") then ... end.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does an instance with no Parent mean for the world?

    An instance only takes part in the game when it sits somewhere in the tree. With no parent it is not in the world.
  2. 2. Which call finds a child without raising an error if it is missing?

    FindFirstChild returns nil when the child does not exist, while dot access errors.
  3. 3. What is a good reason to set Parent last when building a part in code?

    Changes to a part already in the world are simulated and replicated, so configure it first, then parent it.
  4. 4. What does Clone return?

    A clone is a new instance with no parent, so you must parent it for it to appear.

Summary

  • A place is a tree of instances; each has a class, Name, Parent, properties and children.
  • Use the Explorer to organise, the Properties window to edit.
  • In scripts, use dot access, FindFirstChild, WaitForChild, GetChildren, Clone and Destroy.
  • Attributes and tags attach custom data and labels to instances.

Next: Your First Script and the Output Window