Use the SDK by feature

These docs are organized by feature. Start by confirming the SDK feature set, then open the integration examples for the target feature in each engine. Engine folders only contain installation, Quick Start, debugging, and sample project details.

Feature matrix

Core and desktop client capabilities

Feature	Main purpose	Unity	GameMaker	Godot	Prerequisites
Startup and connection	Make the SDK available in game	Preview	Preview	In development	appId, explicit initialization, IGP desktop client
Game authorization	Verify legitimate game ownership	Preview	Preview	No standalone entry yet	Connected IGP desktop client
Real-name verification and anti-addiction	Determine current playability	Preview, optional package	Preview	Not supported	Connected IGP desktop client, handling mode selected
Achievements	Unlock achievements and report progress	Preview	Preview	In development	Connected IGP desktop client

Multiplayer lobby capabilities

Feature	Main purpose	Unity	GameMaker	Godot	Prerequisites
Multiplayer lobby	Entry point for room-based multiplayer	Preview	Not supported	In development	Launched by IGP desktop client
Rooms	ready, start, finish, leave	Preview	Not supported	In development	Launched by IGP desktop client
Realtime messaging	Send custom messages inside a room	Preview	Not supported	In development	Already joined a room
State and RPC	Sync room state and call remote logic	Preview	Not supported	In development	Already joined a room
Mirror transport	Connect Unity Mirror projects to IGP transport	Preview, optional package	Not applicable	Not applicable	Unity, Mirror, already joined a room

Choose an entry point

• To understand the SDK feature set, start with this feature matrix.
• To integrate the SDK base flow, read the initialization method in Startup and connection.
• To decide whether the player can enter the game, read Game authorization and Real-name verification and anti-addiction.
• To integrate player progression or rewards, read Achievements.
• To integrate room-based multiplayer lobby capabilities, start with Multiplayer lobby, then open rooms, realtime messaging, state and RPC, or Mirror as needed.

Recommended reading order

1. Review the feature matrix on this page and confirm the SDK features currently available.
2. Open the target feature page and confirm supported engines and prerequisites.
3. If installation, Quick Start, or debugging details are needed, open Engine integration details.
4. Return to the target feature page and complete integration in the recommended order.
5. After integration, run the checks in Testing.

Status definitions

• Preview: A usable entry point exists, but changes may still occur during the preview stage.
• In development: Code or samples exist in the repository, but they are not yet a stable public deliverable.
• Not supported: The current engine has no entry point for this feature.
• Not applicable: The feature only applies to a specific engine or technology stack.