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

Level API does not load #8

Closed
HGStyle opened this issue Jul 25, 2023 · 4 comments
Closed

Level API does not load #8

HGStyle opened this issue Jul 25, 2023 · 4 comments

Comments

@HGStyle
Copy link

HGStyle commented Jul 25, 2023

Here is the URL I tried:
https://history.geometrydash.eu/api/v1/level/128/brief
I opened it in my browser (Brave) but it does not load.
When requesting a level that never existed, it returns a weird result.
For example, for the API, ID 0 returns ReTraY:
https://history.geometrydash.eu/api/v1/level/0/brief/
Returns:
{"online_id": 0, "comment": "", "is_deleted": true, "cache_level_name": "ReTraY", "cache_submitted": "2018-04-22T00:00:00Z", "cache_submitted_timestamp": 1524355200, "cache_downloads": 20976497, "cache_likes": 3102391, "cache_rating_sum": 10, "cache_rating": 10, "cache_demon": false, "cache_auto": false, "cache_demon_type": 0, "cache_stars": 2, "cache_username": "DiMaViKuLov26", "cache_level_string_available": false, "cache_user_id": 4993756, "cache_daily_id": 0, "cache_needs_updating": true, "cache_available_versions": 0, "cache_search_available": false, "cache_main_difficulty": 1, "cache_max_stars": 5, "cache_filter_difficulty": 2, "cache_length": 3, "cache_featured": 7730, "cache_max_featured": 23802, "cache_epic": 0, "cache_max_epic": 1, "cache_two_player": false, "cache_max_two_player": false, "cache_original": 0, "cache_max_original": 0, "cache_needs_revalidation": false, "level_string_count": 0}
For the API, the level has been deleted since while we all know it's not...
Could you fix it please ?
Thanks you ! (for now I'll have to use requests and bs4 to extract level data I think...)

@Cvolton
Copy link
Owner

Cvolton commented Jul 26, 2023

This is very likely caused by the amount of records 128 has, for which 128 is a very big edge case. Level 0 returns the same result on the actual website as well, so that is intended behavior (records for levels below 91 usually aren't manually cleared, as they are hidden from search)

The fundamental bug here is the same as #5 , except that issue is about the website itself

@Cvolton
Copy link
Owner

Cvolton commented Jul 29, 2023

updated so 128 loads, although it's still much slower than it should be

@HGStyle
Copy link
Author

HGStyle commented Aug 20, 2023 via email

@Cvolton
Copy link
Owner

Cvolton commented Mar 22, 2024

more or less addressed in 7b03c89

@Cvolton Cvolton closed this as completed Mar 22, 2024
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