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

/get_beatmaps get "next 500" #274

Open
varn88 opened this issue Aug 25, 2019 · 2 comments
Open

/get_beatmaps get "next 500" #274

varn88 opened this issue Aug 25, 2019 · 2 comments

Comments

@varn88
Copy link

varn88 commented Aug 25, 2019

Hey,
after sending a request that would have more than 500 results I get the first 500, is there a way to send a new request to get the remainder of the results, instead of getting the first 500 again?

I started working on a little database for (mania) maps, which I could sort by number of favs, and pick up some good maps I don't yet have. But for this I'd have to get all beatmaps first.

It would be convenient if I could send a request to send me the hits from number 501-1000 next and so on. or if the batch of 500 results could be considered a 'page' and I could send a request to tell me how many hits or pages are there for my filter, and then request for the hits on page 'X'.

edit: rephrased the question to make it easier to understand

@tybug
Copy link
Member

tybug commented Aug 25, 2019

Use the since parameter - start at the earliest date, look at the latest date on the page of 500, and use that as your next since param. Loop until all beatmaps are retrieved.

Related: #193

@varn88
Copy link
Author

varn88 commented Aug 26, 2019

according to the wiki, since only returns ranked and loved maps, but my main target would be graveyarded hidden gems here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants