Scene info

Scene info is the on-screen briefing every player can open, holding where they are, why they are there and what they are meant to do.

/sceneinfo shares its permission with /scene, so it 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

The briefing has 3 headings, 3 lines of context and 5 objectives. You set each field with its own command, and every change pushes to all connected players at once. Objectives carry a state you can move as the scene goes, so players see progress without you announcing it.

Setting the headings

3 fields sit at the top of the briefing. name is the scene title, location is where in the world it happens, and planet is the wider setting.

location and planet work the same way:

Pass none instead of text to empty a field:

Writing the briefing lines

3 lines, brief1 to brief3, sit under the headings. Use them for the situation, not the tasks.

Setting objectives

5 slots, obj1 to obj5. Each one starts pending the moment you write it.

Rewriting an objective resets it to pending, because new text means a new task. Clearing one with none also clears its state.

Marking objectives off

An objective is pending, complete or failed. 3 commands set a state outright, and a fourth walks through all 3 in order.

cycle advances one step each time you run it, pending to complete to failed and back round. It is what the panel's per-objective button sends, so it suits a key bind.

All 4 commands also accept the older obj1 to obj5 spelling, so /sceneinfo complete obj1 still works. An empty slot is refused:

Reading and clearing

Run /sceneinfo on its own for the command list, followed by everything currently set. These are the current-value lines of its longer listing:

There is also a setall form that writes all 11 fields in one command. It exists because the scene info panel cannot send commands back to back, so use the panel rather than typing it.

Things to note

• Every field caps at 48 characters. That is one row of the panel. Longer text is refused rather than trimmed, with "Text too long (max 48 chars)".
• There are exactly 5 objectives and 3 briefing lines. Neither number is configurable.
• Scene info survives a map change. It is only reset by /prepmap, a scene load or /sceneinfo clear.
• Rewriting an objective resets its state. Fix a typo after marking it complete and it goes back to pending.
• cycle never stops at failed. Run it a third time and the objective is pending again.
• A scene save stores the briefing. Loading that scene restores it and overwrites whatever was on screen.

Next

• Scenes: save the briefing with the set it belongs to
• Transitions: put a one-off announcement on screen instead