HMCL-dev / HMCL-dev/HMCL

[Feature] 导出的<服务器自动更新整合包>中,针对已有mod索引依旧使用索引从curseforge/modrinth下载

Open
#5,241 8 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
10.1k
Forks
934
Avg merge
1d 5h
Merged PRs (30d)
82

Description

概述 | Summary

目前导出的<服务器自动更新整合包>中,会把mods全部二次分发一遍, 而如果整合包本身是使用curseforge封装格式,包含manifest.json&&modpack.cfg,
故可以将<服务器自动更新整合包>中导出的mods依旧使用原curseforgeAPI(如对应mod封装时依然存在)
而对少量无法链接到curseforge的模组可正常封装进去
类似于packwiz的做法(https://packwiz.infra.link/)

原因 | Reason

1.减少模组二次分发
2.缩小封装的包的大小
3.减少对更新源的带宽依赖
4.提高导出的效率

详情 | Description

见Summary

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading how exported server auto-update packages use manifest.json and modpack.cfg, then trace the existing CurseForge and Modrinth download paths. Done means indexed mods continue to resolve from their original source when available, while mods that cannot be linked are bundled normally, with the package remaining usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.