Daily Streaks

A streak is a run of days a member turned up and said something. They send enough messages to meet the day's goal, the day is claimed, and the number goes up. Miss a day and it goes back to one — unless the server sells them a way out.

The day that matters is the member's own day, not the server's. Somebody in Auckland finishes their Tuesday while somebody in Los Angeles is still in the middle of theirs, and both get counted for the day they actually lived through.

Turning It On

// Syntax
[prefix]streak enable [goal]

// Example
;streak enable 10

Needs Manage Server. The goal is optional — leave it off and it starts at 10 messages a day.

;streak disable    // stops counting, keeps every streak

Disabling only flips the switch. Nobody's run is lost, so turning it back on picks up where the server left off.

What Counts as a Message

Not every message earns progress, or holding down enter would be a strategy:

;streak set goal 15
;streak set cooldown 8
;streak set minlength 3

The cooldown is per member — one message every eight seconds counts, the rest are free to send and simply don't move the number. minlength 0 counts everything, including a bare k.

Claiming the Day

Meeting the goal is not the same as having the day. By default the member collects it themselves:

;streak claim

That is deliberate — a streak somebody has to show up and take is worth more than one that accrues in the background. Their profile turns orange the moment there is a claim waiting.

Autoclaim

If you would rather nobody had to remember a command, hand it to the bot:

;streak toggle autoclaim

With autoclaim on, the message that meets the goal claims the day by itself, and Serenity says so in the channel it happened in — who it was, and where their streak went:

🔥 @member met today's goal - streak 6 -> 7

[prefix]streak claim is switched off while this is on. The two are mutually exclusive on purpose: running both would have members racing an automation they can't see.

Keeping a Run Alive

// Syntax
[prefix]streak set grace [days]

// Example
;streak set grace 1

Grace is how many days a member may miss without losing the run. 0 is strict — one missed day and they start again at one. 1 forgives a single miss, which is usually the difference between a streak system people enjoy and one they give up on after the first weekend away. The ceiling is 7.

Restores

A run that has already lapsed can be bought back:

;streak restore

Restores are off until you configure them, and there are three numbers:

;streak set freerestores 1
;streak set restorecost 5000
;streak set restoredays 2

Free restores are spent before currency, and the month is the member's own local month — someone in Auckland gets their allowance back when their month turns over. Paid restores come out of the economy balance.

A run that lapsed longer ago than restoredays allows is gone for good. That window is the whole point of the setting: without it, currency would undo any absence at all.

Reward Roles

// Syntax
[prefix]streak rewards add [days] [role]

// Example
;streak rewards add 30 @Regular

;streak rewards remove 30 @Regular
;streak rewards list
;streak rewards reset      // deletes all of them, with a confirmation

A member's profile shows how far they are from the next one, so the ladder is visible before they reach it.

Three switches decide what happens to those roles afterwards:

Looking At It

;streak              // your own
;streak @member
;streak calendar     // the last 30 days
;streak leaderboard  // the longest runs here

The profile shows the current run, the personal best, total days claimed, the server rank and a progress bar for today. The calendar is a colour grid:

The leaderboard ranks by the run that is still alive, so a 200-day streak somebody dropped last month doesn't sit at the top forever.

Every Setting

;streak settings

Wiping It

;streak reset member @member    // one member's run and history
;streak reset all               // everyone, with a confirmation