-
Notifications
You must be signed in to change notification settings - Fork 11
[BUG] Old version of mods still not being removed after updated #91
Comments
Do you have a log file for me? |
latest.log |
latest_after.log |
That's a nasty bug. Looks like ModManager couldn't modify To bypass the Windows file lock, ModManager writes the text "MODMANAGER" into the jar so that fabric can't load it the next time. It looks like this hasn't worked here. I will need to setup a Windows VM to debug this more. Relevant log lines`latest.log`
|
This also happens to the other mods. I forgot to tell you that I recreated that bug thing by using Dynamic FPS mod instead of Ears mod due to the game just crashed before launching for some reason |
Yeah can't currently not say why that's happening because Windows should normally allow programs to write to which are open in other programs. |
I cloud replicate it using the 1.1.1 version and the Minecraft launcher but not using the IDE. I need some further testing. |
Closes #91 Signed-off-by: DeathsGun <deathsgun@protonmail.com>
The PR didn't remove the problem completely |
When removing mods you may need to restart twice to get the mod to be not loaded again. |
Describe the bug
So I updated Ears mod then I restarted the game. But fabric just showed me this.
Duplicate versions for mod ID 'ears': [1.4.0 at /C:/Users/NoncanbeZaza/AppData/Roaming/.minecraft/mods/ears-fabric-1.17-1.4.0.jar], [1.3.0 at /C:/Users/NoncanbeZaza/AppData/Roaming/.minecraft/mods/ears-fabric-1.17-1.3.0.jar]
This means that the old version of the mod was still not being removed. I know this one is another one of #51, But this is still not being removed completely.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The game launched normally with the new version of mods without showing the duplicated mod error.
Please complete the following information:
The text was updated successfully, but these errors were encountered: