Check which SDK features are available
Distinguish a declared API from an enabled product feature.
Availability is more than a type
A method in the SDK declaration can exist before its production flow is available. The host may return a valid negative outcome, and a development panel may simulate a response that production does not provide.
| Feature | What to expect |
|---|---|
| Lifecycle and host events | Implemented. Initialise before calls and handle pause, resume, mute and resize. |
| Saves | Implemented host stores; account, device and preview storage differ. |
| Scores | Implemented host integration. Signed-out or ineligible submissions can return accepted: false. |
| Result sharing | Implemented host feature with availability and break checks. Previews do not provide public sharing. |
| Custom events | Implemented numeric event path. Do not infer that every planned dashboard is present. |
| Project images and sound | Implemented local SDK asset helpers and media pipeline. |
| Ads | API and simulation exist. Actual network availability is deployment-dependent; handle no fill. |
| Purchases, entitlements and items | Not available as a complete creator commerce flow. Do not depend on successful purchases or item grants. |
| Paid-content loading | Not ready for a complete paid-content distribution workflow. |
| Rooms and rules | Future multiplayer milestone. Start current games in solo mode. |
| Series-wide saves | Reserved for a later phase; not a replacement for game-scoped saves. |
Before adopting a feature
- Read the relevant SDK guide and the outcome it describes.
- Select supported dependencies in Studio Libraries and Project settings.
- Check the availability messages shown for your account.
- Test negative outcomes, not just simulated success.
Do not fabricate success when the host refuses an action. Keep the game playable without optional platform services where appropriate.