Skip to content

Releases: WesterosCraft/ElectronLauncher

v1.8.0

11 Oct 21:11
@jacobgranberry jacobgranberry
v1.8.0
2e864af
Compare
Choose a tag to compare
v1.8.0 Latest
Latest

Merges in several fixes from forked master dscalzi/HeliosLauncher

Assets 10

v1.7.0

04 May 18:24
@jacobgranberry jacobgranberry
v1.7.0
684e860
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.7.0

This release merges in several commits from HeliosLauncher and fixes the automatic Java download validation.

Assets 7

Release v1.6.0

28 Apr 15:21
@mikeprimm mikeprimm
v1.6.0
e08c3a9
This commit was signed with the committer’s verified signature.
dscalzi Daniel Scalzi
GPG key ID: D18EA3FB4B142A57
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v1.6.0

This release adds support for Forge 1.13 Beta. Forge is no longer a single jar file, and the version manifest formats have changed. There is also a new system for maven-style mod loading. As a result, the following had to be done:

Added new argument parser to prepare arguments provided in both the vanilla and forge version manifest.
Added two new distribution types.
VersionManifest. This is forge's version manifest. In 1.12 and below, this was extracted from the universal jar. Now, this file is only present in the installer. As a result it must now be hosted. The file is stored to common/versions/{forge-version}/{forge-version}.json
VersionJar. This is forge's patched version jar. The file is stored to common/versions/{forge-version}/{forge-version}.jar
Several more Forge files need to be hosted since it is no longer a single universal jar. These files are generated by the installer. An example is provided in repo's sample distribution.json. Files can be identified here.
Forge 1.13 has a new feature replacing --modListFile. These are --fml.mavenRoots and --fml.mods. All 1.13 configurations now make use of this to load mods.
Failed to verify username is finally fixed. The issue was caused when users has fullscreen enabled. The fullscreen argument was not properly passed to the game and therefore overrided whichever argument came directly after it. That argument was --username, hence the name of the issue. Along with fixing this issue, we reorganzed the launcha arguments to be more coherent and in-line with the vanilla launcher.

Features
81367bc Support for launching Forge 1.13.2 Beta.
e08c3a9 Support for Forge 1.13.2's replacement of --modListFile.
Changes
c834ca9 Reorder the launch arguments to be more organized, predictable, and in line with the vanilla launcher.
Fixes
c834ca9 Fixed application of the --fullscreen argument to not block other arguments. In particular, this used to block --username from being registered, resulting in the infamous issue failed to verify username. That will no longer happen.
Dependency Upgrades
6b96770 Fresh Installation
async@3.0.1-0
e8e7f85
electron@4.0.5
eslint@5.14.0

Assets 10