Achievements
Achievements synchronize meaningful game goals with the IGP platform. A project can unlock one-time achievements directly or report progress for cumulative achievements.
Support
Section titled “Support”| Engine | Status | Package | Detailed steps |
|---|---|---|---|
| Unity | Preview | Unity main package | Unity Quick Start |
| GameMaker | Preview | GameMaker main package | GameMaker Quick Start |
| Godot | Preview | Godot Core | Godot Quick Start |
All three engines report achievements through the Desktop Session. The game only needs an attached session and the achievement capability; it does not need to join a room or wait for realtime transport.
Integration flow
Section titled “Integration flow”- Define achievements in the backend and choose stable keys that do not depend on localized display copy.
- Complete Startup and connection and confirm that the current session advertises achievements.
- Trigger unlock or progress reporting at a clear business event such as level completion, collection completion, or a cumulative counter update.
- Keep the same idempotency identifier when retrying one business event. A network retry must not become a new event.
- Handle success, duplicate, and error results. A duplicate unlock normally means an earlier request succeeded and must not grant the in-game reward twice.
- Keep achievement clearing in test flows or explicitly authorized reset tools, never in the normal player path.
Design guidance
Section titled “Design guidance”- Keep achievement keys aligned with backend configuration while localizing names and descriptions separately.
- Use the game’s own save state to grant rewards; do not rely on one network callback to prevent duplicate rewards.
- Queue reportable events while offline and retry them with their original idempotency identifiers after reconnecting.
- Decide whether cumulative progress uses an absolute total or an increment before implementation.
Minimum verification
Section titled “Minimum verification”- A new achievement unlocks and appears on the platform.
- Repeating the same unlock does not grant the business reward again.
- A cumulative achievement grows according to its backend definition.
- A detached Desktop Session produces a clear failure or queued result and can be retried safely.
- Test-account clearing is absent from production player flows.