Requires MixinBooter to load otherwise this mod won't do anything.
Tinkers' Construct scans all recipes to register ore dictory based smelting recipes, such as golden sword => 288mB molten gold. However, there are thousands of recipes in massive modpacks. The game would scan them every game loading and take much time. This mod caches all smelting recipes and stops Tinkers' Construct scanning all recipes over and over again. Performance optimization would appear on the second load.
A test result on a massive modpack: e2e-extended
Thank you for this great mod!
I was wondering if the mod automatically remakes the list when something changes in the modpack, or if there is something I need to do to force it to remake the list? Or would I have to remove the mod and put it back in when I change some smelter recipes? The reason I'm asking is because I'm starting work on a private modpack that is just for me and a friend, with the premise of the pack involving a lot of going through and essentially changing a majority of the recipes, so this would be something good to know ahead of time before I start to mess with the recipes.
When the mod list is different from the last run, this mod will rescan the ore dict and build the new cache.
In reply to youyihj:
Awesome! Thank you!
thanks so much for this. id love to have a mod similar to this but for caching all of jei recipes so it doesnt have to index them every time the game loads
Sounds awesome , thx for all that hard work <3
Great stuff!!!!
wow, there are a lot of things to optimize in modded minecraft (Time, Memory and Performance) that never came to my mind, i appreciate the labor of you modders who aim to increase this performance
But i had a little offtopic doubt, how did you made this graph of loading times?
is there a mod to do this automatically? or you made it by hand with the info in the log?
https://github.com/Krutoy242/Enigmatica2Expert-Extended/blob/master/dev/automation/benchmark.js This is a NodeJS script that reads debug.log and crafttweaker.log file to find what took how much time:
Good work! This was going to be my next optimization in LoliASM