Tools to help identify and resolve mod conflicts for modders and users alike
Permissions and credits
Credits and distribution permission
Other user's assetsAll the assets in this file belong to the author, or are from free-to-use modder's resources
Upload permissionYou can upload this file to other sites but you must credit me as the creator of the file
Modification permissionYou are allowed to modify my files and release bug fixes or improve on the features so long as you credit me as the original creator
Conversion permissionYou can convert this file to work with other games as long as you credit me as the creator of the file
Asset use permissionYou are allowed to use the assets in this file without permission as long as you credit me
Asset use permission in mods/files that are being soldYou are not allowed to use assets from this file in any mods/files that are being sold, for money, on Steam Workshop or other platforms
Asset use permission in mods/files that earn donation pointsYou must get permission to earn Donation Points for your mods if they use my assets
Author notes
This author has not provided any additional notes regarding file permissions
File credits
QuickBMS is by Luigi Ariemma, DQ11 QuickBMS script (v4) is by spiritovod (yes, the same guy who made it possible to make pak files for this game -- love this guy)
comm.exe is originally a UNIX / GNU application, ported for Windows by UnxUtils
Donation Points system
Please log in to find out whether this mod is receiving Donation Points
Changelogs
Version 0.0.3
Added some optimizations that ignores multiple versions of the same mod earlier in the process (and cleans up output slightly as a result)
^Added a "legacy mode" option at the beginning of the script which will force the script to process multiple mod versions like before (for any unforeseen edge cases where this would be needed)
Added a full mod listing to the script's output file along with a metric of the # of files replaced by each pak mod
Small improvements to script's output and verbosity
Version 0.0.2
Added a startup script for the overrides scanner in order to bypass execution policy issues for users that have it set to restricted (default)
Added an additional progress display to the overrides scanner at the start. Results at the end are slightly more verbose if overrides are found.
This is somewhat an offshoot of the Mod Customization Tools released some time ago. It's comprised of a small script (and companion utilities) designed to help both mod authors and users troubleshoot issues -> most specifically mod conflicts.
I highly recommend this if you are a heavy mods user (20+ mods installed). These tools will give you a detailed breakdown of all the mods you have installed, the # of (internal) game files they replace, and exact details on every file override.
I've had this one on the backburner for awhile -- put it off since a year and a half (or so) ago as it wasn't super necessary then. We were a small, tight-knit modding community who all kind of knew how things worked (or could explain it to each other easily enough).
Since then, the DQXI-S Modding Community has grown much larger and a lot more folks have gotten involved (which is awesome!). This has also, predictably, made the case for this tool to be finished and released as more mods mean more (potential for) mod conflicts.
It is my hope that this tool will make it much easier for finding, reporting, and even fixing these issues if/when they arise. They won't always be preventable, but this should make things a little better.
Once found, it's possible that an experienced modder can use the Mod Customization Tools to remove or edit the conflicting files inside the overriding pak.
----------------------
Installation and Usage Instructions
Open the zip and *copy the entire contained folder into <steamapps>\common\Game\Content\Paks
*(Do not unzip as a new folder, copy the existing folder already in the zip)
Enter <steamapps>\common\Game\Content\Paks\Mod_Troubleshooting_Tools\ and double click 'start-scanner.bat'
The script will run (might take a few minutes) and will say whether or not any mod overrides are found. If so, they will be listed in "mod-overrides.txt" in the same directory.
That's it -- see the included 'directions.txt' for more details.
----------------------
Also: feel free to leave these tools in place. Anytime you run into an issue, you can always re-run the checker and it will create a new index based on the mods you have installed --> it will then tell you if there are any overrides. You can upload "mod-overrides.txt" to pastebin and send the link if you need to report a mod conflict to an author.
