Game Engines
RLX Unity API
Unity bridge for LifeRaft OS account linking, entitlement checks, event telemetry, community links, support handoff, and studio-ready C# connector packaging.
What it does
Features at a glance
- Gives Unity teams a studio-ready community, support, and product site around the project
- Creates a path for event telemetry, entitlement checks, support handoff, and update awareness
- Keeps public messaging focused on buyer value while licensed packages provide setup specifics
Built for your workflow
Who it’s for
- Studios connecting supported external experiences with an owned web platform
- Game and world teams bringing community, identity, and support into one project
Setup and fit
Compatibility
Requires a valid LifeRaft OS core license and a supported installation.
No additional add-on is listed as a required dependency.
Optional connections
From setup to everyday use
A straightforward starting point
- Activate RLX Unity API and review its add-on settings
- Gives Unity teams a studio-ready community, support, and product site around the project
- Creates a path for event telemetry, entitlement checks, support handoff, and update awareness
Before you choose
Common questions
What does RLX Unity API do?
Unity bridge for LifeRaft OS account linking, entitlement checks, event telemetry, community links, support handoff, and studio-ready C# connector packaging.
What does RLX Unity API need to run?
RLX Unity API runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.
How ready is RLX Unity API for deployment?
Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.
Review the launch checklist
- Admin setup — Confirm settings, navigation placement, permissions, and any required starter content before launch.
- Public QA — Review the public page, empty states, mobile layout, and activated/deactivated states.
- Package QA — Confirm the module fits the selected product package and does not expose unused workflows.
- Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.
Make RLX Unity API part of your build.
Discuss the fit, requirements, and next steps for your project.