Objectives

Provide tools for a group of Badminton users, with fairness of use in mind.

Backlogs

• [ ] Add API servers to be able to use this website on multiple devices at the same time, while sharing data usage

Priority: Low/[Normal]/High

Impact: User - app owner

Pro:

• Data is funneled and stored on the server side.
• Easy to scale up
• Prevent client-side from external party usage

Con

• Need lots of effort, butthe user won’t see the difference

Objective:

• Refactor it to be in its own module for readability and maintainability

• [ ] Added MMR ranking players’ win/loss

  • [ ] Win or loss count
  • [ ] Win = 3 points
  • [ ] Loss = 0 points
  • [ ] Due Win = 3, Due Loss = 1
  • [ ] Tracked the record after the game finished
  • [ ] Finalized the total score board
  • [ ] Still not able to use, only collect the data for future use cases

• [ ] Planning attendance

  • [ ] Request to register the name with no option of chance (50:50)
    • [ ] Only CAN or CANNOT come
  • [ ] Pre-evaluate the pairing and game to wait
    • [ ] to pre-check the fairness (optional)
  • [ ] No need to add manually upfront

• [ ] Can edited history

  • [ ] Should not edit history? Does it represent the log unless there is a log record?

• [ ] Modify UI to better represent the player's status, maybe rethink about UI to show forced players’ wait and players who left early.

• [ ] Add Player name, Favorite so players can be added before starting the match easily

• [ ] Add ‘Nemesis’ constraint:

  • [ ] Two players cannot be on the same court
  • [ ] Two players cannot be on the same side of the court

• [ ] Ultimate goal:

  • [ ] Everyone can interact
    • [ ] Track the score
      • [ ] Win/Loss of every player (need to keep the record)
    • [ ] Game play
      • [ ] Whoever plays with most or/least
    • [ ] Waiting game
      • [ ] Average waiting game
    • [ ] Next game
      • [ ] Pair with who in the court
    • [ ] to Pay
      • [ ] Automate QR after the game to the PromptPay account.
  • [ ]

Doing

• [ ] Add shuffle logic when selecting players to play: see the player's match history and prepare a match with previously played matches in mind.

Priority: Low/[Normal]/High

Impact: User - app owner

           Player - app user, participant

Pro:

• Shuffle logic and prepare the next game match automatically without the need to shuffle

Con

• The user cannot request to take a break
• If the user takes a break, this will interrupt the next round of logic

Objective:

• Shuffle all players and all matches from the beginning, and real-time shuffle based on the history matched

Done

• [x] Have a calculator that can calculate how many players are needed to pay per game (calculate from everyone's total games)

  • [x] Phase 2: Each person's pay depends on how many games they have played - UI of how many players have been played needs to be rethought - Model of the player.ts needs to be updated to hold field priorityPoint and totalRoundsPlayed (to prevent misunderstanding the logic when a new player is added, They will automatically use the least totalRoundsPlayed from all the players as their own totalRoundsPlayed. - TODO: pending calculation logic !!

    ---

  • [ ] Modify UI to better represent the player's status

    • [x] Actual games play
    • [x] Point that use in shuffle logic
    • [ ] Actual game waited (may be also count 'forced waited players')

## Done:

1. Can add players
2. Can See list of players
   x. Bugs fixed <https://dev.to/kapi1/how-to-fix-page-not-found-on-netlify-a4i>
3. Can create a randomly match with another 3 player, 1 on the same team, 2 on the opposite team
   3.1 logic should be balanced, every person should play equal amount of games (Acceptable need feedback from friends)
4. Have partner history, you can see which players one already played with.
5. show "console.log" somewhere, or let user can export log for debugging purpose...
6. can move players around, as box
   or swap players around in court
7. Have matched history, you can see which matched you already play with which players.
   y. Bugs fixed: Many players experience playing against same person
8. Make it a true random (Done ?)
9. calling calculateFirstPriorityPlayer too many times ( not efficient).
10. Improve UI
11. Improve add function to set only selected players into a match
12. can add courts depends on how many players
13. In match-list view, when adding new player, new players should use least players played rounds as initial.
    z. Last match history depends on the match changes
14. Maybe rethink about how wait players affected shuffle decisions
    --> Removed wait players affected the decision in shuffle
    Z. Bugs fixed: First click in stand-by list is ignored
15. Fix wait counter increased when player is in status 'break'
    #dasd
16. number of 'selected' players doesn't need to be Divisible by 4
    to be ablue to shuffle into the court

17. Have a calculator, that can calculate how much player needed to play
    the calculation logic begin with
    25.1) Phase 1: Every person pay equally ... - calculate the price of the court: price of the court per hour multiply by how many courts and how many hours we played - calculate the price of the shuttle: price of the shuttle multiply by the amount of the shuttle we used - setting: default prices that can be adjustable

18. Have a calculator, that can calculate how much player needed to play
    25.2) Phase 2: Each person pays depends on actually how many games they have been played - UI of how many player have been played need to be rethink - Model of the player.ts need to be update to hold field `priorityPoint` and `totalRoundsPlayed`
    (to prevent misunderstood the logic when new player added,
    they will automatically use the `least totalRoundsPlayed` from all the players as their own `totalRoundsPlayed`) - TODO: pending calculation logic !!