Skip to content

Give users the choice to hide packages tagged as API or Library #544

@Dragonop

Description

@Dragonop

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

  • 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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions