Repository navigation
EN Studio Voices Matrix
Français · How-to · Published, reviewed by a person · Applies from: 4.4.0
The Voices tab holds the voice recording table, per language, and its second view, Heroes × languages: every line that depends on the hero, the text each hero reads in each language and the clip that plays, with what is missing.
Audience, context, and the statuses of what this page rests on
Audience: author · Context: local Studio
The local Studio · contract: stable · verified by CI (support matrix of 4.4.0, 2026-10-23): Chromium end to end (the Studio's checks); Windows: the unit suite only · automated checks: jobs
e2e,windows; CI plane2e,windows; 2 test files · people's passes:studio-hero-matrixnot run (#238) · known limits:table-dev-server,matrix-boundsVoices and music · contract: stable · verified by CI (support matrix of 4.4.0, 2026-10-23): The music director in Chromium and WebKit · automated checks: jobs
e2e; CI plane2e; 2 test files · people's passes:voices-listeningnot run (#87) · known limits:table-dev-server,matrix-bounds
A recording table the actors can work from (CSV out, CSV back in), and a matrix that shows at a glance which hero lacks a translation, a clip, or a choice the source language makes.
The local Studio, engine repository or created project. The matrix is from 4.4.0, read-only, and works on every backend: the dev server, a hosted Studio and the demo Studio. The recording table needs the dev server. How voices and hero choice are written in the game: Voices: per language and per hero, Heroes: several characters and hero choice.
- The Studio running (overview).
- Lines with stable ids (Voices); the matrix lists only lines with an id that depend on the hero.
In the browser, on the Voices tab. npm run voices runs in the engine repository.
- Open the Voices tab, view Recording table, and pick the Language. Each line with a stable id is a row: who
says it, its text in that language, its clip, and its status (draft, record, recorded, approved), with the actor
and a note. A change is saved at once, into
games/<id>/voices.json, and is undoable. "Find a line…" filters the rows; Status filters by status.
-
Export CSV hands the table to the actors. Bring theirs back from the command line:
# in the engine repository npm run voices -- import <file>
Limit ·
table-dev-serverThe recording table needs the dev server (npm run studio): elsewhere the tab says "The voice table needs the dev server (npm run studio)." The matrix still works there.
- Switch the view to Heroes × languages. A row per line with an id that depends on the hero (a text switch or
{hero}, in any language). A column per hero, that is per combination of the values the switched flags take, headed by the variant's portrait and name, and per language. Each cell: the text that hero reads and the clip that plays, or the clip that is missing (the plain id is named when it plays instead).
-
Show "lines with a problem" keeps the rows that flag one:
- untranslated: a language has no text for the line;
- agreement: a translation drops a choice the source makes (a switch the source has, the translation lacks);
-
unlisted: a value of a flag that no switch lists, without a
*=default; - a clip that is missing for a hero.
Language narrows to one language; "Find a line…" searches. The bar counts the lines, those with a problem, the heroes and the languages.
Limit ·
matrix-boundsThe matrix shows 24 hero combinations at most; the bar says how many more were left out. The table shows 200 rows at most: "N more: narrow the search."
With "lines with a problem", an empty matrix: every hero has every line in every language, and a clip where one is
expected. npm run voices -- check agrees on the command line.
| Symptom | Cause | Fix |
|---|---|---|
| "The hero matrix is not available on this backend." | A backend without the route | Use the dev server, a hosted Studio or a recent demo |
| A cell names a plain id | The hero's clip is missing; the plain line's clip plays instead | Record the clip for that hero |
A row is flagged agreement
|
The translation lost a switch | Put the switch back in the translation |
games/<id>/voices.json (the recording table). The matrix writes nothing.
A status, actor or note change is undoable from the header during the session; otherwise git.
-
src/studio/voices.ts,src/studio/hero-matrix.ts,src/engine/tools/hero-matrix.ts,tools/voices.ts. - The routes
GET voices[/:lang],PUT voices/:lang/:id,GET voices/:lang/csvandGET hero-matrix({ langs, flags, columns, rows, truncated? }): Studio API.
Generated publication · publication générée — current documentation · documentation courante: quest'n'click 4.5.4 r2, documentation revision · révision de la documentation 63112c877c587cc4fad16b25a3400408db2c36bd.
Latest documentation · dernière documentation: https://quest-n-click.cleverapps.io/docs · https://quest-n-click.cleverapps.io/fr/docs; earlier versions · versions précédentes: each release's quest-n-click-docs-<version>.tar.gz · l'archive quest-n-click-docs-<version>.tar.gz de chaque release, https://github.com/Quest-n-Click/quest-n-click/releases
An edit made in this wiki is overwritten at the next publication · une modification faite dans ce wiki est écrasée à la publication suivante.
Edit the source · Modifier la source · Report an error · Signaler une erreur
Index (6)
Start (6)
Play (9)
Install (18)
- Requirements
- Install from the release archive
- Install from npm
- Install from the repository to work on the engine
- doctor: checking your machine
- Image toolchain
- Audio toolchain: ffmpeg, fluidsynth, Furnace, uv
- Upgrade
- Upgrade notes: 4.5
- Upgrade notes: 4.4
- Upgrade notes: 4.3
- Upgrade notes: 4.2
- Upgrade notes: 4.1
- Upgrade notes: v3
- Upgrade notes: v2 to v3
- Coming from web-scumm
- Package reference
- Install troubleshooting
Create a game (55)
- Your first game
- Layout of a created project and of the engine repository
- The working loop
- Content principles and the identity contract
- Rooms
- Geometry: placement, walk zones, masks, layers, camera
- Something is visible but unreachable
- Reactions
- Game commands
- Conditions
- Flags, variables and events: which to use
- Custom code
- Characters
- Items and inventory
- World map
- Dialogues
- Scripts and events
- Moving characters: patrols and walks
- Exits
- Chapters and objectives
- State and saves: persistent or temporary, renaming an id, migrations
- Staging: wide rooms and animations
- The stage: lights, particles, floors
- Skin and fonts
- Title and credits
- Heroes: several characters and hero choice
- Built-in minigames
- A custom minigame
- Translations
- Music in stems
- Sound effects
- Voices: per language and per hero
- Images: prompts, cutting sheets, transparency, scale
- Asset provenance
- The storyboard, source of truth
- Puzzle design
- Classic mechanics
- Review pages
- DSL reference
- Checking your game
- What the solver proves
- Solver options
- Playtests
- Remix
- Speedrun for authors
- The sealed ending
- Production template
- Example games
- Working with an AI
- Build and release a game
- Publish on GitHub Pages
- The static game on Clever Cloud
- Other static hosts
- Sub-path, cache and service worker, incomplete deploys, going back
- Testing on a phone over the LAN
Local Studio (24)
- The local Studio: overview and launch
- Edit a room
- Placement and stage
- Preview, apply, undo
- Storyboard
- Assets and cutting
- Check: validator, solver, critical path, heat, health, coverage
- Before and after captures
- Semantic diff
- Play and replay a session
- Rule explainer
- Language and objectives
- Voices and the heroes × languages matrix
- Map
- Notes
- Remix in the Studio
- Music
- The Assistant: bring your own key
- Demo mode and studio-apply
- Local and LAN security
- Studio API
- Local MCP: setting up each client
- MCP tools
- Studio troubleshooting
Team Studio (21)
- What runs where
- Concepts: revision, transaction, span, lease, preview, build
- Starting as an invited dev
- Working together day to day
- Roles and actions: the full matrix
- Invitations
- Managing members
- Write refused on the hosted Studio: stale base revision (409)
- Write refused on the hosted Studio: span locked (423)
- Recovering after a lost lease, a disconnection or a stale preview
- Comments
- Map and semantic diff
- Publishing builds
- Remote MCP
- The game in Git
- Upgrading the engine of a hosted game
- Hosted assets
- The server's command line
- Health and metrics routes
- Trying it locally with compose.yml
- Known limits
Clever Cloud (23)
- Clever Cloud: overview, cost and prerequisites
- Apps and add-ons
- Domains and TLS
- Keycloak
- Generic OIDC and GitLab
- Configuration
- First deployment
- Backups
- RPO and RTO
- Restore the Studio on a fresh installation
- Redeploys
- Upgrading the server and checking state after a migration
- Limits of going back
- Monitoring
- Security
- Rotating keys
- Recovering admin access
- Changing domain or OIDC provider
- Worker, PostgreSQL or Cellar down
- Exporting the game and leaving the installation
- Retention
- Clever Cloud troubleshooting
- Costs and teardown
Reality Bridge and connectors (16)
- The Reality Bridge: what it is
- Quick start
- Guarantees
- Install and run the Bridge
- Backup and restore
- Several tenants
- Signals and the manifest
- The Bridge's command line
- Connectors overview
- Email connector
- Telnet connector
- SSH connector
- Open Badges connector
- The connector SDK
- Security: Biscuit and signatures
- Bridge and connector troubleshooting
Contribute (25)
- Welcome
- Developer setup
- The dev loop
- Before a pull request
- Conventions
- Writing documentation
- Architecture
- Code tour
- Import boundaries
- Which tests run when
- Mutation testing
- The coverage ratchet
- The quality baseline
- CI explained
- Field passes
- Benchmarks
- Releasing
- npm packages
- Decisions and ADRs
- Governance
- Bot pull requests
- Contributing with AI agents
- Security policy
- Code of conduct
- Licences and credits