Engine integration details

This page only collects engine-specific details: installation, Quick Start, debugging, and sample projects.

The main reading order for the SDK docs is still feature-first. If you have not confirmed the target feature, start with Feature overview.

Unity

Unity is the current primary delivery engine and has the broadest feature coverage. Recommended path:

1. Confirm Unity support for the target feature in Feature overview
2. Open the target feature page and read the Unity section first
3. When installation or debugging details are needed, read Unity overview
4. Add the SDK to the project with Unity installation
5. Complete Unity Quick Start
6. Confirm Startup and connection
7. Return to the target feature page and continue integration
8. Complete validation with Testing
9. For Editor debugging, read Unity debugging
10. If the project already uses Mirror, also read Mirror transport

Godot

The Godot adapter is still in development and is not a formal public deliverable yet.

• Godot overview
• Evaluation feature entry points are listed in Use the SDK by feature
• The basic startup flow is covered in Startup and connection

GameMaker

The first GameMaker release targets Windows 10 and later. Game authorization, real-name verification and anti-addiction, and the main achievement flow are available:

1. Confirm GameMaker support for the target feature in Feature overview
2. Open the target feature page and read the GameMaker section first
3. When installation or debugging details are needed, read GameMaker overview
4. Add the SDK to the project with GameMaker installation
5. Complete the minimal validation flow with GameMaker Quick Start
6. Confirm Startup and connection
7. Return to the target feature page and continue integration
8. Complete validation with Testing
9. To troubleshoot state or errors, read GameMaker debugging
10. To inspect exported functions, read Native Bridge

Unreal

The Unreal adapter has not started yet.