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

Stage tiers #884

Open
tsa96 opened this issue Jan 6, 2024 · 1 comment
Open

Stage tiers #884

tsa96 opened this issue Jan 6, 2024 · 1 comment
Labels
Blocked: Needs more info This is lacking essential information like steps to recreate or a video showing reported behavior. For: Backend This is something to do for the backend (server folder) of the website. For: Frontend This is something to do for the front end (client folder) of the website. Priority: Low Something not very essential to the release, can be done in free time and bumped back if needed. Size: Small Something that may take a day at most to do. Type: Enhancement Something that builds on top of what already exists

Comments

@tsa96
Copy link
Member

tsa96 commented Jan 6, 2024

Initially we weren't going to support let submitters/approvers set tiers for stages, @jason-e was the main advocate of not supporting it. But we've been discussing RJ/SJ maps in today's meeting, and Mac brought up RJ courses often being tiered. Plus, some stages on surf/bhop do have tiers, e.g. omnific.

Approach we decided on was to make stage tiers optional, where the submitter can choose whether they want tiers or not. If yes, they must suggest tiers for every stage. Reviewers will only be able to suggest tiers for stages if the submitter selected to tier it. Submitter and mods should be able to switch to enable stage tiers.

In the leaderboard selection UI, we should try to subtly set the colour of the stage button based on the tier, and have a tooltip - showing it outright would really clog up the UI and it usually isn't super important.

Since this can easily be tacked on to my on-going work, I'm self-assigning and not going to bother writing a precise spec right now.

@tsa96 tsa96 added Type: Enhancement Something that builds on top of what already exists Size: Small Something that may take a day at most to do. Priority: High Should be done first and foremost, absolutely essential for this release. For: Backend This is something to do for the backend (server folder) of the website. For: Frontend This is something to do for the front end (client folder) of the website. labels Jan 6, 2024
@tsa96 tsa96 self-assigned this Jan 6, 2024
@tsa96 tsa96 moved this to Todo in Map Submission Feb 14, 2024
@tsa96
Copy link
Member Author

tsa96 commented Dec 20, 2024

From team meeting discussions we sound pretty ambivalent to this and it's a lot of work and awkward in terms of UI/UX. Going to move off the Map Submission board, lower priority, and if we get a lot of requests for this after 0.10.0 release we could reconsider.

@tsa96 tsa96 removed this from Map Submission Dec 20, 2024
@tsa96 tsa96 removed their assignment Dec 20, 2024
@tsa96 tsa96 added Priority: Low Something not very essential to the release, can be done in free time and bumped back if needed. Blocked: Needs more info This is lacking essential information like steps to recreate or a video showing reported behavior. and removed Priority: High Should be done first and foremost, absolutely essential for this release. labels Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked: Needs more info This is lacking essential information like steps to recreate or a video showing reported behavior. For: Backend This is something to do for the backend (server folder) of the website. For: Frontend This is something to do for the front end (client folder) of the website. Priority: Low Something not very essential to the release, can be done in free time and bumped back if needed. Size: Small Something that may take a day at most to do. Type: Enhancement Something that builds on top of what already exists
Projects
None yet
Development

No branches or pull requests

1 participant