-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
When import beatmaps downloaded from osu! website, the game marked the beatmap is not ranked, but beatmap downloaded from osu!direct is ranked #31496
Comments
As far as I can see, you tried to import these maps either from stable or in a large batch:
Additionally, your local online metadata cache is corrupted:
Normally this would lead to falling back to an API request, but it looks like you were also not logged in at the time:
so the online fallback could not be used and ultimately the status of the beatmap could not be determined. As a short term fix please delete On our side there are probably two things that can be done:
@peppy opinions? |
I'm not at home at the moment, when I get home, I'll try to delete online.db on the Stable and Lazer side, I'll also try to delete all beatmaps + user data on the Lazer side. After clean all the data in Lazer (Debian), I will start the setup wirazd to import map from Stable again. |
There is no need to touch stable. Please do not. |
Okay okay. |
I understand your point. Normally, the API will continue sending data to update the beatmap status even if the user is not logged in, and the status would be shown as ranked. However, in this case, it appears that the API request failed due to an authorization error, as indicated by the "Unauthorized" response. After deleting the online.db, I attempted to log in again, which initiated the star ratings calculation process. However, I noticed that not all beatmaps have been set to ranked status. Specifically, some beatmaps older than 2012 remain unranked. For example, "Baby Crushing Love" (mapped by peppy) is still unranked, even though the osu! website indicates it as ranked. This issue seems to affect multiple older beatmaps. (older than 2010) Additionally, I encountered a new error: beatmaps downloaded from the setup wirazd are still set to unranked status. Even reimporting from Stable did not resolve this issue. I'm unsure what might be causing these weird issues? Edit: here logs for debugging |
both of these sound fair, yeah. |
Please remove the beatmaps, restart the game, and only then try to reimport the beatmaps in question again. It's not working for you because beatmaps are not actually deleted from the hard drive until you restart, and for optimisation purposes reimporting undeletes beatmaps if it can. |
Addresses one of the points in ppy#31496. Not going to lie, this is mostly best-effort stuff (while the refetch is happening, metadata lookups using the local source *will* fail), but I see this as a marginal scenario anyways.
@ppy/team-web how feasible would it be to make the |
it's just adding it to the token requirement exception list in alternatively the client can request client credential token and do away with all the exception altogether (the oauth client will need adjustment for this) |
Fixed. But beatmaps downloaded from setup wirazd still marked as not ranked. |
Did you delete those, close the game, and reimport again? If yes attach logs again please. |
Yes, even I run the setup wirazd to download beatmaps (testing). Now, I'm not home so... no logs! (sorry) |
Grab logs remotely by using VNC + FTP |
The latest logs show rather clearly that the beatmaps were not deleted from the game...
These are the ones that don't have ranked status set, correct? |
Yes. But more than this. |
Type
Game behaviour
Bug description
When I open osu!lazer on my Debian 12 and try to import a beatmap from the osu! website I downloaded, the beatmap is marked as not ranked. However, when I download the SAME beatmap from osu!direct, it is marked as ranked.
Screenshots or videos
Version
2025.101.0
Logs
logs.tar.gz
The text was updated successfully, but these errors were encountered: