zelzahn / moleskine Goto Github PK

Don't store the username and discriminator of a user in the database because these can change and thus are unreliable. Even if this is used for logging, olny the id should be used as this is the only reliable thing in a database.

Cumulative for repeated voting for a candidate

Through this

Currently when there's a backend related error this error isn't handled by the frontend and thus not correctly processed.

Lot's of functions are quite confusing right now, thus documentation should be added.

This bloats the database

Starting a vote and then sending cancelled doesn't work.

Maybe when issuing the nextWeek command a graph could be shown on each guild that displays the percentage of voters who think the mole was for that week?

See the weekChange command.

Support multiple years without wiping the data