Logs (and part of the logs.tf API) is already in the bot, however a way to track every log that is played from a server that the bot has hosted is needed for ELO and other features in the future.
In addition to just tracking logs, adding the ability to set a channel for the bot to post logs automatically is a good idea.
The way I am currently thinking of setting this up:
On a team generation/team move (to support captained pugs), created a PartialLog object, that contains all players in the match represented as a Player object (which stores the discord ID and/or steam ID of each player), the guild ID, the PugCategory the match is being played in, and a timestamp.
These PartialLog object will be added to a queue, where a function will check for logs that match the steam ID's of the players in the PartialLog object. If a matching log is found, a Log object is created using the log data and all of the data stored in the PartialLog
The log will then be passed to functions that add it to the database, post it where it needs to go, passes it to ELO calculation (#16) etc.
Logs (and part of the logs.tf API) is already in the bot, however a way to track every log that is played from a server that the bot has hosted is needed for ELO and other features in the future.
In addition to just tracking logs, adding the ability to set a channel for the bot to post logs automatically is a good idea.
The way I am currently thinking of setting this up: