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
Some users have expressed concerns regarding the visibility of packages that don't explicitly provide playable content, such as what we currently tag as API/Library
This has been raised a couple of times in a few different ways, and usually it's because end users don't immediately see the use of such packages, and only perceive the hassle of needing to install them, and manage them when used as dependencies, and of course, when they occupy space in the mod list that would otherwise be held by a package that offers playable content (which I assume is perceived as adding more value to the non-dev user).
Solutions
Add a setting to hide API/Library tagged packages from the browsing experience in the CDB, I assume this would also allow for the posibility to allow users to hide other tags they don't want to see
The following would require engine modification, which while out of scope for this issue, I'll mention regardless:
Add a setting in the client to hide API/Library packages, while still allowing users to download these packages when they are required by another package, as well as making them visible when installed (so the user can uninstall).
The text was updated successfully, but these errors were encountered:
It's worth noting that CDB does not currently have a way for an author to indicate whether a package is solely an API/Library, or simply contains an API/Library.
We can't use the presence of other tags because they're often used orthogonally to this. For instance, "API/Library" + "Weather" would be the correct tags to use for both a package that is an API for weather, and for one that provides a weather system that includes a significant public API.
The idea of adding a Tag or Warning Flag for something like "developer audience only" or "no player UX" or something could work for this, though we would still need to get it applied to a whole bunch of existing packages, as well as making sure that future packages apply it correctly (it will "matter" more than normal informational-only tags).
Problem
Some users have expressed concerns regarding the visibility of packages that don't explicitly provide playable content, such as what we currently tag as
API/Library
This has been raised a couple of times in a few different ways, and usually it's because end users don't immediately see the use of such packages, and only perceive the hassle of needing to install them, and manage them when used as dependencies, and of course, when they occupy space in the mod list that would otherwise be held by a package that offers playable content (which I assume is perceived as adding more value to the non-dev user).
Solutions
API/Library
tagged packages from the browsing experience in the CDB, I assume this would also allow for the posibility to allow users to hide other tags they don't want to seeThe following would require engine modification, which while out of scope for this issue, I'll mention regardless:
The text was updated successfully, but these errors were encountered: