Step 2: Achievement scheduling

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

SCHEDULING

EXAMPLES

Availability

Required

DateTime

Available from (date) - Select the date (day/month/year) and time (hour:minute) in UTC time from when the achievement will be available to the players to receive the achievement when the achievement will be in live state.

Optional

DateTime

Available until (date) - Select the date (day/month/year) and time (hour:minute) in UTC time from when the achievement will be unavailable to the players. This field can be left empty which would indicate that the achievement is indefinite.
Occurrence

Required

Enum

How many times, or when, the achievement can be received.

Possible options:

Once
the created achievement is triggered only once
Repeatedly
the created achievement is triggered every time the conditions have been met
On these days
the created achievement is triggered once on weekdays like Mondays, Tuesdays. You can pick one weekday (for example only on Mondays) or more than one (for example on Mondays and Fridays)
On these weeks
select the weeks (1 - 52) of the years when the achievement can be triggered once
On these months
select the month or months when the achievement can be triggered once

APP Example:

Achievement available

from
12/09/2018, 10:17 am UTC
till

N/A

Members can achieve
Once

API Example:

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

A full example of POST Achievement can be found in the Achievements APP API documentation here


 Click Next and continue to the next step.

 If any required information is missing, the field is shown in red as in the example below.