I am not sure how easy this is to code into the engine, but mods could have before.txt in their mod folder, which acts like depends.txt, but makes that mod load before the selected mods.
Wildcards
Also, it could be good to add *# wildcard support for example:
PilzAdam wrote:Ehm, mods in depends.txt are loaded before the mod. You can also use "?" to not depend on the mod, but just load them first.
I think he means haveing the mod load before others in the file. In mod 1 you have it say default in before.txt and mod 1 will load before default. But i dont think it could work because what if mod 2 befores mod 1 but depends on mod 3. and mod 3 depends on 1 but befores 2. Then none of them can load.
Coding;
1X coding
3X debugging
12X tweaking to be just right
If you want to override a function, wouldn't you have to have it load after the original function or else the original function would override it when it loads? I haven't tried to do this so I don't know but I have overridden some nodes and that is the order they need to be done in. First the original node loads and then my override loads overwriting the original node.
I see at least one use for that: once I wanted a mod that added tin to remove that silly bronze recipe, for that the mod had to load before default. The same thing can be used if one wants a mod to change a craft or delete a default node or change an ABM, that can't be done without that.