Modpack mod metadata returns 'Unknown' latest version and stale Minecraft versions

Open
#112 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api, backend

Research direction

Start at the /api/mods/metadata endpoint and trace how it gathers mod versions for a Modrinth modpack instance. Check the metadata path for truncating mc_versions and resolving latest_version against the instance's Minecraft version and loader. Done when pack metadata includes current Minecraft versions and latest_version is a real version or absent.

Written by the indexing model from the issue text.

Description

bug

Problem

For a Modrinth modpack instance (e.g. MODRINTH_MODPACK=shingeki-no-kyojin), /api/mods/metadata returns stale data for nearly every mod:

  • latest_version: "Unknown" for every pack mod
  • mc_versions lists only the oldest few versions, e.g. Fabric API → ["18w49a","18w50a","19w02a"], Lithium → ["1.16.2","1.16.3","1.16.4"]

Reproduced against a live instance. Anything built on this data, such as update badges (#49, #7) or compatibility hints, will be wrong for modpack instances.

Related: #69 (pack mods missing until first start).

Expected

  • mc_versions holds the full list of supported versions, or at least the newest ones. It shouldn't be cut down to the first three.
  • latest_version is resolved for the instance's Minecraft version and loader, or left out entirely rather than set to "Unknown".

Acceptance

  • Metadata for pack mods includes current Minecraft versions.
  • latest_version is either a real version or absent.

Found in a premium product review of the dashboard.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.