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

Fix support for Forge 50+ #227

Merged
merged 12 commits into from
Aug 12, 2024
Merged

Fix support for Forge 50+ #227

merged 12 commits into from
Aug 12, 2024

Conversation

shedaniel
Copy link
Member

Alternative to #225.

  • Fixes modXXX configurations for Forge 50+
  • Forces static mixin remap for Forge 50+ dependencies
  • Replace Union Relauncher with Bootstrap-Dev from Forge itself

@@ -50,7 +50,7 @@ public abstract class MixinExtensionApiImpl implements MixinExtensionAPI {
public MixinExtensionApiImpl(Project project) {
this.project = Objects.requireNonNull(project);
this.useMixinAp = project.getObjects().property(Boolean.class)
.convention(project.provider(() -> !LoomGradleExtension.get(project).isNeoForge()));
.convention(project.provider(() -> !LoomGradleExtension.get(project).isNeoForge() && (!LoomGradleExtension.get(project).isForge() || !LoomGradleExtension.get(project).getForgeProvider().usesMojangAtRuntime())));
Copy link
Member

Choose a reason for hiding this comment

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

Does the PR fix the crash bypassed by 8c2b72a?

Copy link
Member Author

Choose a reason for hiding this comment

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

I never experienced any crash?
To get a crash here you would need to ref the property in your own buildscripts early, so imo just don't do it?

Copy link
Member

Choose a reason for hiding this comment

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

I never experienced any crash? To get a crash here you would need to ref the property in your own buildscripts early, so imo just don't do it?

I think this crash was Architectury Plugin's fault, if so, the Arch Plugin fix should fix that problem if that was the cause.

Copy link
Member Author

Choose a reason for hiding this comment

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

So the crash in that commit is caused by architectury plugin, this should just require a change in arch plugin (which is in a separate branch there)
I think that is a better solution than making this false for forge.

Copy link
Member

Choose a reason for hiding this comment

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

Could you add a known forge mod to the test to see if it gets remapped correctly?

Copy link
Member Author

Choose a reason for hiding this comment

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

I can add it, but the tests won't be able to pick it up if it doesn't get remapped properly anyways, so I am not sure if it makes sense. I usually just have an external project.

@shedaniel shedaniel requested a review from a team August 12, 2024 10:06
src/main/java/net/fabricmc/loom/util/Version.java Outdated Show resolved Hide resolved
src/main/java/net/fabricmc/loom/util/Version.java Outdated Show resolved Hide resolved
@shedaniel shedaniel changed the title Feature/forge mod remap Fix support for Forge 50+ Aug 12, 2024
@shedaniel shedaniel merged commit c040cd3 into dev/1.7 Aug 12, 2024
234 checks passed
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.

3 participants