Skip to content
This repository was archived by the owner on Aug 27, 2026. It is now read-only.

MCSync 2.0.2

Choose a tag to compare

View all tags
@YU322142 YU322142 released this 25 Aug 08:47
· 1 commit to main since this release
v2.0.2
ff7768f

MCSync 2.0.2 发布说明 / Release Notes

发布日期 / Release date: 2026-08-25

中文

MCSync 2.0.2 是面向 OTA 稳定性和更新器自更新链路的兼容维护版。它保留 schema-v5 和技术 modId=mcmodsync，重点解决旧版更新器必须先完整理解新清单、导致自身无法更新的问题。

主要变更

  1. 独立前置自更新通道

    • 稳定清单旁新增 mcsync-bootstrap-v1.json。
    • 客户端先只验证 MCSync 自身的版本、发布序号、文件大小、SHA-256 和 JAR 身份。
    • 有更新时只下载 MCSync，游戏退出后原子替换；下一次启动才处理完整玩法 OTA。

  2. 严格但可兼容的入口策略

    • 前置清单尚未部署并返回 HTTP 404 时，旧客户端继续走兼容路径。
    • 前置清单已经存在但格式、版本、大小、SHA-256 或下载失败时严格阻止，不自动绕过安全检查。
    • 发布序号仍执行单调防降级和同序号分叉保护。

  3. 发布器自动生成

    • 发布工作台从唯一的必需、本地托管 modId=mcmodsync JAR 自动生成前置清单。
    • MCSync 自身不依赖 Modrinth、CurseForge 或镜像站解析。
    • 发布指南明确要求先上传内容对象和前置清单，最后替换 mods-v5.json 稳定入口。

  4. 平台镜像回退修复

    • 旧清单把 Modrinth 官方 CDN 地址标记为镜像时，客户端会回退到固定官方地址。
    • 每个回退候选仍必须通过清单锁定的 SHA-256 和文件大小校验。

兼容说明

  • 技术 Mod ID 仍为 mcmodsync，旧的 1.9.x/1.6.x 网关仍可识别。
  • modRemovals 的最低兼容版本仍为 2.0.1；2.0.2 不改变既有 schema-v5 清单格式。
  • 旧客户端第一次跨越到独立前置通道时，仍需要一次可被旧版本读取的过桥更新；完成后后续更新不再依赖旧版完整清单解析能力。

English

MCSync 2.0.2 is a compatibility maintenance release focused on OTA reliability and updater self-update behavior. It preserves schema-v5 and the technical modId=mcmodsync, while removing the circular dependency that required an old updater to fully understand every future release before updating itself.

Highlights

  1. Independent updater bootstrap lane

    • Added mcsync-bootstrap-v1.json beside the stable manifest.
    • The client first verifies only the MCSync version, release sequence, file size, SHA-256, and JAR identity.
    • When an update is needed, only MCSync is downloaded and atomically committed after exit; the full gameplay OTA runs on the next launch.

  2. Strict but compatible endpoint policy

    • An undeployed bootstrap endpoint returning HTTP 404 keeps the legacy compatibility path.
    • Existing but malformed, divergent, size-invalid, hash-invalid, or failed bootstrap data blocks safely instead of bypassing verification.
    • Release sequences still enforce monotonic anti-downgrade and same-sequence fork protection.

  3. Automatic publisher generation

    • The publisher derives the bootstrap from the single required, publisher-hosted modId=mcmodsync JAR.
    • MCSync itself never depends on Modrinth, CurseForge, or mirror resolution.
    • Deployment guidance now uploads content objects and the bootstrap before atomically replacing mods-v5.json.

  4. Platform mirror fallback fix

    • If an older manifest labels a Modrinth official CDN URL as a mirror, the client falls back to the exact pinned official URL.
    • Every fallback candidate remains locked to the manifest size and SHA-256.

Compatibility

  • The technical Mod ID remains mcmodsync; legacy 1.9.x and 1.6.x gateways remain recognizable.
  • The modRemovals minimum compatibility version remains 2.0.1; 2.0.2 does not change schema-v5 semantics.
  • A legacy client still needs one readable bridge update to enter the independent bootstrap lane; after that, future updates no longer depend on old full-manifest parsing.
Assets 5
Loading