Metadata.DEFAULT_CLIENT_FILE_API is now https://maven.dandanton.com/repository/tdlm-client (the Nexus raw repository the pack publishes to, read through the CDN host). It was https://packages.dandanton.com/tdlm-client/latest, which answers 404.
First-launch auto install (Controllers.tryInstallBundledModpack): a failed or malformed manifest used to only log a warning. It now shows the error and opens the import wizard, the same behaviour as Instances.installServerModpack().
Why
A player who downloads only HMCL gets an empty launcher when the built-in manifest address is wrong. After this change a fresh HMCL fetches server-manifest.json from the new address and opens the Server Modpack install wizard. Later updates read the fileApi stored in the installed manifest, so they were already correct for packs built after TDLMPack #226.
<!-- claude-projects-attribution -->
_Requested by **Ethyn** · [project thread](https://claude.ai/code/project/chan_01DUNCDJLEksDHKpX5X5cThi?thread=cmsg_01DUNCDJLEksDHKpX5X5cThiRvLTuoiW2aLrdEVjHKAwbz)_
## What
- `Metadata.DEFAULT_CLIENT_FILE_API` is now `https://maven.dandanton.com/repository/tdlm-client` (the Nexus raw repository the pack publishes to, read through the CDN host). It was `https://packages.dandanton.com/tdlm-client/latest`, which answers 404.
- First-launch auto install (`Controllers.tryInstallBundledModpack`): a failed or malformed manifest used to only log a warning. It now shows the error and opens the import wizard, the same behaviour as `Instances.installServerModpack()`.
## Why
A player who downloads only HMCL gets an empty launcher when the built-in manifest address is wrong. After this change a fresh HMCL fetches `server-manifest.json` from the new address and opens the Server Modpack install wizard. Later updates read the `fileApi` stored in the installed manifest, so they were already correct for packs built after TDLMPack #226.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The default pointed at packages.dandanton.com/tdlm-client/latest (404), so the first-launch auto install
silently did nothing. It now points at https://maven.dandanton.com/repository/tdlm-client, and a failed or
malformed manifest shows an error and opens the import wizard (same behaviour as the Start menu install).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
layue13
merged commit f5d739711d into main2026-11-10 08:28:40 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Requested by Ethyn · project thread
What
Metadata.DEFAULT_CLIENT_FILE_APIis nowhttps://maven.dandanton.com/repository/tdlm-client(the Nexus raw repository the pack publishes to, read through the CDN host). It washttps://packages.dandanton.com/tdlm-client/latest, which answers 404.Controllers.tryInstallBundledModpack): a failed or malformed manifest used to only log a warning. It now shows the error and opens the import wizard, the same behaviour asInstances.installServerModpack().Why
A player who downloads only HMCL gets an empty launcher when the built-in manifest address is wrong. After this change a fresh HMCL fetches
server-manifest.jsonfrom the new address and opens the Server Modpack install wizard. Later updates read thefileApistored in the installed manifest, so they were already correct for packs built after TDLMPack #226.🤖 Generated with Claude Code