Skip to content

Player themes

The standalone HTML player can look like the game you are writing, not like a test log. Pick a theme, and the exported file shows your story with the location as a backdrop, a portrait for whoever is speaking, and the line in a dialogue box. It is still one self-contained .html file you can send to a producer, a publisher or a playtester.

Open Export → ▶ Player look & preview (or ⚙ Look settings in Play mode). The preview on the right is the exported file itself, running, so what you see there is exactly what the download contains. Settings save with the project and apply to the HTML player, SCORM and xAPI exports.

▶ Play has a Look picker in its top bar: the Editor player or any theme and style. A theme look runs the exported player itself, so a playtest is a test of exactly what you ship, and picking one also sets how the project exports. Press S (or Shift+S) to cycle through the looks without losing your place: the run is rebuilt at your last choice. Esc leaves.

The Editor player is still there for what themes do not do yet: audio and video per line, Somebody avatars and their live conversations (those projects always play in it), and Lua beyond what the exported player runs (a Lua notes badge says when a story uses some). Shared play links open in the project’s look.

ThemeWhat it looks likeGood for
Dialogue boxFull-screen backdrop, the speaker’s portrait, a name plate and a text box that types the line out. Choices stack above the box. A Log button opens everything said so far.RPGs, adventures, visual-novel-style scenes.
ChatPhone-style message bubbles with round avatars, a typing indicator before each reply, and choices as quick-reply buttons.Messaging games, texting stories, mobile.
ClassicThe running transcript with the variables beside it, now over the location backdrop when there is one.Review, training, SCORM.

The Dialogue box comes in four styles, each staged the way a family of games does it, so a playtester recognises the genre at a glance:

StyleStaging
Cinematic (default)The line as a subtitle in the lower third, the speaker standing in the scene, a plain numbered choice list. Modern narrative games.
CRPGA serif text column beside the scene that keeps the whole exchange; locked options read [Locked] … — reason. Story-heavy role-playing games.
JRPG / visual novelLarge character art, a solid text window with a name tab, and a separate choice menu with a cursor.
RetroA hard-edged box, monospace type, a small portrait in the box and a ▶ cursor. Classic 8- and 16-bit games.

Characters look best as cutouts — a transparent background — so they stand in the scene. ChatMapper’s picture generation can make them that way.

Every style fits the screen it plays on. On a phone held upright, a tablet or a square screen, the speaker stands centred above the words instead of beside them and the text scales up to suit the screen. The CRPG column moves below the scene. On a phone turned sideways, everything tightens and long choice lists scroll. Chat fills a phone-shaped screen edge to edge.

New projects start with Dialogue box in the Cinematic style. Projects linked to LearnBrite or Somebody start with Classic, because those platforms present the story in their own player. Projects from before themes keep Classic until you change it.

The themes use the pictures you have already set:

  • Backdrop: the first picture of the node’s Location, or the conversation’s. When a spot has no picture, the last one stays up.
  • Portrait: the first picture of the speaking actor. An actor without one gets their initials on a colour, the same as in the editor.
  • [pica=N] in a line switches to the actor’s Nth picture — the usual way to show a different expression. [picc=N] shows the conversant’s Nth picture instead. [pic=N] shows the node’s own Nth picture, such as a close-up of a map or a letter. N starts at 1; see Inline markup.
  • The swap happens where the tag sits in the line, so with the typewriter on the face changes mid-sentence. It lasts for the rest of that node.

Only the pictures the theme shows go into the file, scaled down for the screen. Pictures that are not uploaded yet, and tags that point past the end of a picture list, are listed in the export notes.

By default a choice whose condition is false is hidden, as in ChatMapper Desktop and the engines. A game often wants to show it instead, greyed out with the reason: 🔒 Offer gold — You have 5 silver to your name.

Locked choicesShows
HiddenNothing (the default).
Marked onlyOnly choices whose node has Locked Text. You decide which locks the player sees.
AllEvery locked choice.

The reason is the node’s Locked Text field. Turning locked choices on adds that field to every node it could apply to. When it is empty, the reason is worked out from the condition — Variable["Trust"] >= 3 reads as Requires Trust ≥ 3, and a visit check as Requires having seen ”…” — or, when the condition is too involved to say plainly, Not available yet.

Play mode shows locked choices the same way, so playtesting matches the export.

  • Typewriter speed — characters per second, or off. Viewers who have asked their system for reduced motion get whole lines at once.
  • Accent colour — name plates, choice numbers and highlights. Each style has its own until you pick one.
  • Title card — the story’s title and a Play button before it starts.
  • Debug button — shows the variables, for playtesters who want to see the state.
  • “Made with ChatMapper” link — Creator and Team plans can remove it.

Players can click or tap the box, or press Space or Enter, to finish a line or move on, and 1–9 to pick a choice.

Exports that play Somebody avatars use Classic: the avatar layer needs it. The export notes say so if another theme was chosen.