gorilla-devs/GDLauncher

Modpacks utilizing Neoforge installer start a vanilla instance instead of modpack

TGurl opened this issue · 4 comments

TGurl commented
  • I searched the issue tracker for other issues covering my case
  • This is a Launcher issue. (Usually if you can reproduce it with a fresh instance)

Describe the bug
Modpacks using the NeoForge modloader do not work. For example FTB presents Direwolf20 1.20 does not work out of the box as they utilize the neoForge 1.20.1-47.1.79 installer

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Add a new instance -> FTB -> select FTB presents Direwolf20 1.20 '
  2. Click on 'start' after installation is finished
  3. A vanilla version of Minecraft 1.20.1 will start instead of the modpack

Expected behavior
The launcher installs the mods using the NeoForge installer.

Possible solutions
Implement the Neoforge installer next to Forge.

Screenshots
None

Operating System:

  • OS: Arch Linux, kernel 6.1.55-1-lts
  • Launcher Version: v1.1.30
  • Java Version: 17.0.8.1
  • Minecraft Version: 1.20.1
  • Mod Loader: NeoForge 1.20.1-47.1.79

Additional context
The modpack does work with a workaround:

  1. Create a new instance using Forge
  2. Copy over all necessary folders/files from the FTB instance to the newly created one
  3. Start the new instance.

More information about Neoforge: https://neoforged.net/.

steffenlindemann commented

I have the same issue. Also with the direwolf 20 1.20 ftb pack.

Eskaan commented

Sadly, we no longer support FTB. They have asked us to remove the support (and in the dev version it already is). They also changed their API so it's no longer possible to use the old support.

TGurl commented

Understandable when talking about FTB. The only thing is some mods (and maybe later other modpacks) are already moving to Neoforge. Maybe it's still important to check this as it's very likely Neoforge and Forge won't be compatible in the future. Just a thought.

Normal69 commented

Understandable when talking about FTB. The only thing is some mods (and maybe later other modpacks) are already moving to Neoforge. Maybe it's still important to check this as it's very likely Neoforge and Forge won't be compatible in the future. Just a thought.

Indeed I am now trying to download the non-neoforge mods with no choice over the matter.