The lexicographical winner is the one with the earliest highest characters regardless of length of the full folder names. The folders are compared character by character without regard to the full length of the folder name. And it may be different for pure numbers, letters, and mixtures of the two.Įdit: it is not normalized as to length. A 1:1 character by character comparison irrespective of different lengths, or normalizing the names to the longest length and treating shorter filenames as if they have null characters for the nonexistent preceding positions.
However, it is as yet unknown exactly how the enumeration process handles foldernames. Because the ID numbers are incremented for later posted mods, and the ID number is used to set the folder name, it would hold that newer versions with newer dates also have higher Steam ID numbers, and therefore win conflicts due to the higher folder name number. It is believed, but not proven as yet, that the same holds true for files in the local Steam Workshop folder. The exact same files simply swapped between the folders without any other changes causes the one in the "last" folder, alphanumerically (which is B-tree order for Windows) to win every time.
The dates of files or folders (creation, last modified, or accessed) doesn't matter.Īny data or entry in the mod's files doesn't matter. The order of the mods in the XComModOptions.ini file doesn't matter.
If you have three mods with conflicts in the local "mods" folder, using subfolders 001, 002, and 003, then the one in folder 003 will win every time. It is 100% determined by the foldernames of the mods, using an alphanumeric type function.Ĭontrolled by the file/folder handling routines of the OS, not the game. So I have tested how loadorder works using local files.
0 kommentar(er)
