Monday, November 14, 2016

Notice Regarding Loading Battles

To reduce resource usage and improve reliability, Clan Battle loading has been disabled for Clans determined not to be actively using any of the features related to Clan Battle loading.

To be clear, this is in reference to the battle lists shown on Clan Home > Battles, not the data shown on Clan Home > Clan Wars.

If your clan was incorrectly identified as not actively using Clan Battle loading, my apologies for the inconvenience. To correct this, your clan's Commander or any clan Admin on the site can turn Clan Battle Loading back on by going to Clan Home > Edit, checking "Enable Loading Battles", and then clicking Save. You can also Contact me and I can enable it again.

Sunday, October 9, 2016

Changelog for 2016-10-09

Changes

  • Added support for Sweden nation.
  • Removed reliance on Wargaming updating their API for Clan Tools to support newly added tanks (or tanks turned to HD).

Wednesday, June 15, 2016

[Ended] Maintenance Downtime - Starting at 2016-06-17 06:00 UTC

[Update] Maintenance has Ended

Maintenance downtime has now ended. If you are experiencing any issues, please contact me via one of the following:



Downtime Information

  • Downtime Start: 2016-06-17 02:00 Eastern Time (2016-06-17 06:00 UTC)
  • Estimated Downtime End: 2016-06-17 05:00 Eastern Time (2016-06-17 09:00 UTC)

Important Changes

API Token Invalidation

Due to a number of factors1, all API Tokens will be invalid after the Maintenance period. You can create a new API Token after downtime to replace the removed one. This issue should not arise again for tokens from the NA, EU, or ASIA regions.


My apologies for any inconvenience caused by this downtime and by the loss of usability for the existing API Tokens.


Other Changes

  • Fixed incorrect Members count on the Clan Tools - Clan Lookup when one or more members had played no battles (GitHub issue)
  • Improvements to Mobile viewing experience.



Footnotes

1 Wargaming's API has the concept of Application IDs, which it uses to identify the source of any request. The Server Application IDs Clan Tools uses are tied to the current IPs of the Clan Tools servers and I do not have the ability to change the IPs of the current Application IDs.

This is because, while Wargaming does offer the ability to manage Application IDs from their website, they require the given Account have a mobile phone linked to the account. At the time Clan Tools launched, I did not have a mobile phone and thus could not use the website (I instead emailed Wargaming developer support).

Further--importantly--the API Tokens are tied to Application IDs, so I can't use the existing tokens as Wargaming's API rejects them if I try to use the old tokens with the new Application ID.

I now have a mobile phone, and was successfully able to link it for NA, EU, and ASIA, and as such I will be able to change the IPs in the future (thus why I don't expect this to be an issue for those regions in the future). For RU, for whatever reason I am not receiving the text message confirmation code from Wargaming.

Finally, as to why the IP Address of the server is changing, this downtime is due to me moving Clan Tools to a new server, which requires a change in IP.

Saturday, March 12, 2016

9.14 Replay Upload Issues

Update 2016-03-12

This issue should now be fixed. If you're still experiencing issues, it would be very helpful if you could upload the replay to another site (e.g. http://wotreplays.com/) and send me a link (click for contact info).

Once again, apologies for any trouble this caused and thank you for your patience.

Original Post

I'm aware of the issue where attempting to upload certain 9.14 replays causes an Internal Server Error. My apologies for the trouble.

It is not an issue I can reproduce with Random battle replays, which are the only ones I have currently. If you're unable to upload a replay to the site, it would be very helpful if you could upload the replay to another site (e.g. http://wotreplays.com/) and send me a link (click for contact info).

Thank you for your patience.