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

Improve tournament pool logic to require switching less #1753

Open
Sendouc opened this issue Jun 1, 2024 · 0 comments
Open

Improve tournament pool logic to require switching less #1753

Sendouc opened this issue Jun 1, 2024 · 0 comments
Labels
tournaments Tournaments feature

Comments

@Sendouc
Copy link
Owner

Sendouc commented Jun 1, 2024

  • Pools have limit of 100 members in it after which they become unreliable
  • Current logic (inside Tournament class resolvePoolCode) has support for
  1. pool by group
  2. pool by bracket number
  3. pool by hosting team

We could make some further optimizations to reduce the amount of time people need to change pool during tournament name for small tournaments (and/or small brackets) say less than 48 teams (subject for optimizations) just use one pool for the whole tournament. So maybe something like:

  1. if tournament has less than X teams, use common pool
  2. if tournament has more than X teams but bracket has less than X teams, use common pool for the bracket
  3. Otherwise use current behavior
@Sendouc Sendouc added the tournaments Tournaments feature label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tournaments Tournaments feature
Projects
None yet
Development

No branches or pull requests

1 participant