Module Development¶
XRXP modules are standard Unity packages with runtime, editor, documentation, and test surfaces.
Typical package layout¶
Development rules of thumb¶
- keep runtime and editor code in separate assemblies
- put setup commands under
XRXP/Modules/ - document install, setup, emitted data, and troubleshooting
- update changelog and module docs with user-facing changes
Suggested module checklist¶
- define the experiment problem the module solves
- keep the package optional and dependent on
com.xrxp.core - provide one-click setup from the Unity menu
- emit data that fits XRXP's existing recording model
- add tests where practical
When to create a module¶
Create a separate module when the feature:
- is optional for most users
- brings extra dependencies or hardware requirements
- has its own setup and documentation burden