asobi_quests_period (asobi_quests v0.2.2)

Which window a quest counts in, and the key that names it.

Three periods. none counts forever and keys every row all; daily and weekly cut the count at a UTC boundary and key the row by the window it falls in, so a new window simply finds no row and starts at zero. Nothing has to run at midnight for a daily quest to reset - the key changing is the reset.

UTC, not a per-deployment timezone. A rollover boundary that moves with a configuration change would silently hand every player a second daily reward on the day it moved.

Summary

Types

period()

Functions

expired_before/3

The keys of every window of Period that closed more than Days ago, from the perspective of Seconds.

key(Period)

The period key for Period right now.

key/2

The period key for Period at Seconds (a UTC POSIX timestamp).

periods()

The periods a quest definition may declare.

Types

period()

-type period() :: binary().

Functions

expired_before/3

-spec expired_before(period(), non_neg_integer(), integer()) -> [binary()].

The keys of every window of Period that closed more than Days ago, from the perspective of Seconds.

Used by the rollover worker to delete progress nobody can advance or claim any more. Returned as a bounded list of exact keys rather than a < comparison, because the keys of two periods do not sort against each other: 2026-W01 is lexically less than 2026-01-05, so a single string inequality over the whole table would delete live weekly rows.

key(Period)

-spec key(period()) -> binary().

The period key for Period right now.

key/2

-spec key(period(), integer()) -> binary().

The period key for Period at Seconds (a UTC POSIX timestamp).

daily is YYYY-MM-DD; weekly is YYYY-Www on the ISO-8601 week, which is the only week numbering where the key of a Monday and the key of the following Sunday agree.

periods()

-spec periods() -> [period(), ...].

The periods a quest definition may declare.