> For the complete documentation index, see [llms.txt](https://docs.xrmsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xrmsoft.com/xrmseries-3/hs2logparser.md).
# 日志分析工具
## HS2 Log 解析器
基于 BepInEx 运行日志的 HoneySelect2 zipmod 智能管理工具。
### 为什么需要它？
当你的 mods 文件夹积累了成千上万个 zipmod，游戏启动越来越慢，你可能会想清理——但手动排查几乎不可能：
* **文件查重**误判率高，同名不同版本、同 mod 换马甲都查不准
* **逐个试加载**效率极低，几万个 mod 无法逐一验证
* **盲目删除**风险大，删错了可能导致角色缺件、服装丢失
本工具的思路不同：**不扫描文件，而是读取游戏自身的加载日志**。
Sideloader 在每次启动时已经完成了全部检测——哪些 mod 缺少清单、哪些是其他游戏的、哪些 GUID 冲突只加载了最高版本。这些信息全写在 `LogOutput.log` 里，只是淹没在数万行日志中。本工具将其结构化提取、分类呈现、一键操作。
### 功能特性
#### 四类问题检测
| 类型 | 说明 |
| ----------- | ----------------------------- |
| Manifest 缺失 | zipmod 缺少清单文件，Sideloader 无法加载 |
| 游戏不匹配 | 其他游戏专用 mod 混入 HS2，已被自动跳过 |
| 多版本冲突 | 同一 GUID 存在多个版本，仅最高版本被加载，其余被跳过 |
| CAB 冲突 | AssetBundle 标识符冲突，可能加载失败 |
游戏不匹配 类型如果为 AI GIRL 可通过插件自动处理并正确加载，无需禁用或移除。除非他为 KK 或其他游戏类型。
如果您有更多日志类型请将 .log 文件提供给我们，此工具将持续完善。
#### 两种操作方式
| 操作 | 效果 | 可逆性 |
| -- | -------------------------------------- | ------------ |
| 禁用 | `.zipmod` → `.zipmod.xrm`，游戏不加载，文件保留原位 | 改回扩展名即恢复 |
| 移除 | 按原目录结构剪切到备份文件夹 | 备份管理器一键恢复到原位 |
#### 其他功能
* 拖拽导入日志，自动解析分类
* 文件状态实时检测（存在 / 已禁用 / 不存在）
* 批量选择 + 批量操作
* 搜索过滤
* 已禁用 mod 扫描与一键启用
* 备份管理器，按时间戳分组，支持单文件恢复
* Mods 目录和备份目录可配置，设置持久化保存
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.xrmsoft.com/xrmseries-3/hs2logparser.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
