Scenes

A scene is a single file holding everything you placed on a map, so you can rebuild the set in one command.

/scene is hard-locked to director mode by default. Even a leadership admin is refused unless they have taken the director's chair.

What it does

A save records everything you put on the map:

• placed entities, rank locks and spawn points
• NPCs and their routes
• shader remaps
• camera waypoints and camera boxes
• telemarks and points of interest
• the music track, the crawl text and the scene info

Loading that file wipes whatever is live and rebuilds from the file. Scenes belong to your account and to the map you saved them on.

Saving a scene

Names are 1 to 32 characters and accept letters, numbers and underscores only. No spaces, no hyphens, no full stops. A name that breaks the rule is refused:

The file lands in scenes/ and is named <username>-<map>-<name>.cfg. Slashes are stripped from the map name and it is lower cased, so dara saving throneroom on mp/ffa3 writes scenes/dara-mpffa3-throneroom.cfg. Saving over a name you already used overwrites it and the reply adds "(overwrote existing)".

Saving a bare map records nothing worth loading, and the game tells you:

Loading a scene

/scene load wipes the live world with no confirmation prompt. Every placed entity, NPC, route, remap, camera track, telemark and POI goes. The music stops and the crawl text and briefing are wiped, then the file's contents are rebuilt. Save your current set before you load another one.

The bare name form only finds your own scenes for the current map. Anything ending in .cfg is treated as a full filename and loads that file from scenes/ verbatim, whoever saved it:

Loading a scene saved on a different map warns you but goes ahead:

The whole file is parsed before anything is wiped, so a corrupt file leaves your set alone:

Listing your scenes

A bare /scene list shows only your scenes for the current map. Add all to see every scene file on the server, from every account and every map. A bare number in the second position is the page number. So /scene list 2 is page 2 of your own, and /scene list all 2 is page 2 of everything.

Deleting a scene

You can only delete scenes saved under your own account:

Setting a map default

A map default is a copy of one of your scenes that the server loads on its own, the first time someone connects after the map starts. Both commands need leadership.

Anything below leadership is refused, whatever its story tools permissions say:

Things to note

• /scene load has no confirmation prompt. It is the fastest way to lose an hour of set dressing.
• The default is a copy, not a link. Changing the source scene later does not change the default. Run /scene setdefault again.
• Clearing a default leaves a zero-byte file. The auto-load only arms on a file longer than zero bytes, so a cleared default stays cleared.
• Deleting leaves a zero-byte tombstone, not a gap. The file is truncated rather than removed, so it vanishes from /scene list and cannot be loaded, but the filename stays taken. Saving the same name again writes over the tombstone and reports "(overwrote existing)".
• Only one load runs at a time. A save, a delete or a default change during one is refused with "A scene load is in progress - try again shortly", and a second load with "A scene load is already in progress".
• Removed map items and map spawn points do not come back on load. They only return on a map restart, and loading a scene that never removed them warns you rather than restoring them.
• A scene that is over the file limits saves short. The reply warns how many entities, locks or NPCs were dropped.
• Scenes are not portable between accounts by name. Use the full .cfg filename to load someone else's.

Next

• Scene info: write the briefing a save carries with the set
• Prepmap: clear a stock map before you build the set you save