Currently we allow arbitrary user IDs to become players, by sending elo! match 1 win 2 loss. But this doesn't make sense in production. So this has to be disabled after testing.

Currently, these go in the console with argparse, which isn't useful if the user does a typo somewhere...

If we are unsure about part of the scoring history, we can add score adjustment events which explicitly set the score of a particular user id.

A comment field will allow us to store comments about matches and circumstances under which scoring adjustments occur. (e.g. "Migrate scores with unknown history")

Currently, we are utilizing asyncio's locks to prevent race conditions in which two asynchronous operations access the match_history or user_status at the same time. However, these locks are currently in use for atomic actions only, while they should really be acquired for the entire duration of operations on the match history, until the entire operation is done and the match history or user status are in a valid state.

elo! match @mention1 win @mention2 at 2030-01-01 12:00 is valid but should be invalid.

Should happen upon changes in Elo or after recalculating the entire score history.

It's easier to reference events by number. Though this number may not be unique if the system is restarted, attempting to reference by timestamp is annoying. It's also somewhat neat to see a #42 in the corner.

• use categorical dtype for team status
• use csv (good for text), cpickle or hdfstore. pickle seems like the best option for numbers, but is no longer human readable. Maybe normally save as pickle, but save as csv or json if a user-editable version is desired. msgpack also seems like a good option.
• deserialization should produce the same df
• When to serialize? after each operation? on shutdown? additionally serialize periodically?

This is supposed to be an easter egg!

• Require a particular rank/role/permission node to add matches/administrate
• Restrict bot's replies to certain channels
• This should be configurable
• Nicely ask for permissions to change user's roles if that's configured
• Think about configuration for roles (by name, by id?)

Currently players can be recalled by mentions or beginning of name. Adding an option for recalling by id would allow for unambiguous addressing of players

Modify user inputs to prevent timezone issues that could result in creating matches out of order. Store timestamps in the database through one centralised timezone (something like UTC or GMT)

When events are inserted before already existing ones, this needs to cause a recalculation of elo. Otherwise,
in case this happens, we will have to run a recalculation in order to get correct Elo ratings.

There are many breaking API changes in the new version, we need to address these and move to the new version of discord.py.

The new documentation is available here.

Current delta events are inline. This means they will affect ratings of players other than the one they are set on. Having a delta mask event would allow points added from achievements, removed by punishments, and other manual changes to remain neutral for Elo rating, but still reflect on the player's status.

TODO:

• Add column for delta mask in the user status df
• Add delta mask event, rename delta inline event to delta_inline
• Add logic to update players using delta mask (only the delta_mask column is updated for users)
• Add logic to show players' masked scores (this can just be a function get_masked_elo which first calls get_elo and then adds the mask)
• Add logic to show both raw Elo rating and masked scores in the player cards
• Top players by scores, or by rating? (or both)

elo edit EVENTID NEWEVENT

EVENTID can just be given a type hint of int.

Check if the match history contains an event with that event ID.. If not, throw an error.

Using the new EloEventConverter, parse NEWEVENT. The passed type should be the same as the old event. Remove the old event, and add the new one to the match history.
All old optional values should remain the same. (i.e. if any optional values are None after parsing NEWEVENT, get them from the old event.)

We need to make sure that the EloEventConverter isn't filling in default values for things like K factor.

After everything's done, recalculate elo.

Title is currently truncated, contents of card are rounded.

• Limit number of top players to show
• Limit number of player cards sent at once

From rules/punishments in discord:
This sort of thing should be configurable, and is definitely low priority. Since this will vary greatly per implementation of rules, it may be left up to admins to do this.

Level 1 Infraction
Results in a warning more often then not, some cases may lead to being muted. Repeated Level 1 Infractions will result in a Level 2 Punishment.
Level 2 Infraction
One warning, and one warning only, repeating a Level 2 Infraction results in getting the Benched role, which does not mute you, but it prevents you from playing any ranked games. You will have the Benched Role for a day. Repeated Level 2 Infractions will result in a Level 3 Punishment.
Level 3 Infraction
There are no warnings for a Level 3 Infraction, you will instantly get Benched for 3 days, and depending on the situation, you will be muted for one day. Repeated Level 3 Infractions will result in a Level 4 Punishment.
Level 4 Infraction
There are no warnings for a Level 4 Infraction, you will instantly get Benched for a week, and you will instantly get muted, despite the punishment, for 3 days. Upon returning, you will lose 150 elo. Repeated Level 4 Infractions will result in a ban.

elo delete EVENTID

Straightforward. Delete the event with that event id, and then recalculate elo.