AlmostUnified and Loading Order

[radiant tiger]

I want to bulk remove recipes from a mod (Ad Astra) and completely replace them with my own recipes. It's easy to remove all recipes, the problem is that I am using AlmostUnified and this mod has its own type of steel that is being unified. Since AlmostUnified is running before KubeJS, all materials are unified and duplicate recipes are removed, which seems to just keep recipes that are first alphabetically. Then, KubeJS removes all Ad Astra recipes, meaning none of the recipes related to steel (nuggets to ingots to blocks and back again) work anymore from any mod.

Is there any workaround to this? I was hoping I could make KubeJS run before AlmostUnified does, because that would smooth out some other minor issues. Is there a way to run server scripts as startup scripts for this case? Is there any other way to make KubeJS run earlier? Alternatively there are a lot of ways I could manually whitelist these item recipes or add them back, but is there any other way to do this without manually specifying the recipes, especially by changing the load order.

[fervent musk]

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

[midnight rover]

I think (correct me if I am wrong) that the order is forcibly always <whatever the mods do> -> <kubejs> -> <datapacks>

I am also working with almost unified - there is a config option to set priority of mods. I've put FTB materials at the top of that list, making all recipes forced to that. Then all kubeJS scripts work from that point on.

[fringe needle]

Also you can specify more filters in kubeJS, if you specify the output item is not steel that could help fix your issue

Either that or instead of bulk deleting recipes you could get all recipes, print them to a text file and use it as a checklist for the ones you still need to replace

Then either delete or override them one by one