Supported requirements for challenge goals
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
| Areas | Base Requirements | Supporting Requirements | Goals | Purpose |
|---|---|---|---|---|
| Statistic | User's Statistics Value | Statistic Configuration | Need to set the goals value that will be compared with User's Statistics Value | Grant reward to the player upon earning a particular value for a specific statistic configuration |
| Statistic | User's Statistics Value for Specific Cycle | Statistic and Cycle Configuration | Need to set the goals value that will be compared with User's Statistics Value for Specific Cycle | Grant reward to the player upon earning a particular value for specific cycles for a specific statistic configuration |
| Achievement | User Unlock Achievement | Achievement Configuration | No | Grant reward to the player upon earning a particular achievement |
| User Account | User Login | None | No | Grant reward to the player upon successful login to the platform |
| User Account | User Create Account | None | No | Grant reward to the player upon creating an account in your platform using the publisher/studio namespace |
| User Account | User Create Game Account | None | No | Grant reward to the player upon creating an account in your platform using the game namespace |
| User Account | User Account Verified | None | No | Grant reward to the player upon verifying their account |
| User Account | User Account Linked | Third-party platform | No | Grant reward to the player upon linking an account in your platform with a third-party account using the game namespace |
| User Account | User Upgrade Headless Account | None | No | Grant reward to the player upon upgrading their account from a headless account to a full account |
| User Account | User Create Game Account with 3rd Party Account | None | No | Grant reward to the player upon creating an account in your platform from a third-party platform |
| Entitlement | User's ownership of items and its quantity | Store Item | Need to set the target value that will be compared with the user's Entitlement quantity. | Grant reward to the player upon owning or earning a number of particular 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.