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

Conflict on recipes with SecurityCraft #1013

Closed
ghost opened this issue Apr 3, 2015 · 3 comments
Closed

Conflict on recipes with SecurityCraft #1013

ghost opened this issue Apr 3, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 3, 2015

Hello!
Have a conflict with SecurityCraft in recipes.
oc:numPad has same recipe as SecurityCraft's keyPad.
I'm not sure on which side this should be fixed.
This does not result in crash, just leads to non-availability of numPad part for crafting.

@fnuecke
Copy link
Member

fnuecke commented Apr 3, 2015

Hrm... since OC's recipes are based on config files I don't really want to hardcode a switch to an alternative recipe based on mod detection.

@Geforce132 How about we make the items oredict compatible? Then I can use the oredict name in my recipe configs and disable the OC keypad recipe if SecurityCraft is present (and the oredict entry is already present). So basically give yours priority, since the OC one is a pure crafting material.
For what it's worth, OC's numpad already has an oredict entry, oc:materialNumPad. We could either come up with an alternative one used by both, or you could register your keypad with the oredict using that (if it doesn't have one already, of course)? I could do that on my end, too, I guess, but I'd like to avoid registering other mods' items in the oredict without their devs' consent.

Sorry, something went wrong.

@Geforce132
Copy link

@fnuecke No, don't worry, you can keep your recipe how it is, I've changed my keypad's recipe in the upcoming version of SecurityCraft. Thanks for letting me know though. :)

Followed you on Twitter, by the way.

Sorry, something went wrong.

@fnuecke
Copy link
Member

fnuecke commented Apr 3, 2015

Awesome, thanks! And yep, just saw :-)

Will be closing this then.

Sorry, something went wrong.

@fnuecke fnuecke closed this as completed Apr 3, 2015
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

2 participants