However, you don't really want to use this unless unless your mod really requires the other mods to run. Ī mod will always load after any mods in its list in. This default order seems rather kludgy, so I would suggest not relying on it as I wouldn't be surprised to see it change in the future, so I would suggest always using the Priority attribute (see below) to explicitly determine file order when order matters.
modinfo's element, not in their order within the component. The default order of files is to load with their components in the order in which they appear in the. The default order of components is to load with their mods in the order in which they appear in it's. If the last added Mod's id starts with "00", say, it will load last during game creation (since it was added last), but first when a game is reloaded, even before any DLC.īasically, if your mod has load order dependent elements, don't rely on the default load order of mods-it may appear to work during your testing, but that's probably just because it's the last mod whose. When a saved game is loaded, however, mods load in alpha-numerical sort order by Mod Id-the GUID used as the "id" attribute in the root element of the. The default load order of mods for new games is by ModRowId in mods.sqlite, which basically means mods are loaded in the order they were added to the database, with them being re-added any time the modified date of their. This information is really only necessary if you want to modify DLC content or the contents of other mods or you're working on a compatibility issue with another mod that could be resolved by altering load orders. Note-most mods won't have to worry about any of the below because they have no reason to care about load order.
0 kommentar(er)
