To remedy this, you may copy the contents of the old launcher profiles file to the new one (more specifically, the "profiles" section of the file) to move your existing profiles to the new launcher. Sidenote: Because the launcher profiles file is separate for the old launcher and the new launcher, the existing profiles in the old launcher will not be visible in the new launcher, and vice-versa. Until this process is completed, we suggest following the workarounds suggested about. This is the problem reported in this issue, and can be worked around by copying the new launcher_profiles_microsoft_store.json file to launcher_profiles.json in the same directory, and running the installer again.Ī fix has been committed (see 5d8bc95) to the Installer code, and the team is actively working to retroactively fixing all previous installers as well.
If the launcher_profiles.json is not present, then installation will fail early on due to a check in for the presence of said file. However, in this case the installation of Forge as a game version still succeeds, which means you can create a new profile/game installation and manually select the Forge version in the dropdown menu. The installer is programmed to installed the automatically generated Forge profile/game installation in the launcher_profiles.json file, which means if the file is present, installation will succeed but the newly (re)generated profile/game installation will only be visible in the old launcher.
There are currently two issues due to the new launcher storing its profiles in a new launcher_profiles_microsoft_store.json file:
0 kommentar(er)
