Game Engines add-on
RLX Unity API
Unity bridge for LifeRaft OS account linking, entitlement checks, event telemetry, community links, support handoff, and studio-ready C# connector packaging.
Game EnginesCategory
1.0.0Version
ProductionRelease stage
$64.85 · AdvancedLicense
Game Engines add-on
About this add-on
RLX Unity API for LifeRaft OS
`unity-package/RLXUnityCompanions.cs` adds reusable C# intent objects for analytics, achievements, and support handoff. Production networking, signing, retry, and secret storage remain in the licensed trusted-client/server package.
Unity bridge for LifeRaft OS account linking, entitlement checks, event telemetry, community links, support handoff, and studio-ready C# connector packaging. Use it when a studio needs LifeRaft OS identity, entitlements, signed event flows, community systems, support, and analytics connected to the external clients they already build in.
At a glance
- Studio-owned Unity account links and entitlement checks
- Signed event telemetry for analytics and progression workflows
- Self-hosted community and player operations portal
- Lets studios connect community identity, entitlement, signed event, and support workflows to external game clients
rlx-unity-api
Version 1.0.0 $64.85 · Advanced
Production
Capabilities and outcomes
How RLX Unity API improves the build
The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.
Structured private entitlements for a clearer day-to-day workflow
Structured signed events for a clearer day-to-day workflow
Structured player analytics for a clearer day-to-day workflow
Structured achievements for a clearer day-to-day workflow
Structured updates and support for a clearer day-to-day workflow
Add-on-specific scope
Connect Unity player activity to a studio-owned web platform.
RLX Unity API gives Unity teams a self-hosted account, entitlement, telemetry, support, and community layer. Signed client events can feed owned analytics and progression workflows while player-facing achievements, updates, downloads, and support stay attached to one durable identity.
Unity account linkingPrivate entitlementsSigned eventsPlayer analyticsAchievementsUpdates and support
Standalone value
What it does by itself
RLX Unity API can run as its own Game Engines workflow. By itself, it focuses on Studio-owned Unity account links and entitlement checks, Signed event telemetry for analytics and progression workflows, and Self-hosted community and player operations portal, so a customer can use the module without buying every related add-on first.
Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
Connected value
What improves when related add-ons are active
When the customer also owns and activates related modules such as RLX License Manager, RLX Analytics, RLX Support, RLX Updates, and RLX Achievements, RLX Unity API can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Best fit
Who should care about it
- Studios that need game-client identity, entitlement, event, or support handoff without building a private backend from scratch
- Game & Engine Integrations builds that need RLX Unity API without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Unity API and review its add-on settings
- Configure the module settings and permissions
- Add the records, content, media, or rules this module manages
- Review public pages and backend empty states before launch
Works well with
The strongest builds connect the right modules
RLX Unity API becomes more valuable when it is paired with the workflows around it. Common pairings include RLX License Manager, RLX Analytics, RLX Support, RLX Updates, RLX Achievements, depending on the customer package and what the site needs to accomplish.
Platform notice
Independent integration positioning
RealysticTM, LifeRaft OSTM, and RLX Unity API are independent products and are not endorsed by, sponsored by, affiliated with, or partnered with Unity. Any customer using this add-on is responsible for reviewing and following the applicable platform terms, marketplace rules, branding rules, payment rules, age/safety requirements, and developer policies before connecting a LifeRaft OS installation to an external platform.
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.
Connector QA
Test auth flow, entitlement lookup, event posting, network failure states, and engine/client package configuration.
Docs and support
Add customer-facing notes, admin setup instructions, and known limitations for the module.
Customer FAQ
Common questions about RLX Unity API
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.
Who is RLX Unity API best for?
Studios that need game-client identity, entitlement, event, or support handoff without building a private backend from scratch. Game & Engine Integrations builds that need RLX Unity API without forcing it into every install.
Can RLX Unity API run by itself?
RLX Unity API can run as its own Game Engines workflow. By itself, it focuses on Studio-owned Unity account links and entitlement checks, Signed event telemetry for analytics and progression workflows, and Self-hosted community and player operations portal, so a customer can use the module without buying every related add-on first.
Do I need the other add-ons mentioned on this page?
No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Unity API should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
What changes when related add-ons are active?
When the customer also owns and activates related modules such as RLX License Manager, RLX Analytics, RLX Support, RLX Updates, and RLX Achievements, RLX Unity API can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Which add-ons work well with RLX Unity API?
RLX Unity API commonly pairs with RLX License Manager, RLX Analytics, RLX Support, RLX Updates, RLX Achievements. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Unity API?
RLX Unity API should be launched with its real data model and public routes in mind. Optional integrations: rlx-license, rlx-analytics, rlx-support, rlx-updates, rlx-achievements.
How much does RLX Unity API cost?
RLX Unity API has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.
What support is included for RLX Unity API?
Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Unity API for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Unity API fit into a real LifeRaft OS build?
Activate RLX Unity API and review its add-on settings. Configure the module settings and permissions. Add the records, content, media, or rules this module manages. Review public pages and backend empty states before launch.
Does the public page include implementation details?
No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Unity API in your LifeRaft OS build?
RLX Unity API is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.