Skip to main content
This path is for teams building their game in Godot, GameMaker, or a custom (in-house) engine. Unlike Unreal and Unity, these engines don’t have a first-party XBOX plug-in — you’ll integrate the GDK yourself, typically by wrapping GDK APIs behind an engine plug-in or native module.
Is this the right path for you? Pick this if your engine isn’t Unreal or Unity. If you’re using Unreal or Unity, jump to Unreal or Unity — they have dedicated tooling that saves you a lot of work.

Before you start

Make sure the following are in place. If anything is missing, go back to the Home guided path.

Build & develop

GDK and engines

How the GDK plugs into Godot, GameMaker, and custom engines.

Godot integration

Use the XBOX Godot sample to integrate the GDK, XBOX services, and PlayFab.

GameMaker integration

Prepare a GameMaker Studio 2 game with the GDK Extension.

Custom engine integration

Bind GDK APIs from a proprietary C/C++ engine.

Packaging

Package your title for XBOX and Windows.

Error handling

Handle HRESULT, XError, and service errors across the GDK.

Add services

XBOX Services overview

Identity, achievements, multiplayer, cloud saves.

PlayFab overview

Player data, live-ops, and backend services.

XSAPI C reference

Call XBOX Services from native code.

Custom engine integration

Direct GDK integration patterns.

Publish

Publishing overview

End-to-end submission workflow.

XBOX Requirements

XR compliance.

Certification

Cert process.

Store listing

Product page setup.

Pricing

Pricing.

Ratings

Age ratings.

Optimize & reference

Optimize

Profilers, diagnostics, and performance tools.

API References

Gaming Runtime, XBOX Services, and platform APIs.
Last modified on August 21, 2026