-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Recipes with "too many" ingredients fail to be crafted via terminal #110
Comments
Thanks for reporting! |
Should mention that this is occuring with the "Recipe.with_io" operator. I can confirm that I am also running into this issue when having an ingredient as input with more than 10 unique items. Incidentally if you make a new card of the same signature and place it in a crafting terminal, it will flash an X for a brief moment before being recognized as valid. |
The fact that it works with the Crafting Writer but not the Terminal is strange. But it also makes me suspect that this one shouldn't be too difficult to fix, since we have one functional code path. |
The crafting writer also seems to have an issue with these kinds of recipes. |
This fixes issues where some recipes could not be crafted. Closes CyclopsMC/IntegratedCrafting#110
Issue type:
Short description:
When you make a Recipe that has more ingredients than the Logic Programmer has slots, you can't request the recipe via terminal, but it is possible via Crafting Writer.
Steps to reproduce the problem:
(Alternatively, I've attached the modpack including the world I've used for testing. The pack has been exported as a CurseForge pack, so it should be compatible with most launchers)
Integrated Dynamic Testing.zip
Expected behaviour:
I'd expect to be able to order my programmed recipe through the terminal
Versions:
This mod:
1.1.7
Minecraft:
1.20.1
Mod loader version:
Forge 47.3.0
Log file:
N/A
Additional Info:
This issue has a discord conversation preceding it: Messages on the CyclopsMC Discord
When I initially made the test setup, it worked, however after a world reload the issue started happening. That's why I've added step 5 for the reproduction.
The text was updated successfully, but these errors were encountered: