Once we move to MM9, profile our merge mod installs and see if merging them into less m3m files will be faster. We can use comments to know what is what. While we are doing this, check if anything could be upgraded to classupdate or some other kind of more optimized merge.
The con of this is that it gets harder to update specific sections of the mod, especially the ones that work standalone. For example, updating DebugSaves or PersistentSettings becomes harder than just dropping in an updated m3m.
However, if keeping them as seperate mergemods takes more time (as M3 is opening and closing all the startup files multiple times), we should merge them. MM9 will speed up our merge mod installs, potentially making this unnecessary?
Once we move to MM9, profile our merge mod installs and see if merging them into less m3m files will be faster. We can use comments to know what is what. While we are doing this, check if anything could be upgraded to classupdate or some other kind of more optimized merge.
The con of this is that it gets harder to update specific sections of the mod, especially the ones that work standalone. For example, updating DebugSaves or PersistentSettings becomes harder than just dropping in an updated m3m.
However, if keeping them as seperate mergemods takes more time (as M3 is opening and closing all the startup files multiple times), we should merge them. MM9 will speed up our merge mod installs, potentially making this unnecessary?