制作：【柱子工作室】博哥

【柱子工作室】三国全战REX跳出诊断工具v1.0

下载点击：

中文使用说明

一、这个工具能做什么

本工具收集 REX 三国游戏的跳出线索，并生成一份便于转发的 TXT 诊断报告。
报告会整理运行日志片段、崩溃报告、有关配置、文件校验信息，以及所选的系统信息，供后续人工分析。

这是诊断工具，不是自动修复补丁。它不会启动游戏、修改游戏配置、替换资源或修改存档，也不会自动上传报告。它不读取存档内容或内存转储内容。

二、运行要求与放置位置

适用于 Windows 10 / Windows 11 64 位系统。免安装，不需要另行安装 Python，一般不需要管理员权限。

1. 将整个发布包解压到一个可正常读写的文件夹，不要直接在压缩包里运行。
2. 可以将工具放在含 REX.exe 的游戏根目录中，方便自动识别。
3. 也可以将工具放在其他位置，运行后手动选择含 REX.exe 的游戏文件夹。
4. 如果电脑上有多份游戏，请核对界面中的目录，选择刚刚出现跳出的那一份。

三、什么时候运行

游戏跳出后，请尽快运行本工具，最好在重新启动游戏之前生成报告。重新启动游戏可能覆盖或追加日志，使本次故障更难辨认。

如果已经重启过游戏，仍然可以诊断，请在补充说明中写明。若记得跳出的时间，请尽量准确填写；不确定时可以留空，不必猜测一个时间。

四、如何生成报告

1. 双击诊断程序，确认或选择游戏目录。
2. 选择这次跳出发生的阶段和出现规律。
3. 填写大致跳出时间；如有必要，补充战役、势力、地点、近期安装的补丁、报错文字，以及是否只有同一场战斗会出问题。
4. 检查下面两项采集选项，然后点击“生成诊断报告”。
5. 等待完成，使用“打开 TXT”查看报告，或使用“打开报告文件夹”找到文件。
6. 将生成的 TXT 文件作为邮件附件发给我，说明你遇到的问题。

界面支持中文和 English 切换。切换语言时可以保留已输入的游戏目录、时间、补充说明及所选选项，不需要重新填写；你自己输入的文字不会自动翻译。

五、两项默认勾选的选项

【深度扫描整个日志】默认勾选
按小块依次读取日志，以便发现较早的错误线索。日志越大，耗时可能越长；程序不会把整个大日志一次性加载到内存。
取消勾选后改为快速检查：主要读取日志开头 128 KB 和末尾 32 MB，小文件会完整读取。报告会标明扫描范围，未扫描的中间部分可能包含其他线索。

【附带硬件、显卡驱动及相关 Windows 错误记录】默认勾选
有助于核对系统环境，以及当前游戏安装的相关错误事件。
取消勾选后会跳过这部分采集，仍然检查游戏日志和配置，但系统层面的证据会减少。

采集过程中可以点击“取消”。程序会停止本次检查，不生成本次未完成的诊断报告；此前已经生成的报告不会因此被删除。

六、报告保存在哪里

默认保存到诊断程序旁边的“诊断报告”文件夹，文件名包含生成时间和区分标记，扩展名为 .txt。

如果程序所在位置无法写入，会尝试保存到当前用户目录下：
Documents\REX诊断报告

以程序完成后显示的实际保存位置为准。本工具的诊断输出仅为 TXT，不会覆盖已有的同名报告，也不会把整份大日志、存档或内存转储一起打包。

七、如何联系与发送

请先打开报告检查内容，再将 TXT 文件作为附件，通过邮件发给我：
156552351@qq.com

也可以QQ群内联系：懒得起名字了（博哥）

三国全战 柱子官方①群号：83206016（已满）
三国全战 柱子官方②群号：1121917026

工具不会代你发送邮件，也不会自动上传报告。你需要自行使用邮箱或聊天工具发送。请尽量直接发送原始 TXT 文件，避免只发截图或复制少量结论，以免遗漏定位所需的证据。

八、如何理解诊断结果

报告中的“定位”表示发现了某个故障环节或相关线索，不代表已经证明唯一原因，也不代表已经修好。

旧崩溃报告可能随游戏文件一同下载；修改时间较新，也不一定是你这次产生的错误。工具会尽量根据报告内部时间、游戏路径和你填写的时间进行区分。时间未确认、路径不匹配或证据不足的项目会保留相应说明。

报告只包含有范围限制的证据，不是游戏文件的完整副本。未知版本、特定地图、兵模或存档相关问题，可能还需要指定的原始文件或进一步复现信息；不能保证仅凭一份 TXT 就能做出有效补丁。

九、免责声明

本游戏为免费分享，本人虽然愿意尽力提供帮助，但精力、能力确实有限，可能不能及时回复或者技术原因不能解决，敬请包涵^.^

English Instructions

1. What this tool does

This tool collects evidence about crashes in REX Three Kingdoms and produces a TXT diagnostic report that you can share for manual investigation.
The report includes selected game-log excerpts, crash reports, relevant settings, file checksums and, if selected, system information.

This is a diagnostic tool, not an automatic repair patch. It does not launch the game, change game settings, replace resources or modify saved games. It does not read saved-game contents or memory-dump contents, and it does not upload the report automatically.

2. Requirements and where to put the tool

Windows 10 or Windows 11, 64-bit, is required. No installation or separate Python installation is needed. Administrator rights are generally not required.

1. Extract the complete release package to a folder that you can read and write. Do not run the tool directly from inside the archive.
2. You can place the tool in the game’s main folder containing REX.exe so that it can detect the game folder automatically.
3. You can also keep the tool elsewhere and select the folder containing REX.exe manually.
4. If you have several game installations, check the displayed folder and select the installation that just crashed.
5. When to run it

Run the tool as soon as possible after a crash, preferably before restarting the game. Restarting may overwrite or append to the logs, making the original incident harder to identify.

If you have already restarted the game, you can still run diagnostics; mention the restart in your notes. Enter the crash time as accurately as you can. If you are unsure, leave it blank instead of guessing.

4. How to generate a report

1. Double-click the diagnostic program and confirm or select the game folder.
2. Select the stage at which the crash happened and whether it repeats consistently or occurs randomly.
3. Enter the approximate crash time. If useful, add the campaign, faction, location, recently installed patches, error messages, and whether only one particular battle is affected.
4. Review the two collection options described below, then click the button to generate a diagnostic report.
5. Wait for completion. Use the button to open the TXT report or the button to open its folder.
6. Email the generated TXT file to me as an attachment, together with a description of the problem.

The interface can be switched between Chinese and English. Your game-folder selection, time, notes and selected options can be retained when you switch languages, so you do not need to enter them again. Text you entered yourself is not translated automatically.

5. The two options enabled by default

Deep scan of the entire log — enabled by default
This reads the log sequentially in small chunks to find earlier error evidence. Large logs may take longer to scan; the entire log is not loaded into memory at once.
If you turn this option off, the tool uses a quick scan: it reads mainly the first 128 KB and the last 32 MB, or the entire file if it is small. The report states which ranges were scanned. Unscanned middle sections may contain additional evidence.

Include hardware, graphics-driver information and relevant Windows error events — enabled by default
This helps identify the system environment and relevant error events associated with the selected game installation.
If you turn this option off, that information is skipped. The game logs and settings are still checked, but less evidence about the system environment will be available.

You can cancel an ongoing check. The tool stops the current check without producing its unfinished diagnostic report. Previously generated reports are not deleted when you cancel.

6. Where the report is saved

By default, the report is saved in a folder named 诊断报告 next to the diagnostic program. Its filename includes the generation time and an identifying suffix, and its extension is .txt.

If that location cannot be written to, the tool tries the following location in the current user’s profile:
Documents\REX诊断报告

Use the actual location shown by the program after completion. The diagnostic output is a TXT file only. Existing reports with the same name are not overwritten. The tool does not bundle the full large log, saved games or memory dumps with the report.

7. Contact and sending the report

Open and review the report before sharing it. Please email the TXT file to me as an attachment:
156552351@qq.com

You can also contact the QQ group administrator: 懒得起名字了.

The tool does not send email on your behalf or upload reports automatically. You must send the file yourself using your email or chat application. Please send the original TXT file where possible, rather than only a screenshot or a few copied conclusions, so that useful evidence is not omitted.

8. How to interpret the results

A diagnostic finding identifies a crash stage or a relevant clue. It does not necessarily establish the sole cause, and it does not mean the problem has already been fixed.

Old crash reports may have been included in the downloaded game files. A recent file-modification time does not prove that a report belongs to your latest crash. The tool uses the report’s internal time, game path and the time you entered where available. It retains qualifications when times are unconfirmed, paths do not match or the evidence is insufficient.

The report contains evidence collected within stated limits; it is not a complete copy of the game files. An unknown version or a problem involving a particular map, unit model or saved game may still require specific original files or further reproduction details. A single TXT report is not guaranteed to be sufficient to create an effective patch.

9. Disclaimer

This game is shared free of charge. Although I am willing to do my best to help, my energy and abilities are limited. I may not be able to reply promptly or resolve an issue for technical reasons. Thank you for your understanding ^.^