You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying a mod with my main casematching deployer, I get an error message when the mod has different files in the staging mod folder with the filename differing only because of one or more capitals. The deployer then gets an error when it can't create a file with an already existing file name. Examples being Kaidan 3 AIO and seasonal landscapes, both for skyrim. Installing a 'simple deployer' led to a different problem. Maybe there could be an option to let the CM deployer keep on deploying and just skip the case-matching for similarly-named files
The text was updated successfully, but these errors were encountered:
Having this as an option seems like a good idea. It currently stops because having multiple files with identical names except for case may indicate some issue, since this cannot happen happen on Windows.
Keep in mind that in this situation Limo wont be able to match any of the files with identical names to a file in the target directory, since there is no way to know which one is the correct one.
It currently stops because having multiple files with identical names except for case may indicate some issue, since this cannot happen happen on Windows.
Every time I've had this issue is because the case will be different between different versions of the file in different FOMOD options.
When deploying a mod with my main casematching deployer, I get an error message when the mod has different files in the staging mod folder with the filename differing only because of one or more capitals. The deployer then gets an error when it can't create a file with an already existing file name. Examples being Kaidan 3 AIO and seasonal landscapes, both for skyrim. Installing a 'simple deployer' led to a different problem. Maybe there could be an option to let the CM deployer keep on deploying and just skip the case-matching for similarly-named files
The text was updated successfully, but these errors were encountered: