Game Engines add-on
RLX Unreal API
Unreal Engine bridge for LifeRaft OS account linking, entitlement checks, telemetry events, launcher/community links, support handoff, and studio connector packaging.
About this add-on
RLX Unreal API for LifeRaft OS
`unreal-plugin/RLXUnrealCompanions.h` defines companion intent shapes for analytics, achievements, and support handoff that can be exposed through Blueprint-callable nodes in the licensed plugin. Signing stays outside untrusted gameplay clients.
Unreal Engine bridge for LifeRaft OS account linking, entitlement checks, telemetry events, launcher/community links, support handoff, and studio 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.
- Self-hosted UE5 account linking and private player entitlement records
- Signed Unreal Engine telemetry routed into studio-owned infrastructure
- Progression events that can surface achievements, member levels, and profile flair
- Community, support, updates, and player identity in one owned portal
Capabilities and outcomes
How RLX Unreal 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 telemetry for a clearer day-to-day workflow
Structured player progression for a clearer day-to-day workflow
Structured achievements and profile flair for a clearer day-to-day workflow
Structured support handoff for a clearer day-to-day workflow
Add-on-specific scope
Bridge Unreal Engine player telemetry with owned community identity.
Use RLX Unreal API as a self-hosted operations layer beside a UE5 project. Signed progression and gameplay events can connect to private entitlement checks, account links, analytics, support context, achievements, member levels, and unlocked profile flair on a studio-owned player portal. It complements authoritative game servers rather than replacing gameplay networking, matchmaking, or anti-cheat infrastructure.
Standalone value
What it does by itself
RLX Unreal API can run as its own Game Engines workflow. By itself, it focuses on Self-hosted UE5 account linking and private player entitlement records, Signed Unreal Engine telemetry routed into studio-owned infrastructure, and Progression events that can surface achievements, member levels, and profile flair, 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 Unreal 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 Unreal API without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Unreal 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 Unreal 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 Unreal API are independent products and are not endorsed by, sponsored by, affiliated with, or partnered with Unreal Engine. 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 Unreal API
What does RLX Unreal API do?
Unreal Engine bridge for LifeRaft OS account linking, entitlement checks, telemetry events, launcher/community links, support handoff, and studio connector packaging.
Who is RLX Unreal 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 Unreal API without forcing it into every install.
Can RLX Unreal API run by itself?
RLX Unreal API can run as its own Game Engines workflow. By itself, it focuses on Self-hosted UE5 account linking and private player entitlement records, Signed Unreal Engine telemetry routed into studio-owned infrastructure, and Progression events that can surface achievements, member levels, and profile flair, 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 Unreal 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 Unreal 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 Unreal API?
RLX Unreal 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 Unreal API?
RLX Unreal 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 Unreal API cost?
RLX Unreal 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 Unreal 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 Unreal 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 Unreal API fit into a real LifeRaft OS build?
Activate RLX Unreal 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 Unreal API in your LifeRaft OS build?
RLX Unreal 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.