Skip to content

List Specification #579

Description

@GrygrFlzr

List features:

  • Basic Search - slightly more advanced than Ctrl+F by looking for matches that begin or end with the query. This prevents iron from matching environment, but may be undesired. Possible to remove, considering I've seen bacon_donut use Ctrl+F instead of the web search in his streams
  • Advanced Search - more granular, specifying fields like mod name etc to query.
  • Dependency linking - click to go to the mod

It may be better to also have a separate mod page for each mod.

This is what each mod should ideally have:

  • Mod Name
  • Release status - Released, Alpha/Beta/Development (or perhaps just one generic catch-all)
  • Author(s)
  • Links and link type - MCF thread, main site, github repo, forums, OpenEye, etc.
  • Description
  • Dependencies - other mods, may inherit instead of being redundant?
  • Forge compatibility status - should be separated from Dependencies
  • Last modified timestamp
  • Tags - More of a future plan, may follow CurseForge tags/categories

Every part of the mod entry can change between Minecraft versions.

In the current format:

  • Only one link can be used, with an additional "source" field for a repository.
  • Forge compatibility is mixed with dependencies
  • No tags
  • An "other" field which is usually used as release status and a limited "tag": eg. API

"Feature requests"

  • Mod version - 1.0.0.112 - It is realistic to automatically track versions with a database driven site, especially with many mods being open source (118 mods on 1.7.10 at the time of writing).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions