[1.2.9] (I think?) Launcher Bug - Force Update not fully removing old mod version

[mjevans]

I too experienced the 'duplicate mods' screen (on Linux, but it's been reported on Windows and Mac as well) when updating the Direwolf20 1.6.4 pack from release 1.0.0 to 1.0.2 ; this issue also persisted across a forced update.

It is not unreasonable for a Force Update to nuke and pave the mods folder (and possibly some other files); it should /force/ a clean default installation. There should either be an option to force a config update standalone or to include that with 'force update'.

Also, when forcing the update I had to (on my slow connection) re-download the pack even though there was a perfectly good local cache. The local cache should be verified by size, checksum, and successful parsing verification (does this read the way the launcher expects with no errors); only of those fail should the asset be re-downloaded.

 

[mjevans]

This bug still exists in launcher version 1.3.0 (observed updating the DW20 1.6.4 pack from 1.0.2 to 1.0.3)
* Force Update still does not cache valid asset files
* Force Update still does not remove old versions of the mods
** Thus the asset cache and install location
(turn on debugging under advanced options, the asset cache is under dynamicLoc + baseLink then up one folder; the install path is under installPath)
You must close the launcher, then delete the 'asset cache' folder for the DW20 1.6.4 pack and also delete the mods folder within the installPath.
You will, after completing the above need to Force Update to make the FTB Launcher rebuild the install location's mods folder.