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

Automatically hide obsoleted scores / split up site #511

Open
KirbyComment opened this issue Oct 4, 2024 · 0 comments
Open

Automatically hide obsoleted scores / split up site #511

KirbyComment opened this issue Oct 4, 2024 · 0 comments

Comments

@KirbyComment
Copy link

When submitting a score that beats an older submitted score of yours in the same category, it should be automatically hidden from the leaderboard. Currently there's several instances of players hogging multiple 1st/2nd/3rd place ranks, meaning the Player Rankings page serves no real purpose anymore. While it can be made a rule to not allow this to happen, we can't expect players to hide old scores manually.

The quick solution would be to automatically hide all lower scoring replays even if they're runs focused on survival/pacifist/etc.
The long-term solution could be to seperate parts of the site to only focus on specific replay types or display types (just like how RF has replay.royalflare and score.royalflare).

survival = survival replays only
score = all replays displayed by score (no duplicates) - this is the only section that Player Rankings takes into consideration
replay = displays all replays from both sections, ordered by postdate (replays can't be submitted here directly)
(https://discord.com/channels/928695122558857216/928695122558857219/1269742388893585540)

When submitting a replay, you can then choose between either survival or scoring and the site will automatically place the replay in either of the two appropiate sections + replay.silentselene.

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

No branches or pull requests

1 participant