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

Handle new beatmap versions #104

Open
PatTheHyruler opened this issue Nov 27, 2022 · 0 comments
Open

Handle new beatmap versions #104

PatTheHyruler opened this issue Nov 27, 2022 · 0 comments
Labels
Difficulty: Medium Harder than easy Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Available No one has claimed responsibility for resolving this issue. Generally this will be applied to bugs a Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@PatTheHyruler
Copy link
Collaborator

Figure out what to do with beatmaps getting updated and BeatSaver returning new beatmaps for old hashes

@PatTheHyruler PatTheHyruler added Priority: High After critical issues are fixed, these should be dealt with before any further issues. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Status: Available No one has claimed responsibility for resolving this issue. Generally this will be applied to bugs a Difficulty: Medium Harder than easy labels Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Difficulty: Medium Harder than easy Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Available No one has claimed responsibility for resolving this issue. Generally this will be applied to bugs a Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

1 participant