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

Not able to populate.... #75

Open
Dolward opened this issue Dec 7, 2022 · 4 comments
Open

Not able to populate.... #75

Dolward opened this issue Dec 7, 2022 · 4 comments

Comments

@Dolward
Copy link

Dolward commented Dec 7, 2022

I dont know what the problem is here.. It all worked yesterday.
When I try to populate.. I get this message.
image

These are the settings that I've set for the sheet.
image

@conetopia
Copy link

You can only do like 64-68 Results.
Your Guild size is 141 characters
About Half your Guild is level 70
which means your trying to display 69-72 players ( Soon to be more as they level up to 70 )

I would extremely suggest Change your Max Rank from a 10 to maybe a 9 or even an 8.
This would make it so the lowest Ranking Guildy's don't show up.
You can always Whitelist / Blacklist members if needed.

Alternative , you could ask 2 or 3 friends or make 2 or 3 extra google accounts, and make multiple spread sheets.
level 1-50 , 50-69, then like 70 Rank 10-5 , then 70 Rank 4-0 .

Another alternative there is some google premium options, i think the cheapest was like 5 or 8 bucks a month, and that would allow you like another 200 Character displays.

@conetopia
Copy link

Update , Since Dragon Flight & the way things are searched.
We can now only do about 63 Characters.

@inabohx
Copy link

inabohx commented Mar 9, 2023

Something else is going on and not just character count. I'll have this sheet closed for days, not published nor shared, manually killing integrations like WCL and Raider IO... and I'll open it up and be immediately greeted by a sheet full of service-invoked-too-many-times errors.

I've gone through the scripting a little, but not in-depth yet. Has anyone else run into that?

@brewk
Copy link
Owner

brewk commented Mar 10, 2023

This has been a huge issue since Blizz reworked the API a few years ago, and there is a lot of evidence that there is no way to prevent google from updating your sheets, even when they're closed. What this also means is.. if you have ANY old sheets on your account, they're also updating themselves. Make sure you entirely purge any old sheets from your docs account. I'd go as far as deleting any characters in those sheets as well before trashing them, just to make sure.

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

4 participants