* Patches to get 1.17 working, need to revise into real solutions.
* Add version.jar to cp until 1.17.
* Add server selection button to Java settings tab in preparation for by-instance java settings.
* Java settings by instance
* Use classpath flag instead of hardcode.
* Support 1.19.
* Fix refresh of java exec details.
* Add doc.
* Fix auto download of jdk 17.
* Dependency upgrade.
Fix bug with AdmZip by replacing it for the jdk extraction task. It will have to eventually be replaced for everything else.
Remove disclaimer about Oracle JDK, as it is no longer used.
* Update landing.js
This changes the Skin/Avatar server displayed on the landing page to one that displays the hat layer which then features the skin correctly.
* Create landing.js
This changes the Skin/Avatar server displayed on the landing page to one that displays the hat layer which then features the skin correctly.
* Updated remaining Crafatar URLS
Changed Crafatar URLS to matching mc-heads url.
Vendor name is now displayed above the selected Java version on the settings page. This is to allow for easier differentiation between versions (ex. Amazon Corretto vs AdoptOpenJDK).
Fixed issue with passing fullscreen argment to 1.13+, although it doesnt seem to be working well clientside.
Improved the forge version check logic.
Fixed launch area toggling and added a min linger time so that the transition doesnt look abrupt.
Upgraded dependencies.
Fixed file selectors not behaving properly due to breaking change in Electron 7 (#67).
Renamed shell.openItem to shell.openPath (Electron 9 breaking change).
Resolves#67.
Mojang has changed its manifest format for 1.13.
Forge is no longer a universal jar, it requires more hosted files, all of which are generated by the installer.
We can no longer extract the version manifest from forge's jar and have to include it in the distribution.
This commit adds support for launching forge only, mods are currently not supported from the distribution.
Handling of 1.13 launches are subject to change as we move forward.
If anything happens to the forked process, the main should now pick up on it and alert the user.
Should no longer get 'stuck at 100%' issues when the forked process fails, for whatever reason.
