Unity Mod Manager and deleting outdated files

[AndrewBeeman]

So this is a weird one here but maybe there is something I am doing wrong and would love the advice.

If you take a look at the experimental version of my railroader mod here

https://www.nexusmods.com/railroader/mods/143

I have a bundle, definitions.json and catalog.json, the issue has been plaguing me for quite some time now, when people update my mod, everything works out, it replaces the .jsons and .dlls, but it is a heavy hit and miss if it replaces the bundle or not, and usually it doesn't and I get a lot of comments saying that it doesn't work, or things are broken etc.

If there was a functionality within the info.json where Unity Mod Manager will completely clear out a file if it exists and allow for a clean install, that would be extremely helpful, unless it has to do with the way my mod is set up. Any help would be appreciated

[newman55]

The mod update function overwrites all files from the archive. What do you mean by outdated files, files that are now garbage? Such files are not deleted. I don't use a clean install so as not to delete the configs that are generated at runtime.

[AndrewBeeman]

Not necessarily garbage files so much, but it's seeming to not overwrite the old bundle file, so I was thinking if there was a "clean install" option it would fix that issue.

I'm not sure if it's because it doesn't have an extension on it, so maybe UMM is seeing it as a folder instead of a file so it doesn't overwrite or what but it's the only one that doesn't seem to update when someone drags and drops the zip into UMM. The .dll and .json do though.

The bundle file contains all the 3d assets for the mod.

If a user deletes the mod from the mod folder and then reinstalls it, it's not an issue.

[newman55]

The archives do not support multi-mods. If you combine all the folders, I think it will work.

[AndrewBeeman]

Ah I see. The other issue is that there are multiple files with the same names so, that wouldn't work.

I guess the best approach then would just to separate the main mod and its dependencies and have each part separate.

It works quite well with multi mods in the same zip, gives them each a different entry in the manager and whatnot it's just those 'bundle' files that are the problem child.

Thank you for the help, I will do that from now on.

[newman55]

During a clean installation, the manager unpacks all files. But when updating, it reads the first modInfo it comes across and updates the files based on it