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

Use CTFTime team rating for member rating to be more fair #48

Merged
merged 1 commit into from
Apr 14, 2021

Conversation

lanjelot
Copy link
Collaborator

Before, if a member played a CTF by himself, they would get a huge bump on the ranking ladder because no one else played.
Now we are using the team rating shown on CTFTime once the CTF is over, which fixes this issue.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@lanjelot
Copy link
Collaborator Author

lanjelot commented Apr 12, 2021

Just to clarify how member rating is now calculated, here's an example:

  • members chris and joe play CTF xyz
  • chris scores 70% of the points for the team (and joe 30% obviously)
  • once the CTF is over find the CTFTime team rating for that CTF at https://ctftime.org/team/$teamid (e.g. https://ctftime.org/team/10288)
  • the team rating is based on the final CTF weight and how high the team ranked at that CTF (see https://ctftime.org/rating-formula/)
  • save the team rating to the CTF page on ctfpad (let's say the team got a team rating of 10.0 for that CTF xyz)
  • on the ctfpad stats/ranking page, chris' rating goes up 7 points (70% of 10.0), and joe's goes up 3 points.

Now let's say joe plays by himself at the following CTF. Although he obviously scored 100% of points for the team, his rating on ctfpad will only go up by X points, where X is the CTFTime team rating for that second CTF, which can only be negligible unless he managed to rank the team high at a heavy-weighted CTF :)

@hugsy hugsy merged commit ce6de61 into master Apr 14, 2021
@lanjelot lanjelot deleted the team-rating branch April 17, 2021 05:44
@hugsy hugsy added this to the 0.1 milestone Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants