-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] HMCL merge the wrong launch arg when using Cleanroom #3528
Comments
我测试 HMCL 启动通过 Cleanroom 的安装程序安装的版本,结果启动并没有问题? 录屏、启动脚本和 Client JSON:https://www.123865.com/s/82uajv-DW2xH |
我的测试中,由于库的顺序问题,0.2.4-alpha可以正常运行,但只是恰好如此
|
那官方启动器的逻辑是啥 |
不知道 |
https://zh.minecraft.wiki/w/Tutorial:编写启动器#额外的版本json文件
根据 Wiki 中的描述, HMCL 的 inheritsFrom 逻辑并没有问题,我觉得 Cleanroom Installer 该想办法迎合 Wiki 逻辑? |
我们只做了MMC系启动器的官方支持,因为MMC系能通过patches文件夹分发完全不同的原版JSON,从而能直接删掉各类过期库和patchy |
因为最新 cleanroom 的 lwjgl 是 lwjglx 动态 merge 来的 |
早在这之前就有ICU4J爆炸的事了 |
那是不是说,cleanroom 都没法让官方启动器启动?(我买没测) |
平台 | Platform
Windows 11
问题描述 | Bug Description
version instance json
https://mclo.gs/dizgjNC
installer version json
https://mclo.gs/HCoXOIQ
We can see that hmcl simply merged the libraries, causing unexpected errors. lwjgl3 and lwjgl2 both existed during the run.
And other libs, guava, fastutil, exists...
Perhaps HMCL should exclude repeated artificial
启动器崩溃报告 / 启动器日志文件 | Launcher Crash Report / Launcher Log File
Non,HMCL dont crash.
The text was updated successfully, but these errors were encountered: