Moderator Workspace

The moderator workspace combines game design, classroom execution, and post-run analysis.

Workspace Tabs

• Design creates, opens, edits, validates, and manages definitions.
• Execution organizes rooms, starts games, and monitors sessions.
• Run Logs reviews live and completed runs.

Unsaved Design changes are protected when you change game or workspace. Save deliberately; validation failures that require attention are shown as dialogs and in Validation.

Interface Language

Use the Language selector to switch the principal account, player, Design, execution, and Run Logs controls between English and Slovenian. The choice is stored in that browser and is reused on the next visit. It changes application labels and messages only: authored game text, participant input, technical identifiers, diagnostics, and downloaded files remain unchanged. Design dialogs follow the same interface language, including Page and Formula editors and their Pattern offers. Formula names, function names such as Uniform, references, and formula source text remain language-independent so changing the interface language cannot change game behavior.

Navigation and palettes

The main sections are in the left menu, together with the username and Logout. The menu adapts to screen width and can collapse to icons; its collapsed preference is saved. Editor/AI Design and the editor tabs remain inside the selected section.

Colour swatches beside the language controls select blue, green, terracotta, brown or plum. The palette choice is stored in this browser. Starting a game captures the moderator palette for that run and its players; later moderator palette changes do not recolour an already-open run.

Basic Flow

1. Prepare and save a definition in Design.
2. Open Execution and add it to a room or game set.
3. Start the game and share that room's link.
4. Monitor Game sessions and, when useful, Moderator view.
5. Stop the open game when it should accept no more players.
6. Review the run in Run Logs.

Rooms

A room is a player entry space owned by the moderator. The default room is main and cannot be removed. Create other rooms to separate classes, workshop groups, or tests from live use.

Rooms and Game sessions occupy separate scrollable columns. Use the + beside Rooms to open a name dialog and create a room. Each room has its own Add game set (+) action, and each game set can be renamed. The protected main room cannot be renamed or deleted. A room can also be renamed from its row. The display name preserves your spelling, capitalization and accents. Renaming changes only that name: the internal room identifier, player link, shortcuts, game sets and assigned games stay unchanged. Existing rooms keep their previous names until you rename them. Workspace backups retain display names; merging preserves names of rooms already present in the destination. A room may contain games directly or organize them into game sets. Add games can choose from the complete catalog, including predefined games under Demo.

Each game row provides direct controls:

• move up and move down in one vertically split control before the game name,
• participant count when the definition permits adjustment,
• start or stop,
• open test client,
• change game set,
• remove from room.

Change game set can move a game to a room root or game set in any room. Removing a game from a room does not delete its catalog definition.

Starting And Stopping

Starting validates the saved definition and opens it for joins in the selected room. Errors block execution. The same catalog game cannot be started again while its current run is active.

Fixed-player games wait until the required number of players has joined. An adjustable participant field may be left open where the definition permits an open session size.

Stop closes the run to new players and follows the normal completion path, including final calculations and configured Results. Use it after groups have finished, or to conclude an ongoing game such as an unlimited Market. If you stop during unfinished play, calculations depending on missing decisions may be undefined; Stop does not guarantee complete results. It preserves history and does not start another round.

Room Links And Shortcuts

Copy the full room link when players should join. A room can also reserve one unique, account-owned shortcut such as /r/classroom. Expand the room and edit the shortcut text in the sharing toolbar above its games and click Add/Update shortcut to save it; an edited value is not saved until that action is used. The saved value uses the palette accent; unsaved edits use the ordinary text colour. Copy shortcut copies the saved shortcut, and Release shortcut frees it.

Shortcut names use lowercase letters, numbers, and hyphens, start and end with a letter or number, and cannot use reserved application paths. Generate secret shortcut text inserts a secret sequence into the shortcut field; use Add/Update shortcut to save it. The Secret tag belongs to the shortcut. Adding characters while preserving the generated sequence keeps the tag; removing or reordering any part of that sequence clears it. Copying or releasing a shortcut does not change the canonical room link.

Game sessions

The compact Game sessions list shows game, status, room, players, opening time, session ID, and event count. A filter appears when the list contains at least five sessions.

Unfinished sessions are shown first, ordered by ascending event count so the least-progressed session is easiest to notice. Completed sessions follow in newest-first order. The event count appears in parentheses beside the session ID; it is the ordering signal, not a participant-facing result.

Available icon actions depend on state:

• open the read-only Moderator view,
• Stop session without Results, an exceptional interruption after confirmation that skips final calculations and Results,
• download its JSONL event log.

Moderator View

Moderator view is hidden until a session is selected and then opens full width below the two main Execution columns. Close it with the X control.

The view is read-only. It presents the current public tree or matrix state, the moderator Stage, or another available session snapshot. A game without a dedicated moderator view still remains observable through its session status and Run Log.

Session States

Typical states include waiting, running, completed, finalized, stopped, and abandoned after a server restart. A run or session marked abandoned is no longer live even if it had previously been open.

Catalog Management

In Design, the Definitions toolbar creates, opens and uploads games and manages catalog folders. Commands beside the selected game save, download, add it to rooms, rename, move or delete it. Folder pickers show complete paths so equally named subfolders remain distinguishable.

Account-owned definitions can be authored and managed. The Demo tree is read-only in Design but remains selectable from Rooms.

Workspace Backup

The collapsed Workspace backup panel downloads the signed-in account's portable Design and room configuration or previews a Merge/Overwrite restore. Run Logs and credentials are excluded. See Workspace Backup And Restore before using Overwrite or moving a workspace to another account.

Stuck Games

The collapsed Stuck games section is for exceptions, not routine class work. Reset all live games abandons every open run and session owned by your account and disconnects its players. Use it only when those games are stuck; it does not restore them. Rooms, definitions, settings, and finalized Run Logs are preserved.

Before Class

1. Save and validate the intended game.
2. Add it to a test room and start it.
3. Open enough test clients for one representative path.
4. Confirm the session appears and its status advances.
5. Review the Moderator view and resulting Run Log.
6. Stop the test game.
7. Start the live room game and share its room link.

After Class

1. Confirm the intended sessions have reached Results. Use Stop session without Results only for an exceptional interruption; it skips final calculations.
2. Stop games that should no longer accept joins.
3. Review and export the run from Run Logs.
4. Keep definitions in the catalog when they will be reused; removing them from Rooms is sufficient to declutter execution.

For exact Room controls, session ordering, fields, actions, and status interpretation, see Rooms And Sessions Reference.

Settings and problem reports

Open Settings at the bottom of the left menu. AI conversation review is off by default and is saved with your moderator account, independently of the browser and game packages.

If enabled, the server administrator can review a diagnostic sample of new AI Design and AI Analysis messages, including new replies in existing conversations. Earlier history and complete AI input documents are not automatically shared. Messages themselves can contain game definitions or Run data. Disabling closes review access to the collected sample; enabling again starts a new sample. It cannot undo a review already performed. Your own AI history and normal AI functions remain available.

Report a problem works without this permission. Describe what happened and review the included application version, workspace section, and game or Run identifier. You may attach a PNG/JPEG screenshot or TXT file (up to 500 KB). When an AI conversation is open, a separate unchecked option lets you preview and attach that conversation to this particular report. This explicit attachment remains part of the report even if general review permission is disabled.

After submission, a confirmation dialog shows the report reference. Reports are stored in the application for the server administrator; no email is sent. If submission fails, the dialog retains your input for retry. The administrator opens Settings → Administrator inbox to read reports or currently permitted AI messages.