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).

Changelog for 2015-12-22

Fixes

• Added Czech to Nation filter dropdown.
• Switched to new API method for loading tank data since WG is discontinuing the one previously used. Hopefully no more tank names like Cz05 T34 100 short though.
• Added workaround for bug in new WG API release.
• Updated to WN8 expected values v25

Changelog for 2015-12-05

Fixes

• Fixed Battle Loading time zones not encompassing the latest possible battle in the same day. The time zones used now for each server for determining what day a Battle is on are:
  • NA UTC-10:00
  • EU UTC-04:00
  • ASIA UTC+04:00
  These time zones are fixed offsets and are no longer related to the Server Time Zones used where other server specific time zones are used.
• Fixed the current date for the Battles list using the user's specified time zone rather than the Battle time zone, causing inconsistencies.

Changelog for 2015-10-29

Fixes

• Fixed Internal Server Error when attempting to create a new Match for a Match Type with "One Battle Per a Match" enabled, "Require Replay" disabled, and not selecting a replay to upload to the new Match.
• Fixed Clan Lookup error when, typically due to filtering, one or more players have only a single tank matching the filters for which there is no expected tank values for WN8 (for newly added tanks).

Changelog for 2015-10-16

Fixed

• Fixed Payout calculator forgetting notes set via the Modify link on recalculation.
• Fixed Internal Server Error when entering values which are too large in some Payout fields (now a helpful error message is shown).

Changelog for 2015-09-26 (Hotfix)

Fixes

• Fixed updated library causing internal server errors in certain cases.

Changelog for 2015-09-26

Changes

• Added section to WoTManager translation guide about Import functionality.
• Removed ability for clans to manually reload members. Clan member changes are automatically loaded each hour, and whenever a clan member signs into the site, their clan data is automatically updated. There's no need to have this, and it can lead to race conditions (for join/leave events).
• Added a minimum combination check to Code Types, to prevent a random choices and random length combination that gives a very low number of combinations (because this can cause code creation to fail due to not enough combinations).
• Added Note of when automatic code creation occurs to the Code Settings tab.
• Added Delete link on Codes lists.
• Added slight fade to Code Action links on Attendance and Valid Public Codes pages.
• When creating a new Match Type, One Battle per Match now defaults to true as this setting produces more logical results, especially when paired with setting (or having it auto-determined via a replay) the Result for a Match.
• Added better error page for timeouts.
• Added better error page for Security Violations typically caused by having more than one tab open editing an item.
• Added better error page for File Not Found (for replay downloading).

Fixes

• Added check to hopefully prevent issues with duplicate join events and a single (invalid) leave event because created, seemingly due to short-term mismatches in data returned by different WG API methods.
• Fixed Twitter widget not loading due to CSP conflicts with changes to the way Twitter loads the widget.
• View code checking show (details) instead of edit permission for codes listing. Note this was purely an error in the client side display code and had no impact on security.
• Fixed attempting to use a lowercase Prefix that has already been taken causing an internal server error.
• Moved Features/Help images to Clan Tools (instead of using Imgur).

Backend Changes

• Removed unused libraries.
• Updated various libraries.
• Increased maximum concurrent request handlers.

Also, Friday morning I finished setting up the second server. However, there was a small but noticeable increase in latency (the actual delay appears to vary based on the size of the data returned). This is the expected result, due to the database connection now being remote which adds network latency, plus the (temporal) cost of encryption for that connection.

As such, given that the current server--once I fixed the backend scheduler clobbering it--appears to be more than capable of supporting the current load, I see no reason to degrade performance just because.

Images

Due to reports of Imgur being compromised (which I used to host the images on the site, for the features/help sections), I've temporarily disabled images. I think I will host them on the Clan Tools server to avoid future issues such as this.

Changelog for 2015-09-16

Changes

• Re-enabled WoTcs.com clan history views since they appear to be working again.
• Added exception for replay uploads to (hopefully) work around an issue related to Wine.

Fixes

• Fixed WoTLabs signature on Player Lookup using incorrect server name, resulting in the signatures displayed being for NA players of equal names.
• On Player Lookup, fixed no Tier Header being visible in Clan Wars Tanks if a tier section only had close to tanks.

Changelog for 2015-09-12

Changes

• Added Import feature for WoTManager exported attendance data (Clan Home > Import).

Fixes

• Fixed Internal Server Error when trying to view the forum of a clan which doesn't exist in the system.
• Fixed incorrect warning when creating new Subforums.
• Fixed Events display. Now, only events directly regarding the clan should be displayed, be those join or leave events for clan members (to or from your clan, not any other clans). Additionally, current member name changes will also be displayed.

Changelog for 2015-09-11

New Code Type Options

There are several new code type options, two of the most interesting ones are designed to address the same request from clans in two different ways.

Make Valid Codes Public [public as in visible to all clan members]

This, as the name suggests, make all valid codes of that Code Type available to be seen by all clan members by visiting a specific page on Clan Tools. You can get to this page from the Attendance page (Clan Home > Attendance > Valid Public Codes) or Code page (Clan Home > Codes > Valid Public Codes).

Available on the Code Settings tab.

Auto Create Forward

This setting on the other hand allows having auto-creation of codes beyond the current day, up to 7 days. This makes it easy to copy a week's worth of codes for listing someplace else.

Available on the Code Settings tab.

The Other New Options

• Auto-Create Start Time Day Offset and Auto-Create End Time Day Offset - These settings allow the auto-created codes to have start and end dates greater than one day.
• Auto-Create Loose Duplicate Prevention - This setting reduces what it takes to prevent a code from being auto-created from having to have the exact same code type, for date, and from and to datetimes (down to the nanosecond) to just the same code type and for date. This setting, in general, deals with edge cases, so you probably don't need to worry about it. This is enabled by default for new code types; existing code types have it disabled to match prior behavior.

The above three settings are available on the Advanced Settings tab.

Other Changes

• Related to the above, the Valid Codes list on the Attendance page now only displays codes that are valid or will be in 12 hours or less, to prevent having 7 days of future codes from showing up.
• Added notice to Player and Clan Lookups regarding WoTcs.com no longer working, which Clan Tools used for member change history. I am exploring other options, no promises for the moment.
• For Player and Clan lookup, the localization is now forced to english for all servers.
• Added Total footer for Clan Tanks Lists and clan Player Stronghold Stats.
• Improved warning message for Clan Lookup when members have accounts which WG API's doesn't treat as existing.
• Take advantage of the clan members list on the WG API knowing about players to display all players, even those who other parts of the API don't treat as existing.

Fixes

• Fixed an issue where users would be redirected to an invalid page in some cases.
• Fixed checkboxes on clan members list being displayed pointlessly in some cases.
• Fixed "X members accounts are locked" warning being duplicated when changing filters.

Changelog for 2015-09-09

Changes

• Removed restriction on Away Entry: From field requiring it be set to the current date or later for clan administrators.
• Removed restriction on deleting Away Entries for clan administrators.

Fixes

• Fixed internal server error when attempting to save an away entry just providing an end date.
• Fixed invalid back handling in requests from external sources.

Changelog for 2015-09-07

Changes

• On a User's profile page (e.g. mine), the user's clan will always be displayed, regardless of if they are a member of a participaing clan. If they aren't, the WG API is used to load clan information.
• Changed the format of the User's clan details to match what is shown on the User Lookup.
• Added Features page to give an overview of key Clan Tools features.
• Added support for clans from ASIA server.
• Added UTC Offset to Time, Date, and DateTime fields (e.g. Berlin (UTC+02:00) ).
• Added new guide to help documentation: Transitioning from WoTManager

Fixes

• Fixed display issues on the Activity Report Members List.

Changelog 2015-09-04

Negative Industrial Resource Values (is fixed)

Because WG doesn't remember a user's IR data when they leave their clan, and Clan Tools does, a negative value would be reported whenever a player left a clan then rejoined it. Clan Tools now checks the player's join date to detect when this has occured and record the correct delta.

Existing negative IR has also been corrected. If you notice any issues, please contact me: https://clantools.us/contact

Another issue was also fixed, which was Clan Tools for any new member would ignore any IR gained in the first day with the clan.

In Garage (is gone)

To be clear, this has no real impact. The interface is a bit cleaner in a few places (known available, which was often zero, is gone and any display of in garage is gone). Tank Locking data will still work as per usual.

As to why? It was unused. In large part because Wargaming requiring an API token from the individual player to access in garage data, every player in a clan would need to provide an API token to Clan Tools. Possible, but it hadn't happened yet.

I've also optimized the clan refreshing method to require one less API request per a clan and reduce the amount of data transmitted.

Timeout Errors

Intermittent timeout errors was an issue that would spring up every once in a while and didn't make much sense to me when I had looked into it previously. However, I recently had a realization and I believe I've fixed the issue, which appeared to be caused by requests that got stuck waiting due to high server load.

Server Load

On the topic of server load, I've also reduced the maximum number of simulations requests which can be served. This may seem to be a negative, however I suspect that the grinding to a halt of the entire site encountered a few sundays prior was caused by very high server load which pushed memory usage beyond the amount of available RAM and into the swap file (which slowed everything down). My monitoring indicates that most of the instances were rarely used anyway, so I don't expect this to be noticeable the vast majority of the time either way.

Feedback on this is welcome though; do you notice a change during times of high load?

Changelog for 2015-08-27

Clan Lookup Changes

• Added Ceasefire Day, Neutrality, and Stronghold Tier information to Stronghold tab.
• Added industrial resources earned per week and total to Stronghold Player Stats tab.
• Removed industrial resources gained/lost displayed (WG pulled it from the publicly available information).
• Fixed win rates on Stronghold Player Stats tab not being colored correctly.

Other Changes

• Added Primary Group to Activity and Stronghold player lists.

Fixes

• Fixed attempting to use an older version payout as a template failing if the payout referenced a deleted Code Type.

Known Issues

• At times, some Pay Groups are listed more than once in the selection drop downs; this shouldn't cause any issues, it's just annoying.
• If a player leaves the clan then rejoins at a later time, the Stronghold IR tracker will give them negative IR deltas because WG clears their total IR earned when they leave, but Clan Tools doesn't. This is the next thing on the todo list.

Changelog for 2015-08-18

Fixes

• Fixed possibility to save a Payout Reward Rule without a Pay Group set in some cases.
• Fixed attempting to change the Pay Group for a Payout Reward Rule that exists causing an Internal Server Error.
• Fixed Clan Home > Events not displaying player name changes for clan members.
• Fixed unexpected errors in payout calculation causing Payouts to be stuck in a state of "calculating".
• Fixed possible error when attempting to save a payout with duplicate Code or Group reward rules.

Changelog for 2015-08-12

Fixes

• Fixed error when attempting to view Player Lookup > Graphs > Modes in some cases.
• Fixed possibility of highlighting getting stuck on Player Lookup > Clan Wars Tanks
• Fixed Researched jump-to buttons not working when a player had no researched non-star tanks. Now Researched highlights all researched tanks, stared and unstared alike.

Slack Battle Integration Changes/Fixes

• Fixed battle list slack integration not correctly displaying enemy clans whose names were surrounded by underscores.
• Stopped fetching CW1.0 battles.
• Added support for -tz [timezone name or numeric offset] flag to override timezone set on a per-a-request basis.
• Fixed "R" being displayed without number when there was not yet any round defined for a battle on the CW2.0 map.

What slack integration you (maybe) ask?

How do I use this?

1. Create a new outgoing slack intrigration from: https://my.slack.com/services/new/outgoing-webhook
2. For the URL enter:
   https://sv.clantools.us/integrations/battles/report?provider=na&tz=et&service=slack&clan_id=
   
   adding your clan ID to the end (numbers that show up in the end of the URL when you go to https://na.wargaming.net/clans (you have to be signed in to the Wargaming clan website).
   
   For example, Otter's would be:
   https://sv.clantools.us/integrations/battles/report?provider=na&tz=et&service=slack&clan_id=1000008386

You can also change the part of the URL that says tz=et to any of the following, or a whole number representing the timezone offset:

• PT
• MT
• CT
• ET
• UTC

Finally, for clans from other servers, where it says provider=na, change NA to EU, RU, ASIA, or KR respectively.

Also, if you are already using the slack integration and your URL starts with https://clantools.us, please change that to https://sv.clantools.us

Changelog for 2015-08-10 (2)

Fixes

• Fixed internal server error when creating/updating a payout without specifying a to or from date.

Changelog for 2015-08-10

End of an Era

Clan Wars 1.0 is effectively no more with the NA server being the last to freeze the 1.0 map.

With this in mind, the following changes have been made:

• Stopped checking for new CW1.0 battles.
• CW1.0 battles are marked as such with CW1.
• CW2.0 battles are no longer marked as such with CW2.
• Stopped loading Clan Wars Globe/Province/Region data.
• Disabled Global Map viewer on all servers as no servers have CW1.0 anymore.

CW1.0 settings in Payouts will remain for some time; however, they too will eventually be removed.

Changelog for 2015-08-06

Code Granting/Revoking Changes

Note: All of these changes only apply to the new method of granting/revoking codes, via the Members list on the Clan Home, Clan Members, or Clan Attendance pages, or via the Grant/Revoke button on the Clan Attendance page.

• Added restricted grant permission, that only allows granting codes that are currently valid (within the time limit); it can be noted that this permission is pointless if the user can create new codes, or edit existing ones.
• Fixed requiring both the ability to Grant and Revoke codes for the Grant/Revoke code option to be present.
• Fixed permissions not correctly inferring; each level of grant now implies the previous levels.
• Fixed Day being required for Granting/Revoking by Code.
• Fixed given Day being used regardless of what day the given code was for when Granting by Code, which resulted in odd behavior when the two didn't match.

All groups with Grant or Grant (Advanced) permissions have automatically been granted this new permission.

New Clan Wars Tanks / Close To List

Legend:

• Star - Popular Clan Wars Tanks
• R - Researched Tanks (including "Star" tanks)
• C - Close to being Researched Tanks (has the preceding tank).

Other Changes to Clan Wars Tanks lists:

• Added Tier 8 and 6.
• Added Stats Overview for all tanks of that tier 10 (pub stats).
• Fixed Closed To behaving oddly or incorrectly in some cases.
• Updated data for closed to; also data is now pulled from the WG API to remove the issue of it never being updated.

Codes List Changes

Two new filtering options have been added, both set by default, to cut down on clutter.

Has Code?

If the code is listed as N/A (and you don't for whatever reason have N, A, and / as code options), then the given Code doesn't have a 'code' that can be used to refer to that code. Otherwise, the Code has a code. Generally there are two reasons a Code won't have a code:

• The code's valid to date is older than a week; the system automatically reclaims old codes to avoid running into code exhaustion issues (where the number of possible code combinations which aren't in use by the clan run low).
• The code was created by the system with express intent of it never being submittable (as in, it didn't need a code that users can enter).

System Created?

The system creates codes for various reasons; granting linked codes, granting codes from replays, etc... Whenever a code is needed by the system and doesn't need to be submittable (as in, doesn't need a code that users can enter), it is created as system created.

Keep in mind, this doesn't refer to codes automatically created daily. Codes that are "system created" can never be entered.

In either of the above cases, generally, you don't care about seeing those codes, so now they are hidden by default.