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

[Feature Request] Patch Forge ModLoader or Loom in Forge mode to dynamically remap Forge mods #222

Open
Ampflower opened this issue Jun 25, 2024 · 0 comments

Comments

@Ampflower
Copy link

Simply, have Forge remap to the actual dev mappings when remapping mods/. For 1.20.6+, this is only relevant for when dev isn't set to Mojmap.
If Forge has no supporting code for it in the loader, it might be viable to provide an alternate method via Loom instead.

Why?

The mods folder is a good spot for quickly tossing in a mod to test or debug with without actually pulling it in as a dependency, which is non-trivial when the mod in question isn't on standard platforms.

Results:

I have tried to dump EMI for 1.20.1 in, and noticed that when it failed, it seems Forge remapped it to Mojmap; tho that might've just been more so due to modern Forge having classes be in named when compiled. I'm not sure how viable or reliable such a patch would be, if there is a spot to hook in.

Considerations:

Using the already existent mod* functions in Gradle; which work but isn't as convenient for one-offs of "does this work by chance?", particularly when the mod isn't on a maven.
This isn't intended to be a mean of development; merely act as if modRuntime was applied.

Other:

Architectury Loom: 1.6.397
Minecraft 1.20.1
Forge: 1.20.1-47.2.0
Yarn: 1.20.1+build.10

Xplat setup with Arch API absent; Loom is solely used for remapping and running 'Common' and Forge.

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

No branches or pull requests

1 participant