-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Difficulties randomly lose ranked status #30022
Comments
I'm gonna need a link to whatever this is to even start looking whether this is an actual issue or not. |
https://www.youtube.com/watch?v=QlJOV2Z02ZI&t=1s |
So I did run the thing where you can import your maps from stable into lazer yesterday and now I have 2 Highways of Oblivion (in lazer only) which are both exactly the same. Also, 3 diffs of Higher's High lost ranked status (lazer only) and I checked the songs file in stable and I now have 2 versions of the beatmapset, one with the identifier number in front of it and one without. Idk if these things are part of the problem but I thought it wouldn't be bad to post them anyways. |
Ok just had the case that the map (https://osu.ppy.sh/beatmapsets/1999204#osu/4156030) had no working audio for some reason in stable and lazer, however it got fixed in lazer when I downloaded the map again. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Type
Game behaviour
Bug description
So in stable and lazer it can happen that maps randomly lose their ranked status (not sure if this can happen with loved as well)
and turn into unsubmitted difficulties. This can happen to a random amount of difficulties per set.
I would say this whole problem started when I downloaded the Shigetora mappack from his Youtube channel and then started to delete all the maps from the 3 modes that I wasn't playing by searching mode=mania / mode=taiko and mode=catch and then using DELETE ALL VISIBLE BEATMAPS, which didn't work properly and since then this problem has existed.
Back then lazer was not installed on my device and the issue has been there even when I whiped lazer off my pc and downloaded it again.
I also noticed that the difficulties that became unsubmitted on stable are also unsubmitted on lazer, however not all unsubmitted ones on lazer also become unsubmitted on stable.
Furthermore when this happens on lazer, even if you select that difficulty and go into details lazer doesn't let you re-download the map so you have to do it over an actual browser and not the integrated one.
On top of that, if you use the browser do re-download the map for lazer there is a chance that it won't work the first time and the difficulty will still remain in the unsubmitted state. However if you just download it again and put it into lazer for the second time it has always worked. This has not happened on stable so far as I just downloaded the map, put it into stable and it was ranked again.
I have a video that shows that whole downloading issue but it's too big for Github and I don't know how to compress it down to 10MB.
Screenshots or videos
Stable:
Lazer:
Version
Stable: b20240820.1 Lazer: 2024.906.2-lazer
Logs
Lazer:
compressed-logs.zip
Stable:
1727428053.nauth.log
1725622016.nauth.log
1725999700.nauth.log
1726140282.nauth.log
1726143966.nauth.log
1726158552.nauth.log
1726225157.nauth.log
1726234226.nauth.log
1726234947.nauth.log
1726235251.nauth.log
1726236047.nauth.log
1726350880.nauth.log
1726352921.nauth.log
1726390238.nauth.log
1726396233.nauth.log
1726426054.nauth.log
1726426198.nauth.log
1726433806.nauth.log
1726434572.nauth.log
1726436809.nauth.log
1726439155.nauth.log
1726479953.nauth.log
1726494150.nauth.log
1726511068.nauth.log
1727038144.nauth.log
1727040404.nauth.log
1727041007.nauth.log
1727075820.nauth.log
1727075921.nauth.log
1727075946.nauth.log
1727076409.nauth.log
1727077469.nauth.log
1727078238.nauth.log
1727078402.nauth.log
1727089321.nauth.log
1727089413.nauth.log
1727163154.nauth.log
1727204455.nauth.log
1727204493.nauth.log
1727351414.nauth.log
1727366653.nauth.log
1727368610.nauth.log
1727419819.nauth.log
1727423264.nauth.log
1727427368.nauth.log
The text was updated successfully, but these errors were encountered: