[Bug] 如果模组文件被其他进程占用的同时使用HMCL的模组管理功能禁用模组，HMCL并不会对模组文件进行实际操作。
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 10.1k
- Forks
- 934
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 82
Description
问题描述 | Bug Description
- 使用任意软件打开一个模组文件。
- 使用HMCL的模组管理功能禁用该文件。
- 再次检查这个模组文件，会发现模组依旧保持启用状态，而HMCL却显示模组已禁用（左侧的对勾消失）。
启动器崩溃报告 / 启动器日志文件 | Launcher Crash Report / Launcher Log File
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two-step scenario with the attached launcher log available, then trace HMCL's mod-management disable action; the payload names no source file or test. Done means the occupied mod file and HMCL's displayed enabled/disabled state agree after the operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100