Skip to content

Instantly share code, notes, and snippets.

@tt2468
Last active April 27, 2020 13:06
Show Gist options
  • Save tt2468/620dcc4d3f7dd03cf58881e29b6e37fb to your computer and use it in GitHub Desktop.
Save tt2468/620dcc4d3f7dd03cf58881e29b6e37fb to your computer and use it in GitHub Desktop.
Counting Poll

The problem:

Counting has grown a lot in the past, and with that growth, some fundamental problems have emerged. In order to allow counting to continue growing, we have been rewriting various parts of the bot. Unfortunately, in the process we have identified a few problems that would likely result in data loss.

The options:

Because of this problem, there are 2 possible options.

  • Proceed with slowly rewriting the bot, and in the process risk things like votes and counts being completely reset
  • Schedule a date to completely reset all data. This gives us the opportunity to do a complete rewrite and fix the fundamental problems with the bot, without worrying about preventing data loss

Our idea:

As for the devs, we support doing a full reset. With the current bot, ~75% of the time we spend rewriting the bot is put into trying to prevent as much data loss as possible. So, we support doing a full reset.

TLDR; No reset = Most stats kept, random stats lost - Reset = All stats reset, get everything over faster


We invite you to vote on these options

@bekaertruben
Copy link

If you're going to reset all data, perhaps allow server moderators to set the current number, but when they use it don't allow their score on the leaderboard. This might allow people with a high score to continue but without it being competitive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment