ChatMapper for LearnBrite authors

This manual is for people who write branching conversations that play inside a LearnBrite space — the bots you talk to in a 3D scene, the tasks they set, the choices a learner makes, and the consequences that follow.

It has two sections. Read the one that describes you.

1. Start here — new to ChatMapper

Start here — new to ChatMapper

Read this if you have never used ChatMapper before, or if you have only ever edited scenarios in the LearnBrite Dashboard’s own editor. It starts from signing in and ends with a published scenario running in your space, explaining the vocabulary (conversation, node, actor, variable) as it goes.

2. Migrating from ChatMapper Desktop

Migrating from ChatMapper Desktop

Read this if you already author scenarios in the Windows ChatMapper Desktop app and are moving that work to the web. It assumes you know what a dialogue tree, a group node and a Lua condition are, and concentrates on what moved, what is new, and the handful of things that are still Desktop-only.

What both sections assume

• You have a ChatMapper Cloud account at app.chatmapper.com, or can create one.
• You have (or can get) access to a LearnBrite Dashboard account, because that is where scenarios are deployed and where your bots, hotspots and tasks live.

If you only need conversation data for a game engine and no LearnBrite space is involved, read the game developers manual instead.

A note on formats

ChatMapper Cloud never invents its own file format. Everything it saves is canonical ChatMapper JSON, the same format the Desktop app and the LearnBrite runtime read. Web-only extras (canvas positions, reviewer notes, layout preferences) live under an _editor key that is stripped from every export, and LearnBrite runtime settings live in ordinary custom fields that older tools simply ignore. Nothing you do in the web editor can produce a file the rest of the toolchain cannot open.