Uninstalling the DisplayEx mod deletes all the custom backgrounds
While this functionality of the mod manager is intended, it doesn’t feel right with this mod and the background files. Unchecking and rechecking is and should be a standard way to ensure you have the latest version of the mod installed.
So I will need to think of a solution to this problem.
It is only a issue with fixes. Updates for the same versions. With normal version updates, the new mod is just installed. It shouldnt be un-intalling anything and deleting the files… I think…
Comments (5)
-
reporter -
reporter After thinking about it for a few days, pondering a few different ideas… I realized that the app did not delete the files on un-install already. This is specifically because, you know how the mod files are listed in the mods tab? The green/orange stuff used to denote conflicts? Notice how the background files are not listed there? They are a special type of mod file thats not monitored by the header of the mod. When deleting files, CaVE deletes the files it knows exists. The one in the header.
So the issue was purely on the part of extracting the backgrounds from the nsom, and needing to not overwrite custom backgrounds with the placeholders. So what I have done added a check on mod install, where if a file is not specified in the header it checks and compares timestamps, overwriting only if the version in the nsom is newer.
Try this exe update.
https://www.dropbox.com/scl/fi/gbprjqobnagxqtn28iafs/CaVE.exe?rlkey=getbbdyvjuznm56l2qapofoso&dl=1
What should happen now is that when you uncheck and check to ensure you have the latest version of the mod installed, your custom backgrounds should remain.
-
That did the trick.
Did the following to test:
Test 1:
- Opened the resources/sprites folder and unchecked and rechecked the mod with the old CaVE build. Watched my custom backgrounds replaced with default ones.
Test 2:
- Replaced the CaVE.exe with the new one and did the same test as above and my custom background did not get deleted.
Works!
-
I can confirm that the custom background did stay after unchecking, the re-checking the mod after the database reloaded!
-
reporter - changed status to resolved
Thank you!
- Log in to comment
I was thinking of tracking the dates of the files that come out of the nsom, separately from the database files… That would do it for knowing not to delete certain files…
But I realized that would not work when it comes to checking the mod and having it install the files. That has to overwrite existing files.
Maybe… I can only skip overwriting when manually installing? I.E. checking the mod, but not when auto updating?
Still feels prone to issues…