Godot Complete Projects

Every public Godot variant includes two standalone complete projects. igp-godot-sdk-test.zip presents Core, Compliance, and GameKit in one UI; igp-godot-multiplayer-sample.zip covers Arena rooms, the TCP/UDP data plane, Godot RPC, and automated E2E.

This is not an addon

Do not import igp-godot-sdk-test.zip into an existing project through AssetLib. Extract it first, then open its SDKTest/ directory as a standalone Godot project.

SDKTest download set

Download these files from the same row in Release Notes:

• igp-godot-sdk-test.zip
• igp-godot-sdk-core.zip
• igp-godot-sdk-compliance.zip
• igp-godot-sdk-game-kit.zip

All four files must use the same Godot SDK version and exact Godot version.

Run the project

1. Extract igp-godot-sdk-test.zip to obtain SDKTest/.
2. Import SDKTest/project.godot with the matching Godot version.
3. Follow Godot installation to import Core, Compliance, and GameKit into the test project.
4. Enable IGP SDK under Project Settings > Plugins.
5. Set igp/general/app_id under Project Settings > Igp > General to the test application. Also confirm that environment matches the target environment and do not retain values from another application.
6. Wait for native libraries and resources to finish importing, then run main.tscn.

The published project template excludes SDK addons and editor caches such as .godot and .import, so the downloaded SDK packages must be imported before the first run.

Coverage

• Desktop Session, capabilities, game authorization, and Core runtime events.
• Current user, avatar metadata, and avatar bytes.
• Achievement unlock, cumulative progress, and test achievement clearing.
• Real-name web session, anti-addiction state, compliance events, age range, and remaining time.
• Profile, batched player profiles, leaderboard reads/uploads, and text/data/image sharing.

Initialization and read-only state run after startup. Achievement, leaderboard upload, sharing, and other writes only run after their buttons are pressed. Confirm the test account and application configuration before using real backend keys.

Pass criteria

• The UI shows explicit attached, ready, authorization, and capability state.
• Core, Compliance, and GameKit sections detect their installed modules.
• Read-only requests return success or an explainable business error.
• Write operations only occur after a button action and show their results.
• Shutdown requests, authorization changes, and errors appear in the event log.

Multiplayer Sample

Download igp-godot-multiplayer-sample.zip, Core, and the Multiplayer addon from the same Release Notes row. Extract MultiplayerSample/ and import both addons; all files must use the same SDK release and exact Godot version.

The project README documents every directory entry, the manual two-instance flow, and Run-LocalE2E.ps1. The sample does not enable the Desktop Autoload: automated E2E creates or joins an Arena room directly, obtains a per-player descriptor, and requires both host and client to exchange reliable and unreliable messages. Production integrations still use IGP.create_multiplayer_peer() to obtain that descriptor through Hosted Session.

Troubleshooting

• Native library load failure: verify the exact Godot version and Windows x86_64 variant.
• Missing IGP: confirm that Core is imported and IGP SDK is enabled.
• Optional module is null: check its fixed res://addons/... path, stop the game, and run it again.
• APP_ID_REQUIRED: set a valid positive igp/general/app_id.
• Missing capability: check desktop-client version, sign-in, backend application configuration, and environment.