You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
89219da contains an experimental first approach of filtering maps by game mode.
This allows searching specifically for OneSaber or 360° maps for example. However, this first implementation has flaws which is why it won't go into master right now: a) it's slow, b) it spams the BeatSaver API with hundreds of requests to find a few songs, since OneSaber maps are quite rare. This is not optimal and cannot be changed directly right now because of how the BeatSaver API works.
However, I could download a regularly updated scrape of the BeatSaver data regularly and perform the search locally on that copy. Daily updated scrapes are already available at https://github.com/andruzzzhka/BeatSaberScrappedData
The problem is that at the moment, the scraped data from BeatSaver doesn't contain the much needed characteristic infos which is where the game mode information lies. If andruzzzhka includes this information in the future, that would be the solution as long as the BeatSaver API is as it is. kinsi55/BeatSaberScrappedData#3
The text was updated successfully, but these errors were encountered:
Luux
changed the title
Filtering by GameMode
Filtering by GameMode (& don't spam BeatSaver)
May 22, 2020
For GameMode filtering, some algorithmic changes for ARBSMapDo have to be made. However, the cache is implemented now and should speed up ARBSMapDo significantly.
89219da contains an experimental first approach of filtering maps by game mode.
This allows searching specifically for OneSaber or 360° maps for example. However, this first implementation has flaws which is why it won't go into master right now: a) it's slow, b) it spams the BeatSaver API with hundreds of requests to find a few songs, since OneSaber maps are quite rare. This is not optimal and cannot be changed directly right now because of how the BeatSaver API works.
However, I could download a regularly updated scrape of the BeatSaver data regularly and perform the search locally on that copy. Daily updated scrapes are already available at https://github.com/andruzzzhka/BeatSaberScrappedData
The problem is that at the moment, the scraped data from BeatSaver doesn't contain the much needed characteristic infos which is where the game mode information lies. If andruzzzhka includes this information in the future, that would be the solution as long as the BeatSaver API is as it is.
kinsi55/BeatSaberScrappedData#3
The text was updated successfully, but these errors were encountered: