Projects and places
Project layouts, place selection, application settings, and saved content.
A Studio project stores the instances, scripts, and assets used to author a game. A place is one instance hierarchy. A game project groups multiple places and selects a start place.
Project layouts
Studio opens the following directory layouts:
| Layout | Files | Behavior |
|---|---|---|
| Studio world | asterune.project.json and the world file named by its world field | Stores the authored hierarchy in a binary .astx file. New projects use world.astx. |
| Place source project | src/, with an optional asterune.place.json | Builds the hierarchy from source files organized by service. |
| Game project | asterune.game.json, places/, and optional shared/ | Combines the selected place's source with content shared across the game. |
Open and select places
On the Studio home page, select Open Project… and choose the project folder. Studio opens a game project's start place. In a game workspace, use Home → Places to select another place. Home → New Place adds a place; Home → Set start place makes the open place the game's start place.
If the project cannot be opened, read the displayed error and check that the folder contains one of the supported layouts above. An error reading a manifest or source file requires correcting that file before opening the project again.
Source directories
The first level of src/ names services such as Workspace,
ServerScriptService, and ReplicatedStorage. A directory that names an unknown
service produces a project layout error. Game place sources live under
places/<key>/src/; the game's shared/ directory uses the same service layout
and is merged before the place's own sources.
Use Home → Save to persist editor changes. Source projects write changes to their source layout; world projects write their world file. A playtest runs a separate snapshot of the open content. See Playtesting.
Application settings
asterune.app.json at the project root stores the exported application's
identity and local persistence options. These settings also appear in
Settings → App & export. Change Display name, Version, Author,
Application ID, and Icon in that page. Enable Player profile and
Local saves for a local game that needs a persistent identity and saves.
| Control and field | Type | Omitted behavior |
|---|---|---|
Application ID (id) | String | Export derives an application ID from the game name. The ID identifies the game's settings and save namespace. |
Display name (displayName) | String | Uses the game name. |
Version (version) | String | Uses 1.0.0. |
Author (vendor) | String | No vendor override. |
Icon (icon) | String | No project icon override. |
Player profile (localProfile) | Boolean | false; the local player uses the name Player and UserId 0. |
Local saves (localStorage) | Boolean | false; local file storage is not installed as a data-store provider. |
VR support (vr) | String | off; valid values are off, supported, and required. |
For a local game that needs a persistent player profile and saves, set
localProfile and localStorage to true. The runtime keeps that data in the
game's application settings directory. Without a storage provider,
StorageService requests report that storage is unavailable.