Release v1.6.0 - Forge 1.13 Support, Failed to Verify Username Fixed
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 tocommon/versions/{forge-version}/{forge-version}.json
VersionJar
. This is forge's patched version jar. The file is stored tocommon/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.