You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that if you specify version X.Y.Z for a mod dependency, even if you don't pick newest, Knossos treats the Z requirement as an >= test rather than an == test. This has caused a lot of problems with mods making changes they viewed as minor fixes that caused major headaches down the chain, most often with BP-dependant mods after BP adapts to new MVPs versions.
It's possible to force knossos to be pickier, but only with direct edits to the mod.json file, and these edits seem to cause issues at the downloading stage. It'd be much preferable to have a built in, supported strict versioning option.
The text was updated successfully, but these errors were encountered:
I'd actually like to enforce a == check for all dependencies except FSO. That would simplify the dependency logic in Knossos and probably fix a lot of installation issues. However, that means that after a new MVPs release, all mods that use them (AKA most) will have to update their mod dependencies.
It appears that if you specify version X.Y.Z for a mod dependency, even if you don't pick newest, Knossos treats the Z requirement as an >= test rather than an == test. This has caused a lot of problems with mods making changes they viewed as minor fixes that caused major headaches down the chain, most often with BP-dependant mods after BP adapts to new MVPs versions.
It's possible to force knossos to be pickier, but only with direct edits to the mod.json file, and these edits seem to cause issues at the downloading stage. It'd be much preferable to have a built in, supported strict versioning option.
The text was updated successfully, but these errors were encountered: