Given that we no longer have recourse to unique identifiers for mods as in FA through modinfo, is there a need to promote a naming convention scheme so that modders can name their scd's to load in the correct order alongside other mods?
For example, Mithy uses "_
" to make sure his mods are loaded first. So, maybe Mithy could make a post as to what type of mod would need to start with _, which ones would need to be loaded last, etc. We could then have a convention scheme like: _mod_, zmod_, zzmod_, etc.|||As far as I can tell, the name doesn't affect anything. .scd/folder mount order has nothing to do with 'load order' (which doesn't really exist as a concept in SC2, since engine hooking is disabled and no two files can share the same path), and I'm not even sure that mount order is based on name, as it seems that mount precedence for a file that exists in two .scds is pretty random.
I put an underscore in my mods' filenames so they float to the top of a windows explorer window open to \gamedata. No other reason.|||So then how exactly do bp merges of bp merges work?|||As clearly explained in the blueprint merging thread, by the internal path and filename of the actual .bp file. Not the .scd file. A merge of an original blueprint that another mod added has to have a lower path/filename than the original (which is usually easy, since the original should probably be in /units/).|||Thanks Mithy. And sorry, I should have checked the other thread first 
No comments:
Post a Comment