KAG Mod Manager 1.09

.cfg files are now hashed, except for ones in the folder /settings (including ones in nested settings directories), so you should use that folder for including server settings .cfg files, to allow server owners to modify settings without losing their verified status.

Also fixed bug with file extensions being case-sensitive .

Thanks to Aphelion for his assistance in tracking down the windows bug - was causing directory hashes to be calculated incorrectly, thus invalidating the whole server verification process (in some specific cases - was a weird thing to do with specific file path patterns).

Thanks to Diprog for reporting the other issue where the refresh button was still enabled during edit mode.

Biiiiiiiiiiiig thanks to @norill for this help in updating the API to use SHA512 (or more specifically, updating KAG so that it is able to use SHA512 so that it can use the API)!

Hashing algorithm has changed in the API, so this app needed to change too.

An unfortunate side effect of this is that everyone that had previously uploaded a mod package will have to do it again.

Nothing to see here, move along now.
(Nothing much changed, just some code cleanup)

This update removes the confusing finalised name stuff, fixes bugs, adds developer groups and includes a substantial re-write to make the code more manageable in the future.

Windows fixes (I hate these compatibility issues...) plus you can now set each of the 3 mod package types to be available only to devs if you so wish. For example, if you disable 'full' and 'server' but keep client enabled, then you can make it so that the client code is freely accessible but the server/full packages require developer authentication to download.

Added button for deleting selected mod

Previously it seemed that uploading failed 'cos of an oversight - a line of code that behaves differently when packaged as an .exe. I think I fixed it now.
Also, added the option to download the mods.