Step 2: Achievement scheduling

Scheduling controls when an Achievement is available and how often a player can get it.

SCHEDULING fields

EXAMPLES

» Availability DateTime

Mandatory

Available from (date/time) – Select the date (day/month/year) and time (hour: minute) in UTC time when the Achievement will become available for players to receive.

Optional

Available until (date/time) – Select the date (day/month/year) and time (hour: minute) in UTC time when the Achievement will become unavailable to players. This field can be left empty if an Achievement is on-going.
» Occurrence Enum

Mandatory

How many times, or when, an Achievement can be received.

Possible options:

  • Once – an Achievement is triggered only once
  • Repeatedly – an Achievement is triggered every time the conditions are met
  • On these days – an Achievement is triggered once every weekday, e.g. on Mondays. You can pick one or more weekdays (e.g. on Mondays and Fridays)
  • On these weeks – selects the weeks of the year (1 – 52) when an Achievement can be triggered once
    Note!
    Please note that “On these weeks” functionality is in the testing faze.
  • On these months – selects the month or months when an Achievement can be triggered once.

APP Example:

Achievement available from12/09/2018, 10:17 am UTC
Achievement available untilN/A
Members can achieveOnce

API Example:

 

{
    "jsonClass": "Achievement",
    ...
    "scheduling": {

    "scheduleType": "Once",
    "every": [],
    "startDate": "2018-09-12T10:17:36.172+02:00",
    "onlyAggregateOnActiveDays": false
    },
    ...
}

The API example provides only a simplified version of the POST body. A full example of POST Achievement can be found in the Achievements APP API documentation here.

MISSING ENTRIES
If any mandatory fields are missing, the field is shown in red as in the example below.

PREVIOUS – Click Previous and go back to the previous step.

CONTINUE – Click Next and continue to the next step.

Back To Top