Skip to content

new "disable unused dependencies" fails to consider previous enabled mods #142

@silvncr

Description

@silvncr

for example, right now i have 40 mods enabled

  • if i enable strawberry jam, it requires an additional 44 mods
  • but when i disable strawberry jam, it wants to disable 49 unused dependencies -- including some mods that were previously enabled

olympus doesn't store whether a given mod was enabled manually or automatically, making the "disable unused dependencies" feature feel a little pointless

mod presets are a workaround, but they don't feel comfortable to use -- you can't even edit them in-app after creation -- so i'd like to see a more integrated solution

related:

i've considered making an external program to solve all of these, but it really should be integrated into olympus

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions