You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 12, 2025. It is now read-only.
Allow people to sign up, by clicking a discord button or running a command.
On sign-up, collect a player's preferred server regions.
At the start of a PUG:
Require players to check in by joining a lobby VC, or clicking a button.
The PUG should only be scheduled like 15 minutes before the start, so anyone signing up will count as a check-in.
Ask tournament admins to confirm the team size, providing mathematically possible suggestions, and number of servers
Automatically make number of teams teams of team size size based on arbitrary ranking metric of each player. Assign a random name (an allegiance plus a character name?) to each team.
Alternate mode: pick the top number of teams players based on arbitrary ranking metric and let them select players one by one.
Create a Discord VC for each team. Automatically move members to their team's VC when they join the lobby VC.
The VCs can be private to only allow the team members to join. No reason to overcomplicate the bot's functionality.
Use Challonge API to create a bracket and retrieve the next number of servers matches which need to be played.
Every match:
DM the tournament admin to confirm details of number of servers concurrent matches (e.g. region / map supplied by the bot, admin confirms specific server and each team's password)
TOing should be done in a channel, so multiple people can work on it at the same time.
Once the info for a match is received, DM it to the correct players.
After a match, an admin submits the score to the bot.
Update the score on Challonge.
Update each user's matches won / lost statistic.
When the tournament has finished:
Make sure the tournament has finished on Challonge when the admin runs the command.
Send the final scoreboard on Discord
Update the top three teams' members' golds/silvers/bronzes stat
At all times:
Implement a centrifuge-style stats function to show user stats
When a PUG is scheduled:
At the start of a PUG:
Require players to check in by joining a lobby VC, or clicking a button.The PUG should only be scheduled like 15 minutes before the start, so anyone signing up will count as a check-in.
team size, providing mathematically possible suggestions, andnumber of serversnumber of teamsteams ofteam sizesize based onarbitrary ranking metricof each player. Assign a random name (an allegiance plus a character name?) to each team.number of teamsplayers based onarbitrary ranking metricand let them select players one by one.Automatically move members to their team's VC when they join the lobby VC.The VCs can be private to only allow the team members to join. No reason to overcomplicate the bot's functionality.
number of serversmatches which need to be played.Every match:
DM the tournament admin toconfirm details ofnumber of serversconcurrent matches (e.g. region / map supplied by the bot, admin confirms specific server and each team's password)TOing should be done in a channel, so multiple people can work on it at the same time.
When the tournament has finished:
At all times:
centrifuge-style stats function to show user stats