Burning_TNT
Burning_TNT
[Bug] Installing `SNAPSHOT` versions of LiteLoader fails on first try if download source is `Mojang`
> From the logs, the logic of HMCL obtaining the LiteLoader version is consistent between the two download sources, but the file structure of the requested site when using Mojang...
[Bug] Installing `SNAPSHOT` versions of LiteLoader fails on first try if download source is `Mojang`
I see. `http://dl.liteloader.com/repo/com/mumfrey/liteloader/1.9.4/liteloader-1.9.4-SNAPSHOT.jar` this URL is created from: ``` { "repo": { "stream": "RELEASE", "type": "m2", "url": "http://dl.liteloader.com/repo/", "classifier": "" }, "artefacts": { "com.mumfrey:liteloader": { "571ad5e6edd5ff40259570c9be588bb5": { "tweakClass": "com.mumfrey.liteloader.launch.LiteLoaderTweaker", ......
[Bug] Installing `SNAPSHOT` versions of LiteLoader fails on first try if download source is `Mojang`
Maybe a hard coded download URL will be included into HMCL. :( Bad implementation
[Bug] Installing `SNAPSHOT` versions of LiteLoader fails on first try if download source is `Mojang`
怀疑在 2025 年继续支持 LiteLoader 的必要性 :)
If the latest version support both Fabric and NeoForge, why can't HMCL update the mod to this version?
It's strange that HMCL seems not to have checked the mod loader type. It will take longer time.
Could you provide a screenshot on the local mod list page for mod AmbientSounds_FABRIC_v6.0.2_mc1.20.6.jar?
> > Could you provide a screenshot on the local mod list page for mod AmbientSounds_FABRIC_v6.0.2_mc1.20.6.jar? > > @burningtnt > > [HMCL-dev@`e0ecd5e`](https://github.com/HMCL-dev/HMCL/commit/e0ecd5e69599041a6d5b3c9eb42dee26fbd84f10), [HMCL-dev/HMCL/actions/runs/9547498968](https://github.com/HMCL-dev/HMCL/actions/runs/9547498968) > > Preview > _Image_ Could you...
It's strange that HMCL consider this mod as a NeoForge mod.
> @burningtnt > > Preview > _Image_ I suppose this bug is because AmbientSounds_FABRIC_v6.0.2_mc1.20.6.jar supports both Fabric and NeoForge. And HMCL only consider whether is support NeoForge.