executionByFork
commented
3 years ago The issue is likely that the mod edits a game file that MCCModManager thinks isn't a game file. I haven't had the capacity recently to continue development on this so I haven't pushed out any updates, and meanwhile MCC has had a few updates. There is a JSON file which lists every single file in the MCC install directory, which the mod manager uses to determine whether a backup of a file needs to be made before a mod clobbers it. When that mod is uninstalled this mod manager restores that file from the backup, to reset the game to a vanilla state. If an MCC update adds a game file and it is not added to this JSON, then it won't make a backup which means that when the mod is uninstalled the mod manager just deletes the file, leaving the game in an unstable state.
To generate this JSON file, I use a perl script I wrote to walk the game directory (here). The file that is generated sits at Formats/filetree.json beside the mod manager executable. I will try to find some time to run this script to make a new JSON file and push a minor update to fix any incompatibilities, but to do so I need to have every MCC game installed and I think I am a little short on hard drive space atm... So I'll have to manage that before I can put something out. In the meantime, if you want to run the perl script and replace that file you can do so (see installation from source in the readme, from step 6-8). I bet that will fix your issue. You'll need Linux Subsystem for Windows installed, or find out how to use perl with powershell. If you don't have all the MCC games installed when you run the script that is fine, so long as you don't try to mod any of the others if you install them later, or you make sure to run the perl script again after installing new ones. I have to have all of them installed when I run it to make sure everything is supported for anyone who downloads the mod manager.
This thing seemed promising but I think I have no choice but to consider this app to be the reason my game keeps breaking.
I just had fixed my ModifiableWindowsApps directory from a previous state of "UE4 Fatal Error." I launched MCC Manager, it prompted me with this message and it warned me if I don't do it, some features would not be available so I clicked okay. Game instantly back to UE4 Fatal Error.
Sometimes If I just close MCC Mod Manager, the UE4 Fatal Error goes away. But it'll be back.
I did manage to see it work 1 time. I created a modpack, installed it, backups looked like they worked. I installed a mod to for a different halo game, UE4 Fatal Error. Clicking Restore Files didn't fix it. Since the windows store doesn't have a great way of validating file integrity... Now I guess I'll copy the entire directory over from my external (120GB). I sure hope MCC modding evolves to something smoother in the future.
I'll probably check back on the development of this later in the future. Thanks.