Refer to the README for up-to-date information about the program.
I will use this space to outline/discuss modding-specific ideas, concepts, and features.
Why do we need this program? There are no tools available that accurately report conflicts or duplicates between mods.
With more information about conflicts, players can better sort their mods or install them in the optimal order.
With more information about conflicts, modders can easily identify how their mods affect other mods.
With more information about conflicts, STEP guide authors can write better guides.
With more information about duplicates, players will benefit from smaller archive sizes, faster downloads, and less conflicts reported by other software.
With more information about duplicates, modders can easily discover which files are shared across mods or others, and using that information, they can create BSA resource packs containing just those files.
Doesn't Mod Organizer already report conflicts? Mod Organizer reports too many conflicts. 90% of the conflicts reported in MO are duplicates. Duplicates have no impact on your game, so trying to resolve those conflicts is a waste of time. In addition, because only 10% of the conflicts are meaningful, you're just guessing when you use that data to make sorting decisions.
This program takes the guesswork out of the process and shows you not only which files conflict but also how they conflict.
Later, I'll implement features that will allow you to resolve those conflicts directly from the user interface.
Column 1 is the MD5/CRC32/Murmur3 hash of the file. This fingerprint uniquely identifies the file.
Column 2 is the name of the mod. In Mod Organizer, the name of the mod is the folder in which that mod resides.
Column 3 is the path to the file in that mod's folder.
Column 4 is the size of the file in bytes.
Column 5 is the width of the file, if the file is a DDS texture.
Column 6 is the height of the file, if the file is a DDS texture.
The layout will change as I update the program. For example, there's no column for file modified date yet.
Packed vs. Unpacked BSAs
I'm not sure if there's a solution to the BSA problem. It might be possible to generate MD5 hashes for each file in uncompressed BSAs. I haven't investigated yet.
So, for the time being, BSAs will need to be unpacked for this program to work.
Contributing
I'm really not that great with C#, so if anyone here is great with C# and wants to contribute, the source is on GitHub under the GNU GPL v3.0 License.
Question
fireundubh
@fireundubh is currently MIA and has also removed all his projects from all the locations he had them.
As such this page and the links on it are useless.
Page is now locked. -- @GrantSP
"md5gen" accurately discovers conflicts between files.
md5gen was developed with Skyrim and the Skyrim Mod Organizer in mind, but there are probably other applications.
Source available at GitHub | README
Refer to the README for up-to-date information about the program.
I will use this space to outline/discuss modding-specific ideas, concepts, and features.
Why do we need this program?
There are no tools available that accurately report conflicts or duplicates between mods.
Doesn't Mod Organizer already report conflicts?
Mod Organizer reports too many conflicts. 90% of the conflicts reported in MO are duplicates. Duplicates have no impact on your game, so trying to resolve those conflicts is a waste of time. In addition, because only 10% of the conflicts are meaningful, you're just guessing when you use that data to make sorting decisions.
This program takes the guesswork out of the process and shows you not only which files conflict but also how they conflict.
Later, I'll implement features that will allow you to resolve those conflicts directly from the user interface.
Sample Output - Report Type: Conflicts - Hash Type: CRC32
Sample Output - Report Type: Duplicates - Hash Type: CRC32
The layout will change as I update the program. For example, there's no column for file modified date yet.
Edited by GrantSPPacked vs. Unpacked BSAs
I'm not sure if there's a solution to the BSA problem. It might be possible to generate MD5 hashes for each file in uncompressed BSAs. I haven't investigated yet.
So, for the time being, BSAs will need to be unpacked for this program to work.
Contributing
I'm really not that great with C#, so if anyone here is great with C# and wants to contribute, the source is on GitHub under the GNU GPL v3.0 License.
7 answers to this question
Recommended Posts