Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide whether to automatically name Voice Chat channels #79

Closed
pmonks opened this issue Jul 23, 2020 · 1 comment
Closed

Decide whether to automatically name Voice Chat channels #79

pmonks opened this issue Jul 23, 2020 · 1 comment
Labels
feature New feature, functionality or request functional Functional (i.e. user-visible) work wont MoSCoW - this WON'T be implemented

Comments

@pmonks
Copy link
Owner

pmonks commented Jul 23, 2020

Description of Problem:

When a match is upcoming, it would be ideal if the bot renamed an available Voice Chat (VC) channel for that match, so that the admins don't have to manage this manually.

When that match is over, it would be ideal if the bot were to rename the VC channel back to something generic (e.g. unused-1), so that the admins (and the bot, perhaps) can quickly determine which VC channels are in use vs those that aren't.

Complications

  • Determining a descriptive but short name for the VC channel may be difficult to automate. It may be that we need a map of full-team-name to abbreviated name will be necessary (e.g. "Manchester United" -> "ManU", "Sheffield United F.C." -> "Sheffield"), so that the VC chat can be called something like "ManU vs Sheffield".

  • There are many instances where there are more matches running concurrently than there are VC channels, so the bot would need some rule in order to determine which ones are the most important to assign to the (limited) VC channels.

  • Determining when a match is over (in order to rename it back to something generic) is quite tricky - either the football-data.org match API would need to be polled (which raises the risk of quota violations), or a hardcoded time limit on matches (e.g. 2.5 hours) would need to be chosen.

@pmonks pmonks added feature New feature, functionality or request functional Functional (i.e. user-visible) work could MoSCoW - this COULD be implemented labels Jul 23, 2020
@pmonks pmonks added wont MoSCoW - this WON'T be implemented and removed could MoSCoW - this COULD be implemented labels Apr 24, 2021
@pmonks
Copy link
Owner Author

pmonks commented Apr 24, 2021

I don't think this makes sense, given the sheer volume of concurrent matches, the relative lack of voice channels, and the difficulty of algorithmically determining which ones are of most interest to the community.

@pmonks pmonks closed this as completed Apr 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature, functionality or request functional Functional (i.e. user-visible) work wont MoSCoW - this WON'T be implemented
Projects
None yet
Development

No branches or pull requests

1 participant