Some items I can't even auto craft some I can. Shortly after I start seeing lag spikes and 100 percent cpu ussage
when I try to craft something using a pattern I can select it and the amount I want. But when I hit start it shows that it has been click by going dark grey but then nothing happens and I have to hit cancel. Shortly after I start having leg spikes I first noticed it when I went to craft epic bacon on sky factory
Does this issue occur on a server? [yes/no]
[pastebin/gist/etc link here]
What are you trying to craft? Cause when you press the button it might take some time to calculate if it is a large task.
epic bacon from sky factory but it hapens with other things to. It does seem to be a thing happening with larger tasks but it causes lag spikes and maxes out my cpu after I hit start on the crafting.
Are crafting the dyes using RS and the mystical crops essence? Cause that recursive crafting recipe might be causing issues.
Does RS and mystical crops have issues together because I did have some issues with crafting other things from mystical crops before
Took out the dye recipes, they weren't using mystical crops but I can now auto craft bacon.
It is just the fact that some recipes of mystical crops (and maybe others) take as input a lower amount but the same item as the output. In general recursive crafting, although mystical crops isn't always an issue. I made quite some changes to try and support recursive crafting. eg. if you want to upgrade your essences just force start it, that way you won't need multiple stones. But I'll try and fix this issue in the near future (won't be for next SF update, but in a few weeks maybe).
Sounds great, Ill just avoid auto crafting dyes then thanks for all the help!
+1 [Raising Awareness]
Noticed the same issue on our server when one guy used the duping mechanic of botania (1 dust -> 2 dust).
We had to download the map and delete the controller with MCEdit. Everytime we logged in it started crafting and crashed/got stopped by watchdog.
I'd suggest to rename the issue.
Thanks for the report. I'll close this for now, since this is a duplicate of #838.
But, since this issue and #838 are linked now thanks to this comment we'll obviously still look at your profiling report.