If you have a loader mod that isn't currently supported, please post a message below with the mod name and a link to the mod in question. Loader mods currently supported:
- Krastorio 2's loaders, since version 1.2.0.
- AAI Loaders' loaders, since version 1.2.0.
- 5Dim - New Transport's loaders, since version 1.2.0.
- Loaders Modernized's loaders, including Ultimate Belts' compatibility, since version 1.2.0.
- Factorio+'s loaders, since version 1.2.2.
- Comfortable Loaders' loaders, since version 1.3.5.
- Comfortable Loaders's More Belts loaders, since version 1.3.5.
- More Belts Loaders' loaders, since version 1.4.3.

This is not exactly a request for loader compatibility so much as a remark/question about it, which is adjacent enough I am not sure whether to respond to this thread or make a new one, so arbitrarily I have chosen to respond.

If multiple loader mods are present, then this mod seems to only upgrade one's and complain that the others' loaders are unsupported. My specific case is I have AAI loaders, and have left K2 loaders enabled because a K2 addon crashes on startup otherwise; under these circumstances, this mod upgrades K2 loaders but not AAI. I am not sure if this should be considered a bug or intended behavior, but it seems at least worth pointing out and asking about.

That is... kinda intended behaviour? It depends on the order with which I define the options for a tier. In this case, K2 is defined first, therefore the AAI loaders is never considered. I am working on refactoring the system to have arbitrary many loader options for each tier, which will solve this issue. Should have time before the end of the month to get that sorted.

If multiple loader mods are present, then this mod seems to only upgrade one's and complain that the others' loaders are unsupported. My specific case is I have AAI loaders, and have left K2 loaders enabled because a K2 addon crashes on startup otherwise; under these circumstances, this mod upgrades K2 loaders but not AAI. I am not sure if this should be considered a bug or intended behavior, but it seems at least worth pointing out and asking about.

This has now been fixed in version 1.5.0.