Configure experiment identifiers
The Unity window where you paste your eID, verify token, callExternal endpoint, pNum, and isTestMode. The same content lives at Setup → Connect to Web Console — see there for the full walkthrough.
These pages are not yet fully reviewed. The LUIDA team is continuing to review and improve them. If you find anything wrong on these pages, or have questions that aren't resolved by reading them, please ask or report to the LUIDA team.
LUIDA › Configure experiment identifiers opens a small editor window that holds five fields plus a few helper buttons. It's the single place in Unity where your project gets bound to a Web Console experiment.
The five fields:
expID— theeIDfrom the Web Console experiment detail page.token— the verify token; generated here, pasted into the Web Console.callExternalEndpointID— the routing key forcallExternal; usually filled in automatically via the Configure callExternal URL button.pNum— required participants per session (default1).isTestMode— checkbox flagging this session as test data.
The full walkthrough — what each field does, how to generate the token, how to register the callExternal endpoint, common errors — lives at Setup → Connect to your Web Console experiment. That page is the source of truth for this window; rather than duplicate it, this page exists mostly to remind you where to find it.
Quick reference
If you just need a reminder of where things live:
| You want to… | Go here |
|---|---|
| Generate or rotate the verify token | This window → Generate Token button. Paste the result into the Web Console's experiment detail page → Verify token field. |
| Register the callExternal endpoint with Cluster | This window → Configure callExternal URL button (auto-flow). Manual fallback via cluster.mu/account/developer. |
Set isTestMode = false before publishing | This window → uncheck the isTestMode checkbox. Easy to forget — add to a publish-day checklist. |
| Find out where the values are stored | Assets/_Experiment_/Settings/ExpIdentifiers.js (gitignored by default — contains the token). |
| Smoke-test the connection | Click Play with CSEmulator running, then check the Web Console's session list. |
Common errors
The full troubleshooting list is at Setup → Connect to Web Console → Verifying the connection. Most common:
401 / verify token mismatch— regenerate on both sides.404 / experiment not found— theeIDis wrong, or the experiment was deleted.callExternal endpoint not configured— re-register via the Cluster developer dashboard.session count limit reached— bumpmaxSessionCountin the Web Console, or exclude old test sessions.
Where to go next
- Setup → Connect to your Web Console experiment — the source-of-truth page for this window's fields.
- Web Console → Creating an experiment — where to get the
eIDto paste here. - Tutorial 0 — Hello LUIDA — uses this window as part of a 30-minute smoke test.
Configure experiment automation › State-listening Items
Tab 3 of the LUIDA automation window. The grid of items × states — where each cell binds actions to state entry, during, and exit, plus a per-item always-on event-handler section above the grid.
Configure avatars
Register VRM avatars in the project's AvatarRegistry so AssignAvatarToParticipant can spawn them at runtime by string ID.