-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add supports
field.
#11
Comments
So, I think we should have this. One of the most common questions I see is "does it have TweakScale integration", or "does it work with ReaismOverhaul"? Crawling over forums to find that is tiresome and not always productive. An explicit supports field answers these questions. In a possible awesome future, users can right-click on a mod in the So even though this is the weakest relationship of all, I think it's still useful to have. (And completely optional) |
Flipping this to an actionable issue, but feel free to say that we shouldn't have this if you disagree. I'm just trying to maximise future global utility. ;) |
Add a --all option to upgrade.
Co-authored-by: DasSkelett <DasSkelett@users.noreply.github.com>
We currently have arecommends
list, does it make sense to have asupports
list? This would be useful for things like TweakScale or RealismOverhaul, which provide support for a wide range of mods, but which don't necessary recommend them.Having a
supports
field allows quick and machine-friendly answers to questions like "does this work with TweakScale", which is possibly the number one question I've seen asked of any mod I follow.The rich metadata side of me wants this very much, and wants to include it even if we don't use it in initial implementations. The getting things done side of me says that this is a distraction and I should go back to coding. :)The text was updated successfully, but these errors were encountered: