mckyby 创建的主题

前情摘要：DeepseekMirai

*由于某人比较懒，在以下内容中DSMR指上述DeepseekMirai，STMR指这个SillyTavernMirai

================================= 鉴于有人喜欢玩酒馆，喜欢那里的角色扮演，喜欢那里的角色卡，喜欢那里的。。。。 于逝！ STMR(Silly-Tavern-Mirai)，它，来了！

简单来说，这个东西就是 DeepseekMirai的改版，添加了一个按照角色卡补齐System字段作为提示词的功能，支持了由关键词触发的世界书，和角色首句回答的功能，旨在优化输出内容，让它看起来更加符合这个角色的人设。如果不知道什么是酒馆，可以去尝试一下，或者是直接下载这个仿的不怎么像的酒馆插件来体验一下哦~

================================= 如何使用？ 如果你没有用过DeepseekMirai，或者是其他http-api外接插件： 从http-api的Release页面下载这个插件，将它丢进mirai的plugins文件夹。 丢进去以后，重启一下Mirai，当完全正常启动后(或者自动创建配置文件后)再次关闭，在mirai的config文件夹里修改http-api的配置文件，以下是示例，可以直接粘贴哟（但是建议把密钥[verifyKey]改成你自己随意设置的密钥）： adapters: - http - ws enableVerify: true verifyKey: 387060b9324b317f53c3cc674fa6c3c5 debug: false singleMode: false cacheSize: 4096 adapterSettings: http: host: 0.0.0.0 port: 52013 cors: ["*"] unreadQueueMaxSize: 100 ws: host: 0.0.0.0 port: 52013 reservedSyncId: -1 接下来，正常启动Mirai，这一部分的配置就完成了！ 熟练使用http-api？

那可以完全忽略以上内容咯，接下来我们开始部署SillyTavernMirai！

首先，下载好对应系统版本的可执行文件（如何下载见文末），直接运行，按照提示，依次输入要求提供的必要信息。

ca8874b5-7c48-4bde-b738-72a122ab457e-image.png

按回车退出后，重新运行插件，直到显示✦ 开始工作....（这里是pre1.0e6版本）

507e037a-2dd3-47ea-9d6d-d0fe45442cbd-image.png

如果出现报错，或者说是闪一下就自动退出了，那么就有可能是你的http-api配置的有点问题。 显示✦ 开始工作....后，和机器人私聊使用%chat 内容就可以与内置的角色卡：爱莉希雅进行对话啦！（这里是pre1.0e6版本，以后会内置什么可不一定哦） 在最开始时设置的管理员和机器人私聊使用%addg 群号或%addf QQ号就可以在这个群或私聊里使用%chat 内容进行对话了哦！ 进阶操作：

SillyTavernMirai的配置文件和DeepseekMirai几乎一样，但是不能通用(悲)

{ "code": "0", "host": "你的api插件地址，只支持http/s协议，末尾要带斜杠/", "verifykeys": "你的api插件的密钥", "botqq": "绑定的机器人", "deepseekapiaddress": "https://api.deepseek.com", "deepseekapikey": "AI平台的api密钥", "deepseekapimodel": "使用的大模型", "requesttimeSleep": "刷新消息延迟，默认为1秒，过长可能出问题，int，{x|10≥x≥1,x∈N*}" "enableTokenCounting": "是否开启“%usage”一键查token，true/false" "tipsA0": "不知道这里会出现什么文字", "listenGroups": [ "监听群" 123456, 789109 ], "listenFriends": [ "监听好友" 10000, 10011 ], "blockuserList": [ "黑名单，对管理员也有效。" 12345678 ], "adminMode": "是否为白名单模式，仅有管理员们可以在任何群(即使没被添加检测)随意触发。true/false", "atUser": "回复中是否@这个用户，true/false", "sendUserInfo": "发送用户信息，在STMR中暂时无效，未来看情况是修上还是砍掉", "BetterUserInfo": "是的没座，这是还没发布的DSMR中的新功能，在STMR中暂时无效", "BetterUserInfoMessage": "是的没座，这是还没发布的DSMR中的新功能，在STMR中暂时无效", "analyzeUserInfoPrompt": "在STMR中暂时无效", "ATmessagePrefixs": [ "拆开长句时自动补上的前缀，不喜欢可以全清空，但是必须要有11个空" ], "showblockMessages": "是否回复被拉黑的用户，true/false" "atBot": "触发时是否需要@bot，true/false" "breaklongSentence": "拆开长句，分散发送，true/false" "RadicalOptimization": "激进的优化，流式发送消息，大幅提高长句响应速度，true/false", "commandPrefix": { "answerUser": "%chat，触发普通对话的前缀，留空并开启atBot为仅@触发", "adminQQs": [ "管理员列表，还是第一位最 权威 ", "112121" ], "tipsA1": "以下命令只有管理员QQ可以触发，除了changeCard、changePersona、clearChatLog、memorySync之外每个命令均需要首位管理员才能触发。", "changeModel": "%model + 快捷名称，怎么用看前情摘要", "changeCard": "%chara + 角色名称(也就是角色卡文件夹的名称)，修改当前对话使用的角色卡", "changePersona": "%persona + 用户信息(是用来向AI描述用户(也就是你)的提示词)，修改当前对话使用的用户描述信息", "clearChatLog": "%rmrf ，清空当前对话内容", "checkApiBalance": "%apibalance ，查询密钥余额，仅支持deepseek", "addBlackList": "%black + QQ号，拉黑一个用户", "memorySync": "%memory + 群号/QQ号 ，加载其他群的对话历史，也可以 + saves/保存的名字 来加载保存的对话历史", "memorySave": "%save + 保存的名字(可选) ，保存当前对话历史到saves目录", "addFriendsList": "%addf + QQ号，添加一个检测好友", "addGroupList": "%addg + 群号，添加一个检测群", "addAdmin": "%adda + QQ号，添加一个能换角色卡、删对话、加载对话的管理员", "checkTokens": "%usage ，查询当前对话历史的tokens使用量，因算法不够好导致与实际偏差较大" }, "savetime": 1746026115, "configVersion": 1.0 } 以上是全部配置文件，按照需要来修改吧！ 将"answerUser"设置为""并把"atUser"设置为True，即可实现在群里@机器人触发，私聊直接触发！ ================================= 我该如何添加角色卡？ 敬请期待，一键自动导入已经在路上了。。。 ================================= 从哪下载？ 由于还没有优化完全，目前还无法发布第一个版本，想试玩的可以加群，下载可能几分钟就会更新N次的测试版 点击链接加入群聊【斗🐔场(1028466667)】：

😋在论坛找了几圈，没找到可以拿来接AI的插件(还是说找的不仔细)，思来想去就弄了这么一个东西：DeepseekMirai。 🤓使用python编写，调用mirai-http-api控制收发信息。 🤔没有毒，不信可以去测测到底有没有 😭网不太好，不愿意用github，用魔法又被移动针对。想要源码可以直接找我要(虽然写的是一堆屎山) ================================ 2025-4-1 更新：

提取码:oHoM，点击下载 DeepseekMirai[1.31]（123云盘）

虽然是这一天更的新，但是还是希望没有人会开玩笑。
新增功能：
1.添加了聊天命令“%usage”，可以随时查看当前会话的总tokens使用量，将enableTokenCounting设置为True即可正常使用。（可能会稍微影响性能。）
2.自动骚扰！将chatMode更改成annoyingBot即可体验！！
3.“%model”命令改为了从配置文件(DsModelList.json)中加载模型，使用 %model 快捷名称 即可快速切换。首次使用自动创建deepseek的配置文件，可以自行添加修改。

{ "快捷名称": { "apiAddress": "api地址", "apiKey": "api密钥", "model": "使用的模型" }, 例如 "dsreas": { "apiAddress": "https://api.deepseek.com", "apiKey": "sk-666", "model": "deepseek-reasoner" } }

4.可以在配置文件(DsModel.json)中修改到更多的api参数，比如说重复惩罚，但是请去官网的文档学习一下怎么配置哦！
5.优化了传给AI的用户信息，包含群名、群u是否是管理员、是否@bot等。
6.高仿的Mirai后台输出

已知问题：
1.annoyingBot模式下不会响应任何命令，你执行其他mirai 命令的消息也有概率被获取
2.可执行文件比以前“更大”了
3.%apibalance还是会报错，原因是==写错成in了，下个版本修复。
有没有什么新功能建议啊，要不然真的没法更新了

================================ 配置文件详解,兼任功能介绍： { "code": "0", "host": "你的api插件地址，只支持http/s协议，末尾要带斜杠/", "verifykeys": "你的api插件的密钥", "botqq": "绑定的机器人", "deepseekapiaddress": "https://api.deepseek.com", "deepseekapikey": "去Deepseek官网申请来的api密钥", "deepseekapimodel": "支持deepseek-chat和deepseek-reasoner", "requesttimeSleep": "(int)刷新消息延迟，默认为1秒，过长可能出问题," "enableTokenCounting":true, "是否开启“%usage”一键查token" "chatConfig": { "chatMode": "answerUser,已经支持answerUser(常规问答)和annoyingBot(自动骚扰)", "annoyingBotModeConfig": { "annoyingBotDefaultPrompt": "自动骚扰的默认提醒词，默认带的是骂人的", "hitChance": 60, "触发概率，范围1-100" "replyAlltime":[ "谁的触发概率是100%", 123456 ], "neverReply": [ "谁永远不会触发" 789012 ] }, "tipsA0": "没什么用(谁说json里写不了注释？)", "listenGroups": [ "监听群，两种模式均生效。" 123456, 789109 ], "listenFriends": [ "监听好友，两种模式均生效。" 10000, 10011 ], "blockuserList": [ "黑名单，仅常规模式生效，黑名单对管理员也有效。" 12345678 ], "showblockMessages": true,是否提醒被拉黑的用户 "atBot": false,触发是否需要@bot "atUser":false,回复中是否@触发者 "sendUserInfo": false,是否发送用户信息，仅群生效 "analyzeUserInfoPrompt": "",用来让AI识别并理解用户信息，且应用在回复中的提示词，两种聊天模式通用，会补在你的提示词的前面。 "ATmessagePrefixs": [],拆开长句时回复的那11个前缀，尽量不要动最后一个空 "adminMode":false,是否为白名单(管理员)模式 "breaklongSentence": true,把长句拆开，分开发送 "RadicalOptimization": false,所谓的“激进”优化，在拆开长句时生效。 "commandPrefix": { "answerUser": "%chat,触发提问的消息前缀，留空可以关闭触发前缀。", "adminQQs": [ "管理员QQ列表，第一位最牛逼。" 66666666666 ], "tipsA1": "以下命令只有管理员QQ可以触发，除了changePrompt、clearChatLog、memorySync之外的命令均需要首位管理员才能触发。", "changeModel": "%model,快速更改模型的命令前缀", "changePrompt": "%prompt,快速修改当前群/私聊提醒词的命令前缀", "clearChatLog": "%rmrf,删除当前会话聊天历史", "checkApiBalance": "%apibalance,查询已配置的API密钥的余额", "addBlackList": "%black,拉黑某用户的命令前缀", "memorySync": "%memory,大记忆恢复术(加载其他会话或保存的聊天历史)的命令前缀", "addGroupList": "%addg,添加检测群的命令前缀", "addFriendsList": "%addf,添加检测私聊的命令前缀", "memorySave":"%save,保存当前对话的命令前缀，没提供名字默认群号/私聊QQ号" "addAdmin":"%adda,添加管理员的命令前缀，只有管理员列表第一位能用" "checkTokens":"%usage,快速查询总token用量，但是有思维链的模型的思维链不会被计算" }, "defaultPrompt": "默认提醒词，没填就是猫娘咯" }, "savetime": 1743004265, "configVersion": 1.3 } MiraiHttpAPI该如何配置？

看见有人不会配置MiraiHttpAPI了，在这里贴上一份配置文件。

adapters: - http - ws enableVerify: true verifyKey: <你的密钥，可以随意设置> debug: false singleMode: false cacheSize: 4096 adapterSettings: http: host: 0.0.0.0 port: <绑定的端口> cors: ["*"] unreadQueueMaxSize: 100 ws: host: 0.0.0.0 port: <绑定的端口，可以与http端口相同> reservedSyncId: -1 过往内容：

没啥太大用了，点击展开即可查看。

... ================================ 2025-3-27更新:

提取码:zJ3Z，点击下载 DeepseekMirai[1.2]（123云盘）

稍微测试了一下，新功能全部好用！

配置文件内容更新:

请按照下方详解，重新修改配置文件
或查看修改详情：

太麻烦了，现在都是自动更新了！☺️
确保原有配置文件可读，运行第一次自动更新！

新增功能：

1.对于特别长特别长的回复做了一个"激进的"优化，同时设置breakLongSentence和RadicalOptimization为true即可体验！(其实就是优化了一下回复速度)
2.添加了可以把群友信息发送给AI的选项，设置sendUserInfo为true即可体验。该功能会自动把【群友群昵称(群友QQ号)】添加在发送给AI的内容的前面，并尝试修补提示词来让AI识别到用户的信息 (里面自带的可能不咋好用😭)
3.可以自定义设置在拆开的长句的前面的随机小前缀。(最后一位留空的是关闭拆开长句时的回复前缀，如果喜欢可以填上。)
修复问题:
1.每次升级后要手动更新配置文件，太麻烦了，改成自动升级了。
已知问题:

1"激进优化"下通1000问在回复中出现emoji会导致对话整个被截断，因为ds没问题所以怀疑是阿里的问题
2.在新运行自动创建配置文件的时候添加的管理员可能以str形式写入了配置文件，不知道会不会因此产生问题(?)
3.%apibalance用不了了，好像是验证出错。。

================================ 2025-3-13更新：

提取码:T61O，点击下载 DeepseekMirai[1.1]废.exe（123云盘）
提取码4NmD，点击下载 DeepseekMirai[1.1]（123云盘）
更新的有点着急了（笑），没怎么测试，但是我猜应该没什么问题吧（叉腰）
配置文件内容更新：
请按照下方详解，重新修改配置文件
或查看修改详情：
在chatConfig里加入了atUser，和adminMode两个布尔值，
在chatConfig.commandPrefix里加入了addAdmin 文本值，默认为"%adda"
当你遇到TypeError: startswith first arg must be str or a tuple of str, not NoneType这样的问题，就是没有更新配置文件导致的
新增功能：

1.多人同时触发回复时会在回复内容中@触发者，并在拆开的长句的每一句前面都加上了随机的小前缀(共11种)
2.加入了白名单模式，如果开启将只回复所有群中的被配置的管理员，其他任何人无法触发，私聊不受影响。
3.加入快捷添加管理员的指令，默认前缀为"%adda"
4.(链接2)新增可以自定义temperature和max_tokens的配置文件
下次许愿什么功能呢？
修复问题：
1.当一次性收到太多的消息时会出现多提供参数的问题，导致没有一条消息被回复。
2.(链接2)当不拆开长句时开启atUser导致消息链没有被正确组装

================================ 最开始的版本

提取码:qzhV，点击下载 DeepseekMirai-1.0.exe（123云盘）
(运行效果可能不太好，尽力了）
小提示：
1.将commandPrefix中的answerUser设置为空，同时打开atBot，可以做到@bot直接触发，无需其他前缀。私聊直接触发，无需@。
2.你可以去Deepseek官网的聊天页面，让它帮你生成人设，然后填到提醒词里，这样你就拥有了属于自己的"QQ智能体？"
3.如果愿意，可以加一下群哦 (虽然没啥人) ~ 1028466667

这年头，这么干净的号上哪找去 想试试自己的号干不干净？点击下载

干净到连个手机号都没有绑
QQ截图20250101131730.png

拿了一个新号登录，密码不正确会code=1，但是密码正确会出现

Login failed: Consuming(value=null)

完整日志

2024-02-24 11:52:44 W/console: 无法解析 MD5 为 MiraiProtocol > login 1145141919810 <md5> ANDROID_PAD 2024-02-24 11:52:58 I/KFCFactory: create EncryptService(id=1145141919810), protocol=ANDROID_PAD(8.9.96) by fuqiuluo/unidbg-fetch-qsign from file:///ntfs/mirai/KFCFactory.json 2024-02-24 11:52:58 I/KFCFactory: unidbg-fetch-qsign by http://yuanshenqidong.mihoyo:11451 about { "code": 0, "msg": "IAA 云天明 章北海", "data": { "version": "1.1.9", "protocol": { "qua": "V1_AND_SQ_8.9.96_5048_HDBM_T", "version": "8.9.96", "code": "5048", "package_name": "com.tencent.mobileqq" } } } 2024-02-24 11:52:59 I/UnidbgFetchQsign: Bot(1145141919810) initialize by http://yuanshenqidong.mihoyo:11451 2024-02-24 11:53:03 I/UnidbgFetchQsign: Bot(1145141919810) register, Instance loaded successfully. 2024-02-24 11:53:03 I/UnidbgFetchQsign: Bot(1145141919810) initialize complete 2024-02-24 11:53:05 I/Bot.1145141919810: Calculating type 2 PoW, it can take some time.... 2024-02-24 11:53:05 I/Bot.1145141919810: Got PoW result, cost: 142 ms 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] 需要滑动验证码, 请按照以下链接的步骤完成滑动验证码, 然后输入获取到的 ticket 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] Slider captcha required. Please solve the captcha with following link. Type ticket here after completion. 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] @see https://github.com/project-mirai/mirai-login-solver-selenium 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] @see https://docs.mirai.mamoe.net/mirai-login-solver-selenium/ 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] 或者输入 helper 来使用 TxCaptchaHelper 完成滑动验证码 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] Or type helper to resolve slider captcha with TxCaptchaHelper.apk 2024-02-24 11:53:05 W/Bot.1145141919810: [SliderCaptcha] TxCaptchaHelper 的在线服务疑似被屏蔽，可能无法使用。TxCaptchaHelper 现已无法满足登录QQ机器人，请在以下链接下载全新的验证器 2024-02-24 11:53:05 W/Bot.1145141919810: [SliderCaptcha] The service of TxCaptchaHelper might be blocked. We recommend you to download the new login solver plugin in below link. 2024-02-24 11:53:05 W/Bot.1145141919810: [SliderCaptcha] @see https://github.com/KasukuSakura/mirai-login-solver-sakura 2024-02-24 11:53:05 I/Bot.1145141919810: [SliderCaptcha] Captcha link: https://ssl.captcha.qq.com/template/wireless_mqq_captcha.html?style=simple&aid=16&uin=1145141919810&sid=2343551612600543265&cap_cd=yzPFw7X4Jr5Z4WlkPQRGr56HlP8EYzNw_4Crug-Zsf_M0WSCCHRY_w**&clientype=1&apptype=2 LOGIN> > t03uhU91hL31wdjEAavHpmkB62m3mxZuebrFCzocxpUJrN4sXQApkLtMx3UT9agMLgf5zDLp61YykUoevP0F6srIPvYApKxZpDlA46MHNHI9DspHdPMtUt3RiBCcr1Nz7gLNN8tab9zlRcAVT2BBBx3a97Svep9l5g-fFe8P7yPiDBeC-0mlTBRkgHYZ62ElWNDpZWd62j7Ag8* 2024-02-24 11:54:05 I/Bot.1145141919810: [SliderCaptcha] 正在提交中... 2024-02-24 11:54:05 I/Bot.1145141919810: [SliderCaptcha] Submitting... Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. 2024-02-24 11:54:07 E/console: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(1145141919810), code=1, title=登录失败, message=账号或密码错误，请重新输入。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(1145141919810), code=1, title=登录失败, message=账号或密码错误，请重新输入。, errorInfo=)] 2024-02-24 11:54:07 W/UnidbgFetchQsign: with CoroutineName(SendMessage) java.lang.RuntimeException: Bot(1145141919810) callback trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish at fix-protocol-version-1.13.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign$callback$1.invokeSuspend(UnidbgFetchQsign.kt:236) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Caused by: java.util.concurrent.CancellationException: net.mamoe.mirai.internal.network.components.LoginFailedExceptionAsNetworkException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.sendAndExpect$suspendImpl(SelectorNetworkHandler.kt:157) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.sendAndExpect(SelectorNetworkHandler.kt) at net.mamoe.mirai.internal.network.handler.NetworkHandler.sendAndExpect$default(NetworkHandler.kt:194) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt$createChannelProxy$1.sendMessage(OutgoingPacket.kt:328) at fix-protocol-version-1.13.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign$callback$1.invokeSuspend(UnidbgFetchQsign.kt:229) ... 6 more Caused by: net.mamoe.mirai.internal.network.components.LoginFailedExceptionAsNetworkException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:249) ... 6 more Suppressed: net.mamoe.mirai.internal.network.handler.selector.SelectorRequireReconnectException Caused by: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) ... 6 more Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(1145141919810), code=1, title=登录失败, message=账号或密码错误，请重新输入。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(1145141919810), code=1, title=登录失败, message=账号或密码错误，请重新输入。, errorInfo=)] 2024-02-24 11:54:07 I/UnidbgFetchQsign: Bot(1145141919810) destroy, Instance destroyed successfully. 2024-02-24 11:54:07 I/Bot.1145141919810: Bot cancelled: Bot closed > login 1145141919810 woshiaikun ANDROID_PAD 2024-02-24 11:54:29 I/KFCFactory: create EncryptService(id=1145141919810), protocol=ANDROID_PAD(8.9.96) by fuqiuluo/unidbg-fetch-qsign from file:///ntfs/mirai/KFCFactory.json 2024-02-24 11:54:29 I/KFCFactory: unidbg-fetch-qsign by http://yuanshenqidong.mihoyo:11451 about { "code": 0, "msg": "IAA 云天明 章北海", "data": { "version": "1.1.9", "protocol": { "qua": "V1_AND_SQ_8.9.96_5048_HDBM_T", "version": "8.9.96", "code": "5048", "package_name": "com.tencent.mobileqq" } } } 2024-02-24 11:54:29 I/UnidbgFetchQsign: Bot(1145141919810) initialize by http://yuanshenqidong.mihoyo:11451 2024-02-24 11:54:35 I/UnidbgFetchQsign: Bot(1145141919810) register, Instance loaded successfully. 2024-02-24 11:54:35 I/UnidbgFetchQsign: Bot(1145141919810) initialize complete 2024-02-24 11:54:38 I/Bot.1145141919810: Calculating type 2 PoW, it can take some time.... 2024-02-24 11:54:38 I/Bot.1145141919810: Got PoW result, cost: 279 ms 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] 需要滑动验证码, 请按照以下链接的步骤完成滑动验证码, 然后输入获取到的 ticket 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] Slider captcha required. Please solve the captcha with following link. Type ticket here after completion. 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] @see https://github.com/project-mirai/mirai-login-solver-selenium 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] @see https://docs.mirai.mamoe.net/mirai-login-solver-selenium/ 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] 或者输入 helper 来使用 TxCaptchaHelper 完成滑动验证码 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] Or type helper to resolve slider captcha with TxCaptchaHelper.apk 2024-02-24 11:54:38 W/Bot.1145141919810: [SliderCaptcha] TxCaptchaHelper 的在线服务疑似被屏蔽，可能无法使用。TxCaptchaHelper 现已无法满足登录QQ机器人，请在以下链接下载全新的验证器 2024-02-24 11:54:38 W/Bot.1145141919810: [SliderCaptcha] The service of TxCaptchaHelper might be blocked. We recommend you to download the new login solver plugin in below link. 2024-02-24 11:54:38 W/Bot.1145141919810: [SliderCaptcha] @see https://github.com/KasukuSakura/mirai-login-solver-sakura 2024-02-24 11:54:38 I/Bot.1145141919810: [SliderCaptcha] Captcha link: https://ssl.captcha.qq.com/template/wireless_mqq_captcha.html?style=simple&aid=16&uin=1145141919810&sid=5738257646978951294&cap_cd=Hnk3Vsl8PgRc8oK4lc6I14vygZrXmIjE_duptCzb1HrNS2mZOtDD5g**&clientype=1&apptype=2 LOGIN> > t03kVPX87KpIZs0WIMGYCrpwI1qheyN5V-qhkLmfdE7kymgRssrrex8C9LzdL-4Itwv4NZTHqukcIjvexgRLpdXa1eNOeYYbSfKbcmk3bFUldtfZSoPC6xWrDz1Emw5hgDii3GYevrBaYlFavU8FZbBPWo-ip6NYxfpBP57Vhp1uD5KSNBT49rG7mQ77AHV8hmmzRZ1uWrWS2s* 2024-02-24 11:54:54 I/Bot.1145141919810: [SliderCaptcha] 正在提交中... 2024-02-24 11:54:54 I/Bot.1145141919810: [SliderCaptcha] Submitting... 2024-02-24 11:54:55 I/UnidbgFetchQsign: Bot(1145141919810) destroy, Instance destroyed successfully. 2024-02-24 11:54:55 I/Bot.1145141919810: Bot cancelled: Bot closed Login failed: Consuming(value=null) 2024-02-24 11:54:55 E/console: net.mamoe.mirai.utils.channels.IllegalChannelStateException: Consuming(value=null) net.mamoe.mirai.utils.channels.IllegalChannelStateException: Consuming(value=null) at net.mamoe.mirai.utils.channels.CoroutineOnDemandReceiveChannel.expectMore(OnDemandChannelImpl.kt:211) at net.mamoe.mirai.internal.network.auth.AuthControl.actMethodFailed(AuthControl.kt:67) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:297) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$login$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) > login 1145141919810 woshiaikun ANDROID_PAD 2024-02-24 11:55:33 I/KFCFactory: create EncryptService(id=1145141919810), protocol=ANDROID_PAD(8.9.96) by fuqiuluo/unidbg-fetch-qsign from file:///ntfs/mirai/KFCFactory.json 2024-02-24 11:55:33 I/KFCFactory: unidbg-fetch-qsign by http://yuanshenqidong.mihoyo:11451 about { "code": 0, "msg": "IAA 云天明 章北海", "data": { "version": "1.1.9", "protocol": { "qua": "V1_AND_SQ_8.9.96_5048_HDBM_T", "version": "8.9.96", "code": "5048", "package_name": "com.tencent.mobileqq" } } } 2024-02-24 11:55:33 I/UnidbgFetchQsign: Bot(1145141919810) initialize by http://yuanshenqidong.mihoyo:11451 2024-02-24 11:55:39 I/UnidbgFetchQsign: Bot(1145141919810) register, Instance loaded successfully. 2024-02-24 11:55:39 I/UnidbgFetchQsign: Bot(1145141919810) initialize complete 2024-02-24 11:55:41 I/Bot.1145141919810: Calculating type 2 PoW, it can take some time.... 2024-02-24 11:55:41 I/Bot.1145141919810: Got PoW result, cost: 95 ms 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] 需要滑动验证码, 请按照以下链接的步骤完成滑动验证码, 然后输入获取到的 ticket 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] Slider captcha required. Please solve the captcha with following link. Type ticket here after completion. 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] @see https://github.com/project-mirai/mirai-login-solver-selenium 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] @see https://docs.mirai.mamoe.net/mirai-login-solver-selenium/ 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] 或者输入 helper 来使用 TxCaptchaHelper 完成滑动验证码 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] Or type helper to resolve slider captcha with TxCaptchaHelper.apk 2024-02-24 11:55:41 W/Bot.1145141919810: [SliderCaptcha] TxCaptchaHelper 的在线服务疑似被屏蔽，可能无法使用。TxCaptchaHelper 现已无法满足登录QQ机器人，请在以下链接下载全新的验证器 2024-02-24 11:55:41 W/Bot.1145141919810: [SliderCaptcha] The service of TxCaptchaHelper might be blocked. We recommend you to download the new login solver plugin in below link. 2024-02-24 11:55:41 W/Bot.1145141919810: [SliderCaptcha] @see https://github.com/KasukuSakura/mirai-login-solver-sakura 2024-02-24 11:55:41 I/Bot.1145141919810: [SliderCaptcha] Captcha link: https://ssl.captcha.qq.com/template/wireless_mqq_captcha.html?style=simple&aid=16&uin=1145141919810&sid=2386832556388083901&cap_cd=wmrdyg7OBjye7gM5N4u9wmuFTS12HL5Vz0sFGTINNjkmPuQjGHCOFQ**&clientype=1&apptype=2 LOGIN> > t030iUUDSI5Wqv1JO1kgk6VSRDPZ6k_K4j_w9p6besBQLjbTu_Q26ygiwHg2Zs6jE6IxDoZ3vz9rowGbY4w4pUS9Tbxgei_xiJx42mdP8lNcnlsibNiIwK5tTuUHf0ouIvKE_TXOESGw7XW7do7FYdtiYRI403lhpATTaI0gzMQbJEke_sCrv5jkm08B_PuVkgTYeoBCEpR-M8* 2024-02-24 11:56:06 I/Bot.1145141919810: [SliderCaptcha] 正在提交中... 2024-02-24 11:56:06 I/Bot.1145141919810: [SliderCaptcha] Submitting... 2024-02-24 11:56:07 I/UnidbgFetchQsign: Bot(1145141919810) destroy, Instance destroyed successfully. Login failed: Consuming(value=null) 2024-02-24 11:56:07 I/Bot.1145141919810: Bot cancelled: Bot closed 2024-02-24 11:56:07 E/console: net.mamoe.mirai.utils.channels.IllegalChannelStateException: Consuming(value=null) net.mamoe.mirai.utils.channels.IllegalChannelStateException: Consuming(value=null) at net.mamoe.mirai.utils.channels.CoroutineOnDemandReceiveChannel.expectMore(OnDemandChannelImpl.kt:211) at net.mamoe.mirai.internal.network.auth.AuthControl.actMethodFailed(AuthControl.kt:67) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:297) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$login$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) > login 1145141919810 jiniaimei ANDROID_PAD 2024-02-24 11:56:22 I/KFCFactory: create EncryptService(id=1145141919810), protocol=ANDROID_PAD(8.9.96) by fuqiuluo/unidbg-fetch-qsign from file:///ntfs/mirai/KFCFactory.json 2024-02-24 11:56:22 I/KFCFactory: unidbg-fetch-qsign by http://yuanshenqidong.mihoyo:11451 about { "code": 0, "msg": "IAA 云天明 章北海", "data": { "version": "1.1.9", "protocol": { "qua": "V1_AND_SQ_8.9.96_5048_HDBM_T", "version": "8.9.96", "code": "5048", "package_name": "com.tencent.mobileqq" } } } 2024-02-24 11:56:22 I/UnidbgFetchQsign: Bot(1145141919810) initialize by http://yuanshenqidong.mihoyo:11451 2024-02-24 11:56:27 I/UnidbgFetchQsign: Bot(1145141919810) register, Instance loaded successfully. 2024-02-24 11:56:27 I/UnidbgFetchQsign: Bot(1145141919810) initialize complete 2024-02-24 11:56:29 I/Bot.1145141919810: Calculating type 2 PoW, it can take some time.... 2024-02-24 11:56:29 I/Bot.1145141919810: Got PoW result, cost: 173 ms 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] 需要滑动验证码, 请按照以下链接的步骤完成滑动验证码, 然后输入获取到的 ticket 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] Slider captcha required. Please solve the captcha with following link. Type ticket here after completion. 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] @see https://github.com/project-mirai/mirai-login-solver-selenium 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] @see https://docs.mirai.mamoe.net/mirai-login-solver-selenium/ 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] 或者输入 helper 来使用 TxCaptchaHelper 完成滑动验证码 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] Or type helper to resolve slider captcha with TxCaptchaHelper.apk 2024-02-24 11:56:29 W/Bot.1145141919810: [SliderCaptcha] TxCaptchaHelper 的在线服务疑似被屏蔽，可能无法使用。TxCaptchaHelper 现已无法满足登录QQ机器人，请在以下链接下载全新的验证器 2024-02-24 11:56:29 W/Bot.1145141919810: [SliderCaptcha] The service of TxCaptchaHelper might be blocked. We recommend you to download the new login solver plugin in below link. 2024-02-24 11:56:29 W/Bot.1145141919810: [SliderCaptcha] @see https://github.com/KasukuSakura/mirai-login-solver-sakura 2024-02-24 11:56:29 I/Bot.1145141919810: [SliderCaptcha] Captcha link: https://ssl.captcha.qq.com/template/wireless_mqq_captcha.html?style=simple&aid=16&uin=1145141919810&sid=4402868051689171180&cap_cd=2g7FMjs_f5SNKIihhRGIG3kDy7GJnjWDZlWq_ue-omhbnhRD_CL8PQ**&clientype=1&apptype=2 LOGIN> > t031N0r8Vr5JFhRKSxKwoDctIx_Y39agDicaL8HtTbhSCl9hMP8nYMIl6jbZMtZ8f-WAWPna16R2x6RKHJtdYht87HVM9SHNkifM2Mx7NflZCsoY57WjzptD4TizmUi807Upv8HKuB9M2S2WVT_5rryZEpaKdTGiL-THn_e7famlB3CO0dXXALpeH4XfGnU42QmSEhtQGthzu8* 2024-02-24 11:56:47 I/Bot.1145141919810: [SliderCaptcha] 正在提交中... 2024-02-24 11:56:47 I/Bot.1145141919810: [SliderCaptcha] Submitting... 2024-02-24 11:56:48 I/UnidbgFetchQsign: Bot(1145141919810) destroy, Instance destroyed successfully. 2024-02-24 11:56:48 I/Bot.1145141919810: Bot cancelled: Bot closed Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. 2024-02-24 11:56:48 E/console: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(1145141919810), code=1, title=登录失败, message=账号或密码错误，请重新输入。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(1145141919810), code=1, title=登录失败, message=账号或密码错误，请重新输入。, errorInfo=)] Mirai console 2.15.0 ANDROID_PHONE 8.9.96.13525 2023-11-28T17:40:03+08:00 ANDROID_PAD 8.9.96.13525 2023-11-28T17:40:03+08:00