@fubar_life123 I completely understand, and in the end something that deletes and/or modifies files in a recursive way should always be used with caution. I would recommend making a backup of your saves folder before running varbsorb, just in case. However I ran it myself a few times, here's why I think it's fairly safe:
1. It's open source, you can inspect the code here:
https://github.com/acidbubbles/vam-varbsorb
2. It's unit tested (65% code coverage) and has an A rating of code quality by Codacy and 0 alerts by lgtm. There won't prevent bugs but at least they mean basic reviews and typical pitfalls were seen and addressed.
3. Instead of deleting any files, it sends them to the recycle bin. So you can easily see what was modified and restore the files if needed. Note that the scene json files however will be modified.
The methodology is based on file hashes and type-awareness. A hash is a unique representation of a file's content (it's heavily used in security, I'm using SHA1 because security is not a concern in this specific case however). I'm scanning both the scenes and var files, and I find matching files. For morphs, I only match based on .vmi+.vmb pairs to avoid broken references. After cleaning up a file, I update scene files so they point to the .var file instead. In case of multiple var files having the same content, I'll prefer the .var with the fewest files.
Hope that helps, to be honest I cannot say with confidence that this code is flawless (there was no peer review and there's no metrics of success other than on my own machine and from the few people who were nice enough to report back problems) but if you backup your files, it should be fine. I have mechanisms in place to prevent the program from going outside the "safe" folders.
