Options to not start/pair by Lichess and not to show standings/trophies
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 597
- Forks
- 176
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
Hi,
I like to have 2 requests for the Swiss tournament that you have:
-
I know that we can upload our own pairings. It is very useful feature that we can have our own pairings. Can we have so that the tournament ONLY use our own pairings? Like an option that we can have when we create it. It means if we do not upload pairings, do not start the rounds automatically and do not pair for us because in the beginner we already define, "use manual/uploaded pairings". Mixing pairings algorithm can be bad. Use case: Team Tournaments, Custom Pairings, Round Robin, etc.
-
Since we upload our own pairings, can we not showing your standings? We usually put link in the tournaments that we have our official standings and trophies. Use case? Same as above, we want to run custom tournaments and give trophies.
-
Since we custom it, can we also have zero points bye for all? It means, do not add half byes for late players, and if no players not in the pairings, just give 0 (I think this one you already have).
If you ask why need Lichess then? Your lichess/room is strong and can handle thousands players in the room (a tournament), we need that.
thanks
Chacha
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Swiss tournament pairing, standings, and bye behavior described in issue #337, then identify the relevant API entry points and existing manual-pairing behavior. Done should include configurable uploaded-only pairings, optional standings or trophies display, and zero-point byes for unpaired or late players, with tests covering each option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100