Include clanChestTier in the clanChest section of the API about cr-api HOT 7 CLOSED

I do agree that the word Percent is deceptive. I think that renaming would be preferred. We can do what we did previously, which is to add the field and then make an announcement to remove the old param later?

from cr-api.

Percent being 1 or 100 is debatable — Perhaps it’s a matter of field name.

For example, if percent remains 1 without changing it to 100, in Python, I’d be able to:

cc = 1
print("{:.0%}".format(cc))

and get 100% as output. I am sure that other languages may have shortcuts like this also. When representing percentage with max as 100 instead of 1, bugs often appear because you need to keep on remember that certain fields are x100. Happens to me often that I either forgot to multiply by 100 or doing it multiple times. With this being 1 max I keep all the values and only format it at the output stage as a format.

Alternatively maybe rename field to something like clanChestCompletion which then you can convert to percent yourself?

from cr-api.

If you want to keep it at 1, the word Percent is very deceptive. Renaming it to Completion would be good but might break some other work out there

from cr-api.

Whatever you guys like, just let me know.
As for the tier, can someone create a list of tier thresholds?

from cr-api.

Thresholds are in the wiki as linked in the first line of the issue.

from cr-api.

@selfish you can use this: https://github.com/cr-api/cr-api-data/blob/master/dst/clan_chest.json

from cr-api.

Clan chest data dropped until further notice.

from cr-api.