Skip to content

Conversation

@Trial97
Copy link
Member

@Trial97 Trial97 commented Oct 3, 2025

should fix PrismLauncher/issues/4190

It removes the hard dependency on cpw.mods.modlauncher.Launcher
And tries to dynamically load multiple classes that are know:

  • cpw.mods.modlauncher.Launcher for forge and old neoforge versions
  • net.neoforged.fml.loading.FMLLoader for newer neoforge versions

The reason why I got multiple library checks is that there is no guarantee for forge and neoforge to share the same libraries.
The library choice was made by taking into consideration neoforge maintainers' input:https://discord.com/channels/313125603924639766/922237746460893234/1423759561596342454
The cpw.mods.modlauncher.ClassTransformer used in #8 will be moved at some point soon.

This change was not endorsed by the neoforge team as the correct implementation of this would be to just pass the libraries folder to the forgewrapper from the launcher. But that would require a new launcher release.

Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Copy link
Member

@TheKodeToad TheKodeToad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really tempted to point out the error message duplication >:(
but that's a nitpick

@TheKodeToad TheKodeToad merged commit f56fd33 into PrismLauncher:master Oct 4, 2025
1 check passed
@KThompson-Lane KThompson-Lane mentioned this pull request Oct 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NeoForge 1.21.9 fails to load

3 participants