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

[1.12.2] Registering Crafting Condition Factories does not allow for actual Resource Locations #5092

Closed
UpcraftLP opened this issue Aug 10, 2018 · 3 comments · May be fixed by CleanroomMC/Cleanroom#70

Comments

@UpcraftLP
Copy link

UpcraftLP commented Aug 10, 2018

When registering custom IConditionFactorys via a _factories.json file, there is no way to register these using a different namespace, due to CraftingHelper always prefixing the string with the current modid.

ResourceLocation key = new ResourceLocation(context.getModId(), entry.getKey());

Imo this should check for a modid prefix before substituting the current modid.

@temp1011
Copy link
Contributor

Why would you want to register a condition for another mod?

@Pyrofab
Copy link
Contributor

Pyrofab commented Aug 10, 2018

It can be useful when your mod delegates registration to a library

@LexManos
Copy link
Member

This is intentional and will not change. If you MUST donlibrary stuff, then register the factory in the "library" and use the full name in the recipe itself. Thats why we force the namespaces, and load them from all mods before loading the recipes themselves. So you can depend on anothers factory.

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 a pull request may close this issue.

4 participants