Simple idea, probably not the first to think of it or suggest it.
Basically, I want a tool that can be run in one of the game directories, after extracting some mods, that will look at all of the setup-??.tp2 files and analyze them to see which ones modify the same files. The output would be a "??.tp2.conflicts" file for each one, something like this:
MyMod component ## designated ## modifies files that are also modified by OtherMod component ## designated ##
>>list of first N files (N specified on command line before runnig tool) of each extension type of the files that are "conflicted" in this way << e.g.:
17 .cre: kobold1.cre, kobold2.cre, ...
99 .bcs: kobold1.bcs, kobold2.bcs, ..., koboldN.bcs [... additional not shown]
etc. for each component
If it's simpler, the tool could also be designed to work only after all of the mods have been installed, something like the WeiDU --change-log feature except not limited to a single file and with summarized output so we don't get lists of 35565 files.
My reason for this request is to make it easier to discover mod component conflicts for BWS.