-
Notifications
You must be signed in to change notification settings - Fork 30
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 registered late in loading? (Can't remove with crafttweaker) #84
Comments
Are you still experiencing these issues? If so please let us know and we can investigate it further. |
Reproduce with this Script: import mods.gregtech.recipe.RecipeMap;
import crafttweaker.item.IItemStack;
val compressor as RecipeMap = RecipeMap.getByName("compressor");
compressor.findRecipe(2, [<minecraft:coal:1> * 9], [null]).remove(); And the option for compressor recipes for 3x3 blocks is enabled is enabled |
This seems to suggest that we might be adding recipes too late in the Forge initialization lifecycle. Recipe registration is expected to occur in response to |
Following up on this issue, we have determined that it is not possible to fix this at this time. Forestry is registering its recipes after CraftTweaker processes scripts, and we have to run our modifications after their registrations happen. We have done what we can about things on our end in #133 and also contacted Forestry's dev team about this issue (ForestryMC/ForestryMC#2599). If they make the necessary changes, then we can update things on our end as well to support customizations. |
Many sog recipes in gt machines can't be removed with crafttweaker:
chemReactor.findRecipe(24, [<gtadditions:bee_comb:13>*9, <ore:crushedSpodumene>.firstItem], [<fluid:water>*1000])
is null since the recipe hasn't been registered yet.I assume these recipes can't be removed and aren't registered because crafttweaker is running its recipe addition stage after sog and nc, which could be fixed by sog but could also be considered a ct bug since why isn't ct running last of all.
The text was updated successfully, but these errors were encountered: