NX10 Unity SDK
The bridge between your game NX10.
The Two-Way Street Mental Model
How data flows symmetrically between your Unity game loop and the NX10 backend.
Your Game Loop
Raw player behavior and dynamic match contexts are recorded silently.
NX10 Unity SDK
DontDestroyOnLoad SingletonNX10 AI Backend
Longitudinal pattern analysis extracts live cognitive and behavior metrics.
Fuzzy-matched identity profile across devices.
The Two-Way Street
The NX10 SDK is built on a symbiotic relationship. You provide us with the raw kinematic data (telemetry) and ground-truth emotional labels (SAAQ). In return, the SDK exposes incredibly powerful emotional insights back into your game code, allowing you to build reactive, highly-retentive player experiences.
1. The Observation Engine
In the background, the SDK instruments gameplay interactions, collects TAG data (Touch, Accelerometer, Gyroscope), and triggers SAAQ prompts to ask players how they feel at critical deviations.
2. The Insight Engine
Powered by NX10, the SDK fires C# events back into your game containing real-time metrics like the Game Behaviour Index (GBI) and Brain Charge Index (BCI), alongside 15-minute predictive emotional forecasts.
Frictionless Integration
We know that game developers don't have weeks to spend untangling third-party analytics. The NX10 SDK is designed to be a lightweight, drop-in addition to your existing architecture with minimal code footprint.
- Drop-In Singleton: There are no messy prefab setups or complex scene hierarchies to manage. Once user consent is obtained, calling
NX10Manager.Instance.StartSession()automatically bootstraps the necessary hidden GameObjects and handles their persistence across scene loads (DontDestroyOnLoad). - Zero-Config Telemetry: You do not need to manually wrap your UI buttons or rewrite your input handlers. Once a consented session is active and
StartTelemetry()is called, the SDK automatically hooks into Unity's native input systems to capture touch, gyroscope, and accelerometer data entirely in the background. - Simple State Sync: Keeping NX10 informed of what is happening in your game is as simple as firing a one-liner (e.g.,
NX10Manager.Instance.Attributes.SetAttribute("uiScreen", "boss_fight")) whenever your game's context changes. - Flexible Prompts (SAAQ): When the backend requests an emotional label, you can either use our pre-built, fully styleable UI popups for a zero-effort integration, or build your own custom questions to perfectly match your game's native aesthetic.
Privacy, Consent & Data Minimisation
NX10 operates under strict Data Protection Agreements (DPA) and independent Ethics board approvals. We collect only kinematic data alongside the game events and attributes you explicitly send—no message content, no personal text, and no identifiable gameplay visuals are ever captured by the SDK.
Partner Consent Responsibilities
- Wait for Consent Before Starting a Session: Do not call
NX10Manager.Instance.StartSession()until you have obtained valid consent from the user. - Stop the Session When Consent is Withdrawn: If a user withdraws their consent at any time, immediately call
NX10Manager.Instance.StopSession()to terminate the session and stop all data collection. - Pausing Telemetry Only (
StartTelemetry/StopTelemetry): During an active, consented session, callingStopTelemetry()stops high-frequency kinematic telemetry collection while allowing you to keep collecting Events and Attributes. CallStartTelemetry()when you are ready to resume kinematic capture.
