Semi-permanent grist registry for large packs to reduce huge startup delays in 1.19.2

[Darkmega18]

As reported from my discord post. My game hangs for a good 3-10 minutes depending on luck when selecting a world or starting up world gen, it's very disruptive to pack creation where I must iterate my recipes and other datapacks and such a lot to be able to test things.

Can I have atleast a way to disable auto grist registry until something along the lines of a "automatic grist recipe cache" feature can be created? Basically Make the thing do the recipes etc as needed and save them into a very big config file or something that remembers the output so it doesn't need to do it again unless you want to do it again. For example when a modpack changes one can just run a command to update the outputted file.

Any recipes in the auto grist registry that seems fair and if someone cares to do so, should also be fine to just be copied out of the file and turned into a grist cost recipe etc after the fact, which would double it's usefulness to also being a pack making aid.

[kirderf1]

To reiterate what I might've said elsewhere and add to it: With the slightly niche nature of such a feature, I can see this done as an addon mod, which could output a datapack with explicit recipes as well as disabling the minestuck:recipes/grist_costs/generated.json recipe (a datapack which in turn shouldn't need the addon to function). It's of course also important to check whether generated json files is a sufficiently good step-up for performance. If insufficient, it could be worthwhile to at that point support an alternative and more compact format to speed up IO/parsing.

[Darkmega18]

well, since I'm already the one with a huge pack that keeps expanding cause I wanna try some mods. make something when you can and ask me to test how it goes then and we'll find out the difference.