Determining a Bye after a drop should take into account who has already faced that player.
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
For example, my round two opponent dropped, then it gave me the bye for round three. I was expecting it to go to one of the other 3pointers who hadn't yet faced the dropped player.
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
Reproduce the round-three bye scenario described in the issue, where a round-two opponent has dropped, and trace the tournament pairing logic that selects the bye recipient. Done means the bye considers which players have already faced the dropped player, with the reported scenario assigning it to an eligible player who has not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100