-
Notifications
You must be signed in to change notification settings - Fork 18
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
Received HTTP 422 from booru: 'PostQuery::TagLimitError' #87
Comments
Using https://github.com/AtoraSuunva/booru/blob/master/src/boorus/Booru.ts#L166= I could add a |
Sounds like a good solution to create a minor update But doesn't danbooru support random? It always worked with a large number of tags and randomly before, the problem arose only on these tags, which was shocking for me, so i'm here |
So is this gonna be a thing or not? |
@Hatsune-Mikun danbooru does support Danbooru also does not let you search using more than 2 tags unless you have a paid account @Skitteyy I was planning to add it in to the rewrite of booru, but I've been busy updating my other code first If you have a use for this right now I can try adding it in |
I take a big break on programming because depression, so you can make it when it gonna be comfortable for you, and i just update it after, i will use you library anyway |
Ah I see. No worries |
Well I don't know if anything will happen but I use booru for my discord bot and I found out that you can put a limit of 100 when you search with 2 tags and then put something like Seems to also error sometimes when searching with only one tag |
@Skitteyy You're probably searching tags that have less than 100 results, which then makes You'll need to generate a random number based on the number of search results: const random = Math.floor(Math.random() * post.images.length)
const image = post.images[random] |
I see, works perfectly, thanks |
Hello! It's me, again c:
I got this error while trying to get 1 post from danbooru with tags:
angel, white_hair, rating:safe
I guess isn't your issue, is it API, but anyway, can you recommend something or do with this?
The text was updated successfully, but these errors were encountered: