0.4.5

v0.4.5

• solo mode: SCUT supports playing without a teammate via the solo
  config option
• cli: the cli now warns and prompts if you would like to upload an
  autosave when there is no save file for your part of the current turn
• config set bugfix: config set now updates the config file

0.4.4

v0.4.4

• automate release process
• documentation for users and developers in github README.md

v0.4.3

This release fixes a bug in the uploading of player's saves performed by the GUI.

The whole saves folder would be zipped and sent to dropbox instead of just the individual save file due to passing the wrong path to the 7zip command.

v0.4.2

This release fixes the auto updater url. Future versions have a much better chance of auto updating!

v0.4.1

SCUT version 0.4.1

Fixes for the new UI:

• uploads from the UI no longer crash due to parsing errors
• moves work off of the main thread so it doesn't trigger Task Manager's 'Task is not responding'
• loading indicator while uploads (and downloads) are running
• 7zip console window is suppressed, noticeable when uploading multiple saves
• new app identifier so the publisher shows as me 'drmason13' instead of just 'github'

v0.4.0

This is the first release to come with a Graphical User Interface and MSI installer!

Download the installer to install SCUT, no matter where you install it, it will be able to find your config in the same default location.

Running the app will load SCUT into your system tray on the bottom right hand side of your taskbar. Click the SCUT icon (it looks a lot like Strategic Command World at War's logo!) and a small interface will open showing the saves Scut has found that it thinks are ready to upload and download. This is exactly the same as running scut 0.3.0 without arguments.

To actually upload/download the checked saves, simply click Go.

A future release should add an option to the installer to have SCUT run on startup.

Future updates should be possible using an automatic updater, but this is still experimental.

v0.3.0

This version is the result of a fairly large code refactor. The behavior should feel familiar: it's still just a cli program.

The main difference is scut upload and scut download have been merged into a single command, simply running scut with no arguments will predict what needs uploading or downloading based on the files it can see.
If it looks like the turn could be finished, it will suggest uploading an autosave, you can decline the autosave but still upload a turn, which is useful for partial turns.

The turn is no longer read from the config file, any value currently there is simply ignored in 0.3.
You can still overwrite the predicted turn using the --turn flag e.g. scut --turn 4 will make scut upload and download saves for turn 4, even if scut thinks it is a different turn.

Scut downloads saves for the predicted turn and the previous turn that are missing from your saves folder, including partial turns.

Release v0.2.2

• Improved save parsing to accept extra space characters
• If you try to upload a next turn save without a teammate's save for that turn present you are no longer prompted for confirmation to upload the autosave because it wouldn't be uploaded anyway. Instead a warning is displayed advising to use --force if you want to upload the turn.

Release v0.2.1

• Bug fix: No longer offers to download previous turns that you already have downloaded
• Compile with MSVC toolchain from Windows instead of cross compiled using GNU from WSL2.

Release v0.2.0

• You can now upload saves in parts, simply add a name for your part at the end of the file name when saving. e.g. Axis DM 40B
  • All parts for the current turn are uploaded every time you run a normal upload.
  • Multiple parts from current and previous turns should be downloaded
• More save name formats are understood now, mainly so you can omit spaces, e.g. Allies 40DG, Allies DG1 and even alliesdm3 should all work now.
  • Note: There is an ambiguity with parts when not putting the turn number last; so Allies 40 DMpart2 will think that DMpart2 is the name of a player! It's best to put the turn number at the end of a normal save, and then add A, B, C or whatever you like at the end for the part.