Version 2.1.5

This critical bugfix release contains an updated parser which has better support for Heroes of the Storm 2.0, in addition to not completely crashing the replay handling on failure.

Issues fixed

#157 - StormParser bypassed fallbacks and did not support Heroes 2.0

Version 2.1.4

This bugfix release fixes the Battle Lobby for macOS after Blizzard changed their temporary file locations. It also tunes the My Documents detection on Windows systems.

Issues fixed

#148 - Documents folders were not detected if the user had a dash in any folder
#154 - Battle Lobby did not display on macOS

Version 2.1.3

This bugfix release reenables Brawl uploads, as they are now supported by Hotslogs. It also fixes an issue with the .jar file generation.

Issues fixed

#138 - Brawls were being held back from upload, but Hotslogs now supports it.
#143 - Uber-jars were not properly generated

Version 2.1.2

This bugfix release fixes issues with Windows drive labels, and with uploading Brawl replays.

Issues fixed

#136 - Windows allows lower case drive labels, but the app does not.
#138 - Brawls are uploaded even though Hotslogs.com doesn't support it.

Where's the .jar file?

We're having an issue with Spring Boot and "uber jars". This is typically resolved using a special Spring Boot plugin, but this seems to be incompatible with the JavaFX Maven Plugin we use for native bundles.

Version 2.1.1

This bugfix release fixes the issue with invalid version numbers that causes the application to think there's an available update while you're still running the latest version

Issues fixed

#130 - Application version can be not semantic number version compliant.

Version 2.1.0

This feature release brings a Battle Lobby feature that allows users to get a preview of the currently active match in the app. It also displays a link to display more detailed information on HotsLogs.com

New features

#118 - The account list now automatically selects the account with the most recently played match - thanks @rogusdev!
#127 - The application now halts uploading and display match information when in a match
#126/UNTRACKED - The code base has been massively overhauled to use a Spring context instead of Guice. We've also modularized the application views.

Version 2.0.5

This is the final bugfix release for the 2.0 branch of the application. Development is now shifting fully to the next feature release, in lieu of critical issues that arise.

Issues fixed

#113 - If replays were deleted while queued for upload and the application was running, the application would break down
#115 - Removed replays were not deleted from the database on startup
#119 - An update to the HotsLogs hero model broke our hero list - this has been resolved.

What happened to 2.0.4?

While fixing #115, we introduced a pretty critical bug that would've deleted our tracking state for all your replays on every restart if you had multiple accounts. This wasn't discovered until we had finished preparing to release 2.0.4 and were doing final testing. Therefore, the release was skipped.

Version 2.0.3

This is the release of version 2.0.3. This bugfix release fixes two issues related to replay folder locations and failed uploads that later succeeded not being saved properly.

Issues fixed

• #107 Previously failed uploads were not tagged as successful uploads after they did succeed.
• #108 Windows user with dots(.) in their username could not use the application

Version 2.0.2

This is the release of version 2.0.2. This bugfix release fixes an issue, which was introduced by 2.0.1 causing an abnormal amount of "uploaded replays" to appear.

Issues fixed

• #96 Replay files were duplicated, if multiple accounts and / or multiple regions were used on a single machine

Version 2.0.1

This is the release of version 2.0.1 This bugfix release fixes issues related to the new way we save statuses.

Issues fixed

• #80/#81 - 2.0.0 did not start on some systems due to an improper uniqueness check for files.
• #92 - Crash on start if replay files were deleted.
• #93 - Some file states were not persisted properly and required a double pass through the uploader. Files were however only actually uploaded once.
• UNTAGGED - Fixed an issue where using both the jar and native package would flag the database as corrupted.