Skip to content

Updating a modpack with disabled mods creates copies of the disabled mods #1233

Open
@jhymni

Description

@jhymni

What Operating System

Windows 10

Debug Code

https://pste.ch/etiwunonul

Describe the bug

Updating a modpack with disabled mods adds enabled .jars to the mods folder, but the mods still show up as disabled in the app. When I try to reenable the mods, I get an error ("Failed to enable [mod.jar]"). Deleting the new .jars fixes the issue.

Steps to reproduce

  1. Disable mods in a modpack
  2. Update the modpack

In the app, the mods show up as disabled, they are not, and you have to manually delete the .jar's the update added.

Expected behaviour

The update should either delete the .disabled files (enabling previously disabled files), or replace them with the updated files with .disabled appended.

Screenshots

No response

Additional information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @MichaelHillcox@jhymni

      Issue actions

        Updating a modpack with disabled mods creates copies of the disabled mods · Issue #1233 · FTBTeam/FTB-App