Roblox Studio Explorer
- The Explorer window shows a hierarchical list of every object inside a place
- It uses the concept of parenting to organize all of the objects. If an object has any children, it will show a small arrow next to its name
- It holds objects that exist in the 3D world. Objects can still exist outside of Workspace, but they will not be physically rendered or active in the game -- objects which aren’t currently needed should generally be placed in ReplicatedStorage or ServerStorage.
- Contains individual Player objects for clients currently connected to a Roblox game server
- Includes adjustable properties which control the environmental lighting in a game
- Contents here replicate to each client before anything else in the game, making it ideal for custom loading screens. For objects that do not need this prioritized replication, use the ReplicatedStorage container instead
- Objects here replicate to all connected clients, meaning they can be accessed from either a server-side Script or client-side LocalScript. However ServerStorage is a more optimal container for objects which only the server needs access to
- Container for server-side game logic. Scripts can be securely stored and run from inside this service without replicating to game clients
- Objects here are held in storage until they're required, such as treasures that drop from a defeated enemy. These objects can be placed in ServerStorage, although they will need to be cloned and parented elsewhere (such as Workspace) before clients can access them. ServerStorage is also a valid container for ModuleScripts which only the server needs access to
- Holds GUI objects such as ScreenGuis. When a player's character spawns, children of this container are copied (along with their descendants) into the player's PlayerGui, an object which is automatically inserted into their Player object
- Contents are copied into each player's Backpack when their character spawns. It's generally used to hold tools, but it may also hold LocalScripts to ensure that each player gets a copy
- When a player enters the game server, each property of their Player object is set to the corresponding property value in StarterPlayer. This object also contains two script containers:
- StarterCharacterScripts can contain scripts that will be added to each player's character every time they spawn.
- StarterPlayerScripts can contain scripts that run once for each player when they join the server.
- specifies various aspects of how Sounds play in the game
- Contains the Lua code responsible for running the Lua Chat System
- Responsible for handling automated in-game translation