

HCDU (the Hack Conflict Detection Utility, as created by Paladin, and available at will find all mods that conflict with each other, and lists them in the order in which they currently load. However, if you were to put the plug-ins in sub-folder A, and the main module in sub-folder B, then the main module would load AFTER the plug-ins, and stuff would NOT work as intended. So, for example: if you keep the main mod and the accompanying plug-ins together in one folder, they'll load in a specific order depending on the names they were givenm and the author purposely names them such that they load in a correct order.


Load order is normally settled very simply (at least on NTFS drives): all sub-folders of Downloads are read in alphabetical order, and the packages within each folder are also sorted by alphabet. So, in this case, the conflict is INTENTIONAL, and the author of the mod supplies instructions for the load-order, in order to ensure the proper functioning of all parts of the mod. Now obviously, if the main module loaded last, the plug-ins' versions of those BHAVs would not be called, rendering said plug-ins inoperative. So the plug-ins contain different, expanded versions of a few of the BHAVs that are also found in the main module. However, for the plug-ins to work properly, SOME of those BHAVs need to be expanded. The trick here is, that the main mod needs all the BHAVs that are included in it, and these BHAVs need to be exactly the way they were written. In some cases, a mod is created to complement another, or to improve upon it.
