チャレンジ目標についてサポートされている要件
Introduction
In AccelByte Gaming Services (AGS), a challenge contains goals and the goals contains requirements, which refer to tasks or activities that players have to complete in order to accomplish the goal. AGS allows combinations of requirements in a single goal using OR or AND logic.
This article provides a list of the available requirements in AGS that you can add to challenge goals.
To learn how to create goals and rewards for a challenge, see Create goals and rewards.
Supported requirements for challenge goals
| Area | Base Requirement | Supporting Requirement | Goal | Purpose |
|---|---|---|---|---|
| Statistic | Player's statistic value | Statistic Configuration | Set a goal value to compare with the user's statistic value. | Grant a reward when the player's statistic value reaches the goal. |
| Statistic | Player's statistic value for specific cycle | Statistic and Cycle Configuration | Set a goal value to compare with the user's statistic value for a specific cycle. | Grant a reward when the player's statistic value reaches the goal within a specific cycle. |
| Achievement | Player unlocks achievement | Achievement Configuration | N/A | Grant a reward when the player unlocks a specific achievement. |
| User Account | Player logs in | N/A | N/A | Grant a reward when the player logs in to the platform using their credentials or via the authorization code option. |
| User Account | Player logs in with third-party account | N/A | N/A | Grant a reward when the player logs in to the platform using a third-party account. |
| User Account | Player creates account | N/A | N/A | Grant a reward when the player creates an account on the publisher or studio namespace. |
| User Account | Player creates game account | N/A | N/A | Grant a reward when the player creates a game account on the game namespace. |
| User Account | Player verifies account | N/A | N/A | Grant a reward when the player verifies their account. |
| User Account | Player links account | Third-party Platform | N/A | Grant a reward when the player links their account on the game namespace to a third-party platform. |
| User Account | Player upgrades headless account | N/A | N/A | Grant a reward when the player upgrades their headless account to a full account on the game namespace. |
| User Account | Player creates game account using a third-party platform | N/A | N/A | Grant a reward when the player creates an account on the game namespace using a third-party platform. |
| User Account | Player has full account status | N/A | N/A | Grant a reward when the player registers an email address for their account, achieving full account status (with or without email verification). |
| Entitlement | Player own specific items in specific quantities | Store Item | Set a target quantity to compare with the user's item ownership. | Grant a reward when the player owns or earns a specific quantity of items. |
Player progression update
Manual and auto-update of player progression data
- Statistics and Entitlements are areas that are non-event based requirements. These require manual evaluations on the game server or client implementation before retrieving the updated player's progression data. For more information about the manual evaluation process, refer to the Evaluate the challenge section in the Integrate challenge interaction in the game client article.
- The event-based requirements (i.e., User Account and Achievement) run an automatic background process to update the player's progression. This means that player's progression data is refreshed without having to do a manual evaluation process similar to the Statistic and Entitlement requirements.
Update process and delays
All requirements run asynchronously in the background which may be subject to delays when getting the player's updated progression data. Both non-event and event-based requirements need processing time, with the process starting from the moment the user initiates an action or submits an evaluation request up to when the progression update is completed. This may result in progression update delays as several factors could impact the processing time, including (but not exclusive to) high traffic or load and infrastructure hiccup.
Due to potential delays from the processing time required for updating the progression data, we recommend implementing a retry mechanism to make sure that the game client or the server updates the player's progression data as quickly as possible.