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

Proposal: Remove Short Matches #33

Closed
samdking opened this issue Nov 19, 2020 · 1 comment
Closed

Proposal: Remove Short Matches #33

samdking opened this issue Nov 19, 2020 · 1 comment
Assignees
Labels

Comments

@samdking
Copy link
Owner

samdking commented Nov 19, 2020

The concept of short matches was added to accommodate for mid-match changes to teams. Be it through injury or 1 team massively beating another. There were 3 instances where this occurred (twice in 2015 and once in 2017). A similar event occurred recently, in 2020, and it was decided a new match type ("void") should be created to represent this match.

Void matches count towards attendance and partnerships but nothing else. Scores nor results are recorded.

The problem with short matches

  • Attendance counts as double (provided you didn't drop out through injury)
  • Results in a short match carry the same weight as results in a full match
  • They're untidy and largely obsolete now due to void matches

Proposal

  • Remove the 2nd of each pair of short matches
  • Change the 1st of each pair to be void (and scrub the result)
  • Add injury flags for the 2 occurrences were injury changed the teams

Affected matches

  • 22nd June 2015: 10 - 1
  • 22nd June 2015: 4 - 6
  • 20th July 2015: 11 - 4
  • 20th July 2015: 6 - 4
  • 3rd April 2017: 3 - 3
  • 3rd April 2017: 16 - 7

Knock-on effects

This will mean:

  • A reduction in Pld, W, D, L, F, A, Pts totals for those involved in any of the short matches
  • A change in GD and Win % (for some positively, for others negatively)

However, if it is done before the next match (provisionally 7th December 2020):

  • No attendance milestones (100, 200) will be affected
  • No win milestones (50, 100) will be affected
  • In the all time rankings, only 1 meaningful change of position will occur (Alex will drop from 13th to 15th)
  • No change to the top 4 of the 2015 leaderboard
  • No change to the top 4 of the 2017 leaderboard

Current top 20 all-time leaderboard

Screen Shot 2020-11-19 at 19 50 25

New top 20 all-time leaderboard

Screen Shot 2020-11-19 at 19 49 43

@samdking
Copy link
Owner Author

samdking commented Dec 1, 2020

Done.

@samdking samdking closed this as completed Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants