Organizing Your Project
Use folders and groups to organise the project tree, and learn the slug and reach rules they bring.
Organizing Your Project
As a design grows, the project tree on the Design tab keeps it manageable. This guide covers folders, moving things around, and the rules groups bring for slugs and for which elements can use which.
Folders
Folders organise the project tree for your team. They have no effect on your game: moving something into or out of a folder never changes its path.
- Add a folder — hover a row in the project tree, click + and choose Folder. Enter the folder's name (e.g. "Economy"). Folders can be nested up to 8 levels deep.
- Rename or delete a folder — hover it and click Rename folder or Delete folder. Deleting a folder doesn't delete what's in it: its contents move up a level, and Leap tells you how many elements will move before you confirm.
Tip: An empty folder is only kept in your browser until you put something in it. Move something into a new folder to keep it.
Moving Things Around
Drag systems, groups and folders in the project tree to reorganise them. Moving between folders happens straight away. Moving into or out of a group changes paths your game uses, so Leap asks first — "Move into …" or "Remove from …" — and shows an example of the old and new path. Click Move or Take it out to confirm.
Every element's Inspector also has a group field below Tags. Changing it asks for the same confirmation before the element moves.
Slugs Inside Groups
Resource, constant, flag, achievement and formula slugs only need to be unique within their group — the top level counts as a group of its own — so gold can exist both at the top level and inside Daily Rewards. Entitlement and group slugs are unique across the whole project.
If the slug is already taken in the group you're moving an element to, Leap refuses the move and names the element that uses it — rename one of them first. Renaming an element to a slug that's taken in its group shows an error such as "Resource slug must be unique within its group — “gold” is already used by “Gold” at the project root".
Which Elements Can Use Which
When you merge, Leap checks that every element can reach the elements it changes, runs or fires, and the formulas and system states it uses:
- Elements at the top level (not in any group) can be used by every element.
- Elements inside a group can be used by any element under the same top-level group, however deeply either one is nested.
- An element at the top level can't use elements that are inside a group.
A reference outside these rules stops the merge with "Reference from … is not allowed" — see Working with Workspaces. Plan your groups with this in mind: an operation that changes elements inside a group should live in the same group tree.
Scoping the Element Explorer
Select a group in the project tree, and the Element Explorer's toolbar lets you switch between that group's elements and All; + nested also includes the groups inside it. While the list is scoped to a group, New creates the element inside that group.
Next Steps
Continue to Custom Operations to define the actions in your design.