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

Read "Fabric-Loom-Remap" manifest entry to allow an artifact to control if its remapped or not. #749

Merged
merged 2 commits into from
Nov 4, 2022

Conversation

modmuss50
Copy link
Member

This allows for none mod jars to opt-into remapping, as well as mods or mod loaders to opt-out. This is useful for mods that have an API jar, that isnt a real mod.

Set "Fabric-Loom-Remap" to true/false in the jar's manifest to opt-in or out. Omit this for the default (only remap mods).

Closes #717 and cleans up + tests some code.

…ol if its remapped or not.

This allows for none mod jars to opt-into remapping, as well as mods or mod loaders to opt-out.

Setting "Fabric-Loom-Remap" to true/false in the jar's manifest.
@modmuss50 modmuss50 merged commit aedfd09 into FabricMC:exp/1.1 Nov 4, 2022
SquidDev added a commit to cc-tweaked/CC-Tweaked that referenced this pull request Nov 18, 2022
 - Bundle the core API inside the Fabric API jar for now, to ensure
   that ResourceLocation is remapped.

 - Add a dummy fabric.mod.json file to the API. We'll remove this once
   FabricMC/fabric-loom#749 is released.
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.

Add a jar manifest option to opt-in and opt-out of remapping when on a mod* configuration.
1 participant