The Project panel✎

The project's files and its place's DataModel, and what each colour, icon and menu in them means.

Reviewed

The Project panel is a card on the left of the editor; the button after the mark shows and hides it. It lists the project's files and, when the project has a place, the place's instances.

Over the project tree, with a place open.

Hover a control or its row to light the other.

  • Files | DataModelWith a placeThe project's files, or the place's instances as Studio's Explorer lists them.

The headings

HeadingHolds
GraphsYour graphs, from the services down. The folder they live in is a setting, Settings › Compiling › Graphs live in, so it is not a row. New graph makes one at the top
Node mapsWhere your files land in Studio. A map's row shows the project file it writes, green when written as the map has it, and Serving on the one rojo serve reads; Serve on another swaps it in. Unfold a map for what it syncs; a row opens the map there. clash marks two maps writing one file, and neither writes it. New map makes one at the top
PackagesWhat wally.toml depends on, by realm: Shared is Packages/, Server ServerPackages/, Dev DevPackages/, each with where a map lands it. Each package is a ModuleScript with the package mark and its version; +1 dependency opens what Wally installed with it, vendored is code from a zip or GitHub, and not installed has Install on its menu. Add opens Add a package: from Wally, a zip or GitHub. sync… on a realm turns on autosync, which keeps its folder synced in the served map, in a service or a path you give; a realm listed but not installed is mapped as optional, which needs Rojo 7.1 or later. Settings › Compiling › Wally packages sets all three.
PlaceThe place in use, marked in use, and the others waiting in .roswaal/places. Open shows the place in use in the Place Editor; Use swaps another one in, and is refused while Studio has either open. Add keeps a copy of the place, a place file or a baseplate there. A Roblox project with no place has Add Place here
OutputWhat Roswaal writes, and code it did not, from inside src as Graphs is from inside its folder, then place/ and .luaurc. A folder of generated Luau folds to a count. What needs a look is marked: stale (its graph is gone; Remove on its menu), hand-written, imported and place, and the heading counts those. Luau there opens read-only
Node packsThe nodes the project adds. Double-click a pack to open Node Design. It starts folded

Each heading folds from the chevron by its name. Drop a file on Graphs to move it to the top.

Colours and icons

IconMeans
A service's or container's own iconA folder named for it, as Studio's Explorer shows it
A node map in the cornerA folder a node map syncs; hover it for the map
A faint folder saying emptyA folder with nothing in it yet
A dot after a graph or mapEdits not saved yet, as on its tab. Hover a graph for its file and the Luau it compiles to
A grey outlined folderA plain folder
A grey filled folderA Folder a node map syncs, under Output
A blue filled folderA script in Studio, with the rest of the folder as its children
A red filled folderplace/: scripts only the place can hold
A purple filled folderPackages/: Wally's packages
A white or slate scriptA Script: white on a dark theme, slate on a light one
A green scriptA LocalScript
A blue scriptA ModuleScript

New graphs and folders

Point at a graph or a folder under Graphs and two buttons appear at its right: New graph and New folder. On a folder they make one inside it. On a graph, New graph asks whether inside it, as its child, or beside it, and New folder goes beside it. Pressing one leaves the folder open or shut as it was. On a touch screen they show on the row you tap. New graph, New map and New folder list the graphs' folders under the name, starting where you were: go into another to make it there, or press New folder in the list to make one first.

A yellow border marks a graph or folder no node map syncs: its Luau is written, and Rojo never sees it. A folder holding a synced one, as ReplicatedStorage holds Tank, is not marked.

Menus

Right-clickOffers
A folder or a fileNew graph here and New map here under Graphs, New folder, Show in file manager, Rename and Delete
A graphNew graph…, which asks where: inside it, as its child, or beside it in its folder. Open Luau opens the Luau it compiles to, read-only, and Show Luau in file manager finds it
A .luau you wroteImport as graph as well: a new graph that compiles back to that file. Its prompt names the risks and asks what file-level locals become and how the graph reads. It is laid out in rows as the file reads, keeping its blank lines. Names and types stay as the file has them, and a name that hides a global or a service is flagged on its node. A line such as local Players = game:GetService("Players") becomes one of the graph's services, and a method call becomes its node where the importer knows what it is called on. function foo() becomes a Declare Function that writes function foo() back unchanged, so its body is nodes too. Modern offers rewrites, each a choice: game.Players and its kind to declared services, :connect to :Connect, and, off to start because their timing differs, wait, spawn and delay to task.*. The file stays as it is until you overwrite it, after seeing what changes
A package, or Add on the Packages headingAdding and removing packages. See Wally packages

Scripts with children

New graph… on a graph puts the new one inside it, unless you choose Beside. The first child makes the graph its folder's init.nodescript, so Greeter.nodescript becomes Greeter/init.nodescript, and puts the child beside it. It compiles to Greeter/init.luau, as Rojo makes a folder holding an init file a script. The tree shows the folder as the script, named Greeter; double-click it to open its graph. In Dynamic mode its Luau moves at once.

Drag the script to move it, children and all, or rename it. Its own init.nodescript does not move alone. A child's module is require(script.Child) from the script, and its Script Functions and types are offered as any module's are.

Deleting a graph deletes the Luau Roswaal wrote for it. A script whose last child goes stays in its folder, unless Settings › Compiling › When the last child goes moves it back out.

Info

A graph and a folder of the same name side by side would be two instances Studio calls by one name, so Roswaal refuses to make or move one beside the other.

Opening everything inside

Shift + click a folder, or an instance's arrow in DataModel, to open or close it with everything inside it, as in Studio's Explorer.

Dragging from the tree

Drag a graph or a .luau onto the canvas for Require Module with its path filled in, or Instance for a reference to it. Drag a file onto a folder to move it.

Files and DataModel

With a place, Files and DataModel sit at the right of the panel's heading. DataModel lists the place as Studio's Explorer does. Double-click an instance for Properties, on the right under the Inspector; on a tablet or a phone, double tap and it slides out. Editing a place has the rest.

Last reviewed 30 September 2026 by @neopolitans