-
Notifications
You must be signed in to change notification settings - Fork 98
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
[5.09.32pre6] Advanced Circuit recipe annoyance #1556
Comments
Okay, possible clue: I started a new world with Mekanism included in the modlist, and now the circuit assembler recipe that would normally make an IC2 advanced circuit instead makes a Mekanism Advanced Control Circuit, at least when looking up the recipe in NEI. I haven't (yet) figured out why that happens either, but I'm guessing it's related. |
It took a little digging, but this can be fixed with a one-line change:
That first "true" in the argument list is for "aIsUnificatable", meaning that circuits can be oredict unified (though the GregTech-specific ones have subtags to prevent that). I see no reason to unify circuits, and setting that false allows proper lookup of the Processor Assembly and Nanoprocessor (without having to scroll past the IC2 Advanced Circuit recipe). |
See Blood-Asp#1556 - most (or maybe all) GT-specific circuits are already blacklisted, and I don't know of any reason to insist on unifying circuits, but this had a weird side effect described in that bug related to looking up recipes for HV-tier circuits.
When I go to check the recipes in NEI for making an HV-tier circuit with an MV-tier circuit assembler (called a Processor Assembly, using a plastic circuit board) or an EV-tier circuit assembler (called a Nanoprocessor, using an epoxy circuit board), I have to scroll past the recipe for the IC2 Advanced Circuit in an LV-tier circuit assembler (which indirectly uses phenolic circuit boards) every time, and quickly gets annoying.
I've tried searching the source code (local copy, since searching GitHub often doesn't work as well), but I haven't had much luck figuring out why this happens. Maybe somebody else will have better luck.
The text was updated successfully, but these errors were encountered: