API Tokens
Due to coding error all existing API Tokens are no longer considered valid by WG's API. As such, you'll need to create a new API Token (https://clantools.us/account/settings/tokens) to replace any existing token. Sorry for the trouble.
Clan Lookup
Similar to the player lookup, there's now also a clan lookup. It still has room for improvement, however there's enough there already that I feel it's worth releasing. Accessable via the Tools dropdown, or just click here. For an effective summery, see the image below (click for larger version).
The Clan's Tank page has also been replaced by the combination of the tanks and performance tabs, though the tank list also includes a more detailed view of available tanks.
Known Available won't be very useful without having your members add an API Token on Clan Tools (https://clantools.us/account/settings/tokens) as it only shows confirmed in garage tanks (which requires an API token from that user to get their in garage status) and which are unlocked. Possibly Available is effectively the same as what was shown as available before as it shows unlocked tanks that are known to be "in garage", or that there is no in garage data for. Available Maximum shows what is effectively the same as "count" on the clan lookup page, and is effectively just a simple count of every member for which that tank was reported by the WG API.
Everything isn't objectively better though, as everything (except in garage and tank locking) is retrieved from the WG API each time. Previously the Clan Tools server loaded this data once a day and served the statistical information that way. This was extremely costly. For the 1,764 users with stats being tracked, there are 786,868 database entries for stats alone. Though the bigger issue was the time it took to load this data, which was around 30 minutes (for 8 clans). This simply wasn't scalable, nor an effective use of the limited resources available to Clan Tools. As such, while I understand the longer waiting times are less than ideal, they are a necessity.
In Garage Data
In Garage data now correctly reflects if the data isn't available (due to the lack of an API token for the user).
Player's Tanks Page
The player's tank page now sources its data from the Wargaming API, rather than pulling stats from Clan Tools. The In Garage and Tank Locking data is still provided by Clan Tools, so no information has been lost.
Clan Home Dropdown Nav Changes
I've added a link to matches and removed the link to payouts on the clan home nav dropdown. My personal view is that the nav dropdown should have links to pages which are likely to be used at least one a day; payouts is more a once a week sort of thing. On the other hand, matches (if used) is something which is likely to see daily use.
Other Changes
- Added Average Tier to player lookup.
- Missing WN8 expected values are now calculated using the formula listed here: http://forum.wotlabs.net/index.php?/topic/9786-wn8-expected-values-update/?p=299540 Note that this relies on the tank entry being reported by the WG API, so there still may be missing tank WN8's at times.
- Updated Player Lookup footer to reflect WN8 expected tank values table source.
- Player lookup lists now have smarting sorting behavior (stats default to descending order when first sorted).
- Removed not Once Per a Day restriction on code types granted via replays.
- Updated Create Token page to take into account changes to how WG deal with tokens.
Fixes
- Player lookup tank list having no default sorting.
- Codes automatically created by creating a new match now use the correct date based on the for date.
- Adding a replay to an existing match failing due to a missing link in information propagation.
- Issues caused by tanks missing from clan tools, but not the WG API.
- API Tokens not being sent when mass refreshing clan member data.
- Error when attempting to filter by in garage.
Note: Some might have noticed that this post seems a day or two late; for various reasons this didn't end up getting posted until today.
No comments:
Post a Comment