EverestAPI / EverestAPI/Olympus

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

Open
#142 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Lua
Stars
179
Forks
41
Avg merge
2d 16h
Merged PRs (30d)
8

Description

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:
- #91
- #119

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.