Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MinecraftGameProvider: Support split assets jar #793

Merged
merged 1 commit into from
May 4, 2023

Conversation

Juuxel
Copy link
Member

@Juuxel Juuxel commented Apr 17, 2023

Companion PR to #790. The older one is needed for ModLauncher support, this one is needed for running on ML together with Forge. Forge splits the MC assets into a separate jar on modern versions, so it needs to be recognised as an MC jar as well.

(If it's not recognised, random things like the detected MC version break.)

Copy link
Member

@modmuss50 modmuss50 left a comment

Choose a reason for hiding this comment

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

LGTM, will need testing, especially in a split sources setup.

It is an intresting idea, as right now loom (wongly?) adds this file to both the client and server jar when splitting here: https://github.com/FabricMC/fabric-loom/blob/11f69ccbf0ed5660a3cf547685e2e2fc28581835/src/main/java/net/fabricmc/loom/configuration/providers/minecraft/SplitMinecraftProvider.java#L79

Maybe moving the assets to their own jar would be a cleaner solution 🤔

@modmuss50 modmuss50 merged commit 912233f into FabricMC:master May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants