Scheduled resets

A scheduled reset puts your members' invite counters, their message counts, or both back to zero on its own: once, at a date and time, or again and again on a repeat. Reset the invites on the 1st of every month at midnight, and your invite leaderboard becomes a monthly one.

A run does exactly what the reset commands do (/reset all invites, /reset all messages, /reset left invites, /reset left messages), at the time you chose, for every member or only for the members who left.

Scheduled resets are free: 1 per server, 10 with Premium.

Schedule a reset#

1. Dashboard → Scheduled resets, in the Engagement group of the sidebar.
2. Create a reset and choose what it resets: Invites, Messages or Both.
3. Choose for whom: Everyone, or only the Members who left.
4. Choose when: once, at a date and time, or on a repeat (see When it runs).
5. Choose the time zone of that date or repeat.
6. Save. Before it saves, the dashboard reminds you that a reset can't be undone.

Each reset then shows its next run and the result of its last one. You can edit or delete a reset at any time. Scheduled resets are managed on the dashboard only, with the Manage Server permission like every page of it.

What a run resets#

After a run, the leaderboards show the new counts, pinned leaderboards included, as after a reset command.

A run never touches:

• the scores of events, which keep their own;
• XP and levels;
• giveaway entries;
• the history of who invited whom: rejoin detection, the lists of invited members and analytics stay as they are;
• the audit log.

Members who leave after a reset#

A reset of everyone's invites also changes what happens when the members who joined before it leave: their departure no longer takes an invite back from their inviter, and doesn't change the inviter's counters at all. The new counts start clean and stay clean. Members who join after the reset count as usual. It's the same rule as for /reset all invites (see Management).

A reset of the members who left doesn't change how departures count.

When it runs#

Once#

At a date and time, from 1 minute to 1 year ahead, on the clock of the time zone you chose.

On a repeat#

On each of those days, it runs at every hour you choose (1 to 24 different hours) and at the minute you choose, the same for every hour. A reset never runs more than once an hour.

• A day that a month doesn't have (29, 30 or 31) runs on that month's last day, once: a reset on the 30th and the 31st runs once on 30 April.
• A yearly reset on 29 February runs on 28 February in the other years.

Time zones and changes of time#

The time zone you choose, such as Europe/Paris (UTC when there is none), is the clock of the date and of the repeat. A reset at 00:00 stays at 00:00 in that zone all year, across the changes of time:

• when the clocks go forward, a time that doesn't exist that day runs as late as the change: 02:30 becomes 03:30;
• when the clocks go back, a time that happens twice runs only the first time.

Good to know#

• A reset runs within a minute of its time. It never runs twice, even if the bot restarts meanwhile.
• Saving a repeating reset counts its next run from the moment you save.
• A one-off reset stays listed after its date, as done, skipped or failed. Give it a new date to plan it again, or delete it.

Skipped and failed runs#

A reset that comes hours after its time, when nobody expects it any more, would do more harm than good. So, rather than run late, a due reset is skipped when:

A run fails when an unexpected error remains after those 6 hours of retries. A repeating reset runs again at its next date; give a one-off reset a new date. If it keeps failing, ask in the support server.

After a skipped or failed run, the reset shows a warning with the reason, until its next run succeeds or you edit it. A skipped or failed one-off reset never runs later on its own.

In the audit log#

• Creating, editing and deleting a scheduled reset on the dashboard are recorded with the member who did it, like every dashboard change.
• Each run, done, skipped or failed, is recorded too, as an action of InviteCount itself: what was reset, for whom, and how many members.

InviteCount keeps the settings of each reset and the member who created it. See Audit log.

Free and Premium#

Everything else is the same on both plans. A one-off reset that has already run still counts until you delete it.

When Premium ends#

• Every reset stays saved, but only the oldest one keeps running.
• The others are paused: they are skipped when they are due, and they can be deleted but not edited.
• Repeating resets run again at their next date once Premium is back.

Reset now instead#

They need Administrator and ask for a confirmation first. See Management and Data management.

FAQ#

How do I make a monthly invite leaderboard?

Schedule a reset of Invites for Everyone, every month on day 1 at 00:00, in your time zone. Each month starts from zero. To keep a record of the month that ends, export the leaderboard before the reset (/export leaderboard, Premium).

Does a scheduled reset change my events?

No. Events keep their own scores, from their start to their end, and no reset ever touches them. See Events.

My reset didn't run. Why?

Look at its warning on the dashboard and at the audit log. A reset is skipped when the server lost Premium and it isn't the oldest one, or when InviteCount couldn't run it within 6 hours of its time. See Skipped and failed runs.