CoreModules is in charge of loading modules, both loading into the editor as loading and delivering the instances with their correct ID so each module instance has it's own settings file. CoreModules is also in charge of getting the settings files for each instance as to not have a directory which is full with people inventing their own standards for naming their modules which could conflict with other modules.
One thing which should be taken in mind is that CoreModules should have it's loadables first, else it'll cause problems with CoreLayouts.
CoreModules is in charge of loading modules, both loading into the editor as loading and delivering the instances with their correct ID so each module instance has it's own settings file. CoreModules is also in charge of getting the settings files for each instance as to not have a directory which is full with people inventing their own standards for naming their modules which could conflict with other modules.
One thing which should be taken in mind is that CoreModules should have it's loadables first, else it'll cause problems with CoreLayouts.