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
Can you add the ability to detect mod conflicts to the mod list?
A lot of mod managers help with load order (LOOT, Vortex, etc) and detect mod conflicts. I think a potential implementation of this would be to generate the file list for every mod's .pak file, along with a checksum value for each file. And if two mods contain the same file and different checksums, it would be listed as a conflict.
Ideally, it would also allow for resolving the conflicts by creating a "Last Word" mod that merges the conflicts and is loaded last. For text files (scripts, etc) it would allow a three-way merge (maybe invoking Beyond Compare in 3-way merge mode) with the base file, and each mod's modified version of the file (BC would show what's different in each one) and allow you to merge the changes from both mods into a single file that could then be repacked into a mod file that gets loaded last to resolve the conflict. You could then record that the conflict was resolved and not show that conflict again unless a mod updated itself and the checksum of the file changed.
The text was updated successfully, but these errors were encountered:
jchamlin
changed the title
Detect Mod Conflicts
Detect (and possible help resolve) Mod Conflicts
Oct 14, 2020
Can you add the ability to detect mod conflicts to the mod list?
A lot of mod managers help with load order (LOOT, Vortex, etc) and detect mod conflicts. I think a potential implementation of this would be to generate the file list for every mod's .pak file, along with a checksum value for each file. And if two mods contain the same file and different checksums, it would be listed as a conflict.
Ideally, it would also allow for resolving the conflicts by creating a "Last Word" mod that merges the conflicts and is loaded last. For text files (scripts, etc) it would allow a three-way merge (maybe invoking Beyond Compare in 3-way merge mode) with the base file, and each mod's modified version of the file (BC would show what's different in each one) and allow you to merge the changes from both mods into a single file that could then be repacked into a mod file that gets loaded last to resolve the conflict. You could then record that the conflict was resolved and not show that conflict again unless a mod updated itself and the checksum of the file changed.
The text was updated successfully, but these errors were encountered: