Real-name verification and anti-addiction

Real-name verification and anti-addiction determine whether the current player may continue playing and what to do when verification, time-window, or duration restrictions apply. This is a separate compliance flow from game authorization.

Support

Engine	Status	Package	Detailed steps
Unity	Preview	Optional Compliance package	Unity installation
GameMaker	Preview	GameMaker main package	GameMaker Quick Start
Godot	Preview	Optional Compliance addon	Godot installation · Godot Quick Start

Godot 0.1.3 places real-name verification and the public anti-addiction surface under the Compliance addon. When it is absent, IGP.compliance is unavailable and Core does not expose a duplicate alias.

Integration flow

1. Complete Startup and connection, then install the engine’s Compliance package. GameMaker does not need a separate package.
2. Confirm the real-name verification and anti-addiction policy configured for the game in the platform backend.
3. Subscribe to compliance state before initialization.
4. Treat ALLOW as playable and map every BLOCK state to a clear pause or blocking flow.
5. When verification is required, open the temporary session returned by the SDK in the game’s own page or WebView. Do not collect or persist identity-document data.
6. When the state returns to allowed, close the blocking UI and let the game restore the systems it paused.

UI and gameplay responsibilities

The SDK can provide state and fallback UI, but the game remains responsible for the complete behavior:

• Block input to primary gameplay.
• Pause physics, AI, audio, and network behavior when needed.
• Handle page failures, Desktop Session detach, and unavailable services.
• React to later state changes instead of checking only once at startup.

The Godot Compliance fallback only blocks input. It does not pause the SceneTree, poll, show a countdown, or open a WebView. Unity and GameMaker projects should likewise avoid treating a visible message as a full gameplay pause.

Minimum verification

• A verified, eligible account enters the game normally.
• An account requiring verification can open the flow and handle cancellation or failure.
• Every BLOCK state prevents primary gameplay, and a later ALLOW restores it correctly.
• Unavailable services and unknown state do not become allow-by-default.
• A missing optional package or capability follows an explicit degraded path.