Comments

Français · Type: how-to · Audience: author · Context: hosted Studio · Status: ready · Applies from: 4.2.3

The Studio Server (hosted team Studio) · contract: experimental · verified by CI (support matrix of 4.4.0, 2026-10-23): Postgres, S3 and Keycloak in CI; Chromium and Firefox (job studio-hosted); WebKit on macOS, by hand only · automated checks: jobs studio-hosted, studio-install-smoke; CI plan studioHosted; 3 test files · people's passes: studio-hosted not run (#149), studio-collab not run (#150), studio-preview not run (#166), studio-assets-hosted not run (#167), studio-mcp-remote not run (#196), studio-oidc-generic not run (#197) · known limits: comments-limits

On a team Studio, members comment on what the game names (a room, a door, an item, a rule, a storyboard panel) or on the game itself, in threads. Comments are kept by the Studio, never in a game file, so a reviewer comments too.

What you get

A thread anchored on a stable id of the game, with the revision it was written at, that the team answers, resolves and opens again; and the old notes.json notes brought in as comments.

Context and versions

A hosted Studio (the Studio Server), from 4.2.3. The local Studio has notes (notes.json), not comments. The code is studio-server/src/server/comments.ts.

Prerequisites

• Any role: a reviewer comments, replies and resolves their own threads; a dev or an owner resolves any thread; bringing the notes in is an owner's (see Roles and actions).

Where to run the commands

In the Studio, the Notes tab, panel Comments. Or through the API with a member's token.

Steps

1. Write a comment. In the about field, type what it is about: a room id (hall), an entity (hall.door), an item (item:key), a character (char:lou), a rule's id, an objective (objective:<id>), a checkpoint (checkpoint:<id>), or a storyboard board or panel id. Leave it empty for the game itself. Type the text (1 to 4,000 characters), then Comment.

2. Reply. Under a thread, type in Reply. A thread is one level deep: a reply to a reply joins the same thread, on its anchor.

3. Resolve, or open again. Resolve closes the whole thread; Open again reopens it.

4. Bring the notes in (owner). Bring the notes in turns each note of notes.json into a comment, once: its about becomes the anchor when it is an id, otherwise the note lands on the game's thread with its about in front of its text. Running it again brings only the new notes. It answers {imported, already}.

Through the API:

# anywhere, with a member's token
curl -H "Authorization: Bearer $TOKEN" "https://studio.example.fr/api/comments?anchor=hall.door"
curl -X POST -H "Authorization: Bearer $TOKEN" -H "content-type: application/json" \
  -d '{"anchor": "hall.door", "text": "The door should creak."}' https://studio.example.fr/api/comments
curl -X PUT -H "Authorization: Bearer $TOKEN" -H "content-type: application/json" \
  -d '{"resolved": true}' https://studio.example.fr/api/comments/<id>

Each comment has id, anchor ('' for the game), rev (the revision it was written at), parent, author, text, resolved, at, edited, and orphan.

The rules

• A comment keeps its revision. It says which version of the game it was written about.
• Orphan, never moved. A comment whose anchor the game no longer names (a room removed, an id renamed) is shown "orphan: the game no longer names it"; it is never attached elsewhere. The anchors are the game's rooms, rules, scripts, entities, objectives and checkpoints, and the storyboard's boards and panels. A line's id is not an anchor. While the game does not load, no comment is said orphan.
• Its author alone changes its text. The Studio's panel has no edit button: the text is changed through PUT /api/comments/<id> with text.
• A reviewer resolves their own threads; a dev or an owner, any thread.
• Kept by the Studio: in its database and in its backups, never in a game file; no game file is written, so a comment needs no span and is never refused with a 423.

Guarantee · comment-author-edits · referenced · executed on aff6caab7514 · scope self-checked by the author (AI), not reviewed Only its author changes a comment's text; a thread is resolved as a whole; a reviewer resolves their own threads only.

Limit · comments-limits A comment cannot be deleted (there is no route). One member keeps 2,000 open comments at most (429 past it: resolve some first). The list gives the 2,000 newest. Comments are not in the game's Git repository nor in an export: they live in the Studio's database.

Expected result, and how to check it

The thread appears in everyone's Comments panel, under its anchor, with its revision. GET /api/comments?anchor=<id> lists it.

Common errors

Files or data changed

Rows of the studio_comments table. No game file, no revision.

Recovery or going back

A thread resolved by mistake is opened again. A text is corrected by its author. Nothing else can be undone.

References

• Roles and actions.
• The local Studio's notes.
• tests/studio-comments.test.ts.

Edit the source of this page · Report an error