Your next feature
Player values
Server-owned currencies, counters and energy. Define balances, offers and checked changes for each project.

Your game shows configured balances and offers. Purchases return the current player state.
This step does not have a video yet. The guide and MCP request are ready to use.
Prepare the same project
Choose the same project in the dashboard as in your game configuration.
Player values →Create or reuse these test entries in the dashboard form. These are example values, not current project data.
- Values
coins: initialBalance=100, maxBalance=1000000; energy: initialBalance=10, maxBalance=100- Allow direct changes
false- Offers
energy-pack: costs=[{"key":"coins","amount":20}], rewards=[{"key":"energy","amount":5}]
Starting balances apply once per value key. Direct changes are off by default. Validated Actions keeps its own per-run bounds; daily and balance caps come from these definitions. Blank optional limits mean no cap.
Save, reload and verify the entries before running the example. Preserve unrelated definitions.
Build this feature
You can preview the guide. Running it requires an active project key. Prepare project
SDK installed, project configuration imported and player signed in.
This SDK example uses develop. Check whether the required APIs exist in your installed SDK.
Complete the Quickstart connection with the intended player. Call RunReviewedAction() from an explicit button or scene action. Opening the file alone sends no request.
Test your new feature.
Your game shows configured balances and offers. Purchases return the current player state.
Choose the same project in the dashboard as in your game configuration.
Endpoints
- GET
/player-values - GET
/player-values/offers - POST
/player-values/purchase - POST
/player-values/adjust


