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

Closer process to Forge Gradle's #86

Closed
wants to merge 5 commits into from

Conversation

MsRandom
Copy link

@MsRandom MsRandom commented May 17, 2022

This revamps the process of merging and patching by using the userdev and mcp configs more instead of assuming where everything is. This also uses the official userdev patches instead of getting them from the installer jar.

I also changed the userdev classifier to userdev3 for versions lower than 1.13, which can with the rest of the changes allow 1.12.2 or any other legacy FG3 versions to work.

Tested with:
1.12.2 with MCP(with a bit of extra configuring on the mod's part)
1.14.4 with MCP, Mojmaps
1.16.5 with MCP, Mojmaps
1.18.2 with Mojmaps

One side effect of this is now the Forge merged Jars use Forge's annotations, which shouldn't effect anything, but if that's not reasonable then I could post process the merged Jar to replace the annotations with fabric's.

(Note: this also does what #10 does, as I was unable to use MCP mappings for most versions without it.)

@MsRandom
Copy link
Author

Closed as #87 basically does this but better

@MsRandom MsRandom closed this May 21, 2022
@Juuxel
Copy link
Member

Juuxel commented May 21, 2022

Thanks for this PR btw, it kind of inspired mine 😄 I had been planning a rework to MinecraftPatchedProvider anyway to support the single jar MC option, so this idea fit into that pretty well.

@MsRandom
Copy link
Author

MsRandom commented May 21, 2022

Glad to help! I thought of adding an additional step to the provider to optionally split the Jars to support single Jar and split Jars, but I thought it would've been out of scope for the PR and just rewriting the provider like you did is a much better way of going about that lol

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.

2 participants