Step 4: Achievement dependent on
Select Category, Achievements that will be dependant on this achievement and metadata.
DEPENDANT ON
EXAMPLES
Category | Optional Array [String] | Lets you filter the Achievement in the back office. | |
Dependent On | Optional Array [Object] | You can specify a particular achievement (by Name) as a dependency to be eligible for your current achievement. When adding a dependency on other achievements, they can be in a must, should or must-not rule. Dependent on achievements cannot be seen by the player. This lets you build complex achievement trees to meet your goals. For Example: | |
| an achievement that triggers after "5 free spins if you win once" with a dependent on achievement with a rule of Must of "register" means that you cannot complete the first achievement if you don’t register. | ||
| an achievement that triggers after "5 free spins if you win once". Adding 2 dependent on achievements: 1 - with a Should rule of "register" means the user has to register and 2 - with a Should rule that the user has to "log in" means that you can not complete the first achievement (5 free spins) if you don’t do one of the two dependent on achievements. | ||
| an achievement that has been created to get "5 free spins if you win once" and adding a dependent on achievement with a Must-not rule that is achieved when a player "redeems a voucher" means that the players who redeemed a voucher will not get the "5 free spins if he wins once". | ||
Metadata | Optional Array [Object] | Optional information you can use to store reference information. |
APP Example:
Category | Returning | |
Dependent On | N/A | |
Metadata | Key | Login |
Value | 1 |
API Example:
{ |
A full example of POST Achievement can be found in the Achievements APP API documentation here
Click Next and continue to the next step.