Reference
Actions, Web Console API, signals, state keys, and the variables your scripts can read.
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.
Bookmark these. Lookups, not narratives — the reference section is where you go when you know what you need but forgot the exact name or shape.
Actions
Every predefined state-listening action: ShowItem, SetPosition, SendHaptics, AssignAvatarToParticipant, etc. 25 cards.
Web Console API
Every type accepted by POST /api/cluster — questList, questions, uploadCustomData, checkJoinEligibility, and the rest.
Signals & state keys
The inter-object protocol: state_currentID, exp_recordCustomData, luida_avatar_cmd, and friends.
Variables in scripts
What's in scope inside Customized Action and Data Collector scripts: CONDITION, PARTICIPANTS, COLLECTED_DATA.
How to read this section
- Action pages are one-per-action MDX cards with a fixed schema: signature, fires, requires, description, parameters, side effects, example, related.
- API pages group every dispatch type under one heading per type. Each shows request shape, response shape, error cases.
- Signals & state keys is one big table you'll skim with Cmd-F.
- Variables is the shortest page — three globals, with their fields enumerated.
Cross-cutting reference (links)
Beyond what's documented here, you may need the underlying CCK / ClusterScript reference:
- Cluster Creator Kit official docs — when LUIDA is silent on a CCK primitive.
Assets/Doc/CCK-Types.d.ts— the full ClusterScript API as TypeScript declarations. Most useful when you're writing aCustomized Actionand need to know "is there a$.method()for X?"Assets/Doc/LUIDA-StateListeningItemScriptDoc.md— the source-of-truth markdown the Action cards on this site are extracted from. Useful as a flat doc when this site isn't reachable.