寄了，不能用了。请移步用Pandora继续白嫖chatGPT

前段时间看到了ading2210发布的poe-api,可以从poe.com白嫖到gpt3.5和claude，这种白嫖的好事怎么能少得了我😋。

下载

项目地址
配置教程

注意

需要使用代理和mirai-api-http，详见文档

使用

考试周了，做的很急，poe-api的文档还没来得及看个遍，让我本来就依托答辩的代码水平雪上加霜😭。
QQ图片20230619100955.jpg

我目前在用MCL，想要用签名服务来正常登录。目前的理解是，MCL需要装sakura插件进行扫码登录，需要装fix-protocol-version插件来与签名服务器对接。其中支持的签名服务器有两个，一个是unidbg-fetch-qsign，一个是magic-signer-guide，二者任选一个就可以了。
我尝试配置qsign的时候出现了问题：
1.我（似乎）正常配置了config和device等信息
2.我可以打开go-cqhttp.bat，并且正常登录，显示好友发送的消息
3.打开mcl的时候，似乎可以正常连接qsign的服务器：

2023-10-03 10:16:20 I/fix-protocol-version: 当前签名服务配置信息: v8.9.58 by fuqiuluo/unidbg-fetch-qsign from http://127.0.0.1:13579

4.在mcl中login，然后使用sakura扫码登录，报错：

2023-10-03 10:16:47 I/Bot.xxxxxxxxxx: Bot cancelled: Bot closed Login failed: unidbg-fetch-qsign 服务异常, 请检查其日志, 'running' 2023-10-03 10:16:47 E/console: xyz.cssxsh.mirai.tool.KFCStateException: unidbg-fetch-qsign 服务异常, 请检查其日志, 'running' xyz.cssxsh.mirai.tool.KFCStateException: unidbg-fetch-qsign 服务异常, 请检查其日志, 'running' at fix-protocol-version-1.12.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.check(UnidbgFetchQsign.kt:109) at fix-protocol-version-1.12.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.customEnergy(UnidbgFetchQsign.kt:137) at fix-protocol-version-1.12.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.encryptTlv(UnidbgFetchQsign.kt:125) at net.mamoe.mirai.internal.network.protocol.packet.TlvKt.t544ForVerify(Tlv.kt:1013) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1$1$1$1.invoke(WtLogin2.kt:35) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1$1$1$1.invoke(WtLogin2.kt:28) at net.mamoe.mirai.utils.TlvMapKt._writeTlvMap(TlvMap.kt:130) at net.mamoe.mirai.utils.TlvMapKt._writeTlvMap$default(TlvMap.kt:123) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1$1$1.invoke(WtLogin2.kt:28) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1$1$1.invoke(WtLogin2.kt:25) at net.mamoe.mirai.internal.network.protocol.packet.EncryptMethodEcdh.makeBody(EncryptMethod.kt:121) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeOicqRequestPacket(OutgoingPacket.kt:455) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeOicqRequestPacket$default(OutgoingPacket.kt:448) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1$1.invoke(WtLogin2.kt:25) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1$1.invoke(WtLogin2.kt:24) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeSsoPacket(OutgoingPacket.kt:985) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeSsoPacket$default(OutgoingPacket.kt:352) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1.invoke(WtLogin2.kt:24) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2$SubmitSliderCaptcha$1.invoke(WtLogin2.kt:23) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.buildLoginOutgoingPacket(OutgoingPacket.kt:310) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.buildLoginOutgoingPacket$default(OutgoingPacket.kt:278) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin2.SubmitSliderCaptcha(WtLogin2.kt:23) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:472) 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.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) 2023-10-03 10:18:47 W/io.netty.channel.DefaultChannelPipeline: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. io.netty.handler.timeout.ReadTimeoutException

请问我应该如何解决呢？
顺便想问，官方可以出一个稍微易懂的教程吗，或者有没有人做一个...感觉我肯定是哪里配置有问题...

mirai版本：2.15.0
登录协议：ANDROID_PAD

2023-07-16 07:21:03 W/EncryptService.alert: Encrypt service was loaded: KFCFactory(config=file:///D:/Dice/Mirai%20Dice%20Windows/KFCFactory.json) 2023-07-16 07:21:03 W/EncryptService.alert: All outgoing message may be leaked by this service. 2023-07-16 07:21:03 W/EncryptService.alert: Use this service if and only if you trusted this service and the service provider. 2023-07-16 07:21:03 W/EncryptService.alert: Service details: 2023-07-16 07:21:03 W/EncryptService.alert: `- Jvm Class: class xyz.cssxsh.mirai.tool.KFCFactory 2023-07-16 07:21:03 W/EncryptService.alert: `- ClassLoader: JvmPluginClassLoader{fix-protocol-version-1.9.5.mirai2.jar} 2023-07-16 07:21:03 W/EncryptService.alert: `- Source: file:/D:/Dice/Mirai%20Dice%20Windows/plugins/fix-protocol-version-1.9.5.mirai2.jar 2023-07-16 07:21:03 W/EncryptService.alert: `- Protected Domain: ProtectionDomain (file:/D:/Dice/Mirai%20Dice%20Windows/plugins/fix-protocol-version-1.9.5.mirai2.jar <no signer certificates>) JvmPluginClassLoader{fix-protocol-version-1.9.5.mirai2.jar} <no principals> java.security.Permissions@122604e ( ("java.io.FilePermission" "D:\Dice\Mirai Dice Windows\plugins\fix-protocol-version-1.9.5.mirai2.jar" "read") ) 2023-07-16 07:21:03 E/main: java.lang.RuntimeException: 请检查 magic-signer-guide by http://127.0.0.1:8888 的可用性 java.lang.RuntimeException: 请检查 magic-signer-guide by http://127.0.0.1:8888 的可用性 at fix-protocol-version-1.9.5.mirai2.jar//xyz.cssxsh.mirai.tool.KFCFactory.createForBot(KFCFactory.kt:97) at net.mamoe.mirai.internal.network.components.EncryptServiceHolderImpl.<init>(EncryptServiceHolder.kt:49) at net.mamoe.mirai.internal.QQAndroidBot.createBotLevelComponents(QQAndroidBot.kt:288) at net.mamoe.mirai.internal.QQAndroidBot$defaultBotLevelComponents$2.invoke(QQAndroidBot.kt:192) at net.mamoe.mirai.internal.QQAndroidBot$defaultBotLevelComponents$2.invoke(QQAndroidBot.kt:191) at net.mamoe.mirai.utils.LateinitMutableProperty.getValue(LateinitMutableProperty.kt:47) at net.mamoe.mirai.internal.QQAndroidBot.getDefaultBotLevelComponents(QQAndroidBot.kt:191) at net.mamoe.mirai.internal.QQAndroidBot.createNetworkLevelComponents(QQAndroidBot.kt:300) at net.mamoe.mirai.internal.QQAndroidBot$createNetworkHandler$1.invoke(QQAndroidBot.kt:312) at net.mamoe.mirai.internal.QQAndroidBot$createNetworkHandler$1.invoke(QQAndroidBot.kt:305) at net.mamoe.mirai.internal.network.handler.selector.AbstractKeepAliveNetworkHandlerSelectorKt$KeepAliveNetworkHandlerSelector$1.createInstance(AbstractKeepAliveNetworkHandlerSelector.kt:277) at net.mamoe.mirai.internal.network.handler.selector.AbstractKeepAliveNetworkHandlerSelector.refreshInstance(AbstractKeepAliveNetworkHandlerSelector.kt:249) at net.mamoe.mirai.internal.network.handler.selector.AbstractKeepAliveNetworkHandlerSelector.getCurrentInstanceOrCreate(AbstractKeepAliveNetworkHandlerSelector.kt:57) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.getContext(SelectorNetworkHandler.kt:51) at net.mamoe.mirai.internal.QQAndroidBot.getComponents(QQAndroidBot.kt:189) at net.mamoe.mirai.internal.AbstractBot.login(AbstractBot.kt:154) at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge$doStart$11$1.invokeSuspend(MiraiConsoleImplementationBridge.kt:426) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:284) at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.kt:369) at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:512) at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:182) at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:181) at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:59) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.itxtech.mcl.Utility.bootJars(Utility.java:86) at org.itxtech.mcl.Utility.bootJars(Utility.java:76) at org.itxtech.mcl.Utility.bootMirai(Utility.java:98) at org.itxtech.mcl.module.builtin.Boot.boot(Boot.java:113) at org.itxtech.mcl.module.ModuleManager.phaseBoot(ModuleManager.java:123) at org.itxtech.mcl.Loader.lambda$start$4(Loader.java:196) at org.itxtech.mcl.Loader.tryCatching(Loader.java:151) at org.itxtech.mcl.Loader.start(Loader.java:196) at org.itxtech.mcl.Loader.main(Loader.java:84) Suppressed: java.lang.RuntimeException: 请检查 magic-signer-guide by http://127.0.0.1:8888 的可用性 at fix-protocol-version-1.9.5.mirai2.jar//xyz.cssxsh.mirai.tool.KFCFactory.createForBot(KFCFactory.kt:97) at net.mamoe.mirai.internal.network.components.EncryptServiceHolderImpl.<init>(EncryptServiceHolder.kt:49) at net.mamoe.mirai.internal.QQAndroidBot.createBotLevelComponents(QQAndroidBot.kt:288) at net.mamoe.mirai.internal.QQAndroidBot$defaultBotLevelComponents$2.invoke(QQAndroidBot.kt:192) at net.mamoe.mirai.internal.QQAndroidBot$defaultBotLevelComponents$2.invoke(QQAndroidBot.kt:191) at net.mamoe.mirai.utils.LateinitMutableProperty.getValue(LateinitMutableProperty.kt:47) at net.mamoe.mirai.internal.QQAndroidBot.getDefaultBotLevelComponents(QQAndroidBot.kt:191) at net.mamoe.mirai.internal.QQAndroidBot.createNetworkLevelComponents(QQAndroidBot.kt:300) at net.mamoe.mirai.internal.QQAndroidBot$createNetworkHandler$1.invoke(QQAndroidBot.kt:312) at net.mamoe.mirai.internal.QQAndroidBot$createNetworkHandler$1.invoke(QQAndroidBot.kt:305) at net.mamoe.mirai.internal.network.handler.selector.AbstractKeepAliveNetworkHandlerSelectorKt$KeepAliveNetworkHandlerSelector$1.createInstance(AbstractKeepAliveNetworkHandlerSelector.kt:277) at net.mamoe.mirai.internal.network.handler.selector.AbstractKeepAliveNetworkHandlerSelector.refreshInstance(AbstractKeepAliveNetworkHandlerSelector.kt:249) at net.mamoe.mirai.internal.network.handler.selector.AbstractKeepAliveNetworkHandlerSelector.getCurrentInstanceOrCreate(AbstractKeepAliveNetworkHandlerSelector.kt:57) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.getContext(SelectorNetworkHandler.kt:51) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler$scope$2.invoke(SelectorNetworkHandler.kt:54) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler$scope$2.invoke(SelectorNetworkHandler.kt:53) at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.getScope(SelectorNetworkHandler.kt:53) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.access$getScope(SelectorNetworkHandler.kt:45) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.resumeConnection$suspendImpl(SelectorNetworkHandler.kt:130) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.resumeConnection(SelectorNetworkHandler.kt) at net.mamoe.mirai.internal.AbstractBot.login(AbstractBot.kt:145) ... 27 more Caused by: java.net.ConnectException: Connection refused: connect at java.base/java.net.PlainSocketImpl.connect0(Native Method) at java.base/java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:101) at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255) at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237) at java.base/java.net.Socket.connect(Socket.java:609) at java.base/java.net.Socket.connect(Socket.java:558) at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:182) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:507) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:602) at java.base/sun.net.www.http.HttpClient.<init>(HttpClient.java:275) at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:374) at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:395) at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1253) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1187) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1081) at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:1015) at fix-protocol-version-1.9.5.mirai2.jar//xyz.cssxsh.mirai.tool.KFCFactory.createForBot(KFCFactory.kt:95) ... 48 more Caused by: java.net.ConnectException: Connection refused: connect at java.base/java.net.PlainSocketImpl.connect0(Native Method) at java.base/java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:101) at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255) at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237) at java.base/java.net.Socket.connect(Socket.java:609) at java.base/java.net.Socket.connect(Socket.java:558) at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:182) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:507) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:602) at java.base/sun.net.www.http.HttpClient.<init>(HttpClient.java:275) at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:374) at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:395) at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1253) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1187) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1081) at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:1015) at fix-protocol-version-1.9.5.mirai2.jar//xyz.cssxsh.mirai.tool.KFCFactory.createForBot(KFCFactory.kt:95) ... 42 more

是fix-protocol-version我没装对嘛？版本是1.9.5
谢谢大佬们指点

Mirai机器人插件 mirai-plugin-midjourney

Github项目指路

Mirai机器人插件 mirai-plugin-midjourney 介绍 免责声明 使用方法 1 添加插件 2 编辑配置文件 config.yml(必须配置) help_config.yml (选择配置) 3 开始使用 功能 四宫格图像 单图像 指令 出现问题 开源协议 介绍

本项目为 Mirai 的机器人插件，对接 Midjourney API，实现 QQ 机器人的AI绘画功能，当前版本 v0.1.0。

本插件基于 Mirai 2.15 版本开发，支持 2.14 版本，暂未测试其他 Mirai 版本，如有其他版本请自行测试。

本插件使用的 Midjourney API 兼容:

Calcium-Ion/one-api novicezk/midjourney-proxy 免责声明

注意，本项目仅限于学术研究，请勿用于非法用途。不建议向公众提供服务，当然也不鼓励，不支持一切商业使用。生成的图像属于 Midjourney ，任何由于此项目导致的法律问题本人概不负责。

使用方法 1 添加插件

如果你要添加该插件，请将该插件放在 MCL 根目录下的 /plugins 文件夹中,并运行一次 MCL，生成插件的 Config 文件。

2 编辑配置文件

目前版本暂不支持在线更新Config。在 MCL 成功运行后，请关闭 MCL 主程序。

在 Mirai 的根目录下找到 /config/top.joyer.mirai-plugin-midjourney 文件夹，在该文件夹下为本插件的配置文件。

config.yml help_config and More... 插件主要配置文件 插件自带Help指令配置文件 and More... config.yml(必须配置) 配置项 类型 描述 bot_qq long 被允许运行此插件的机器人企鹅号（必须是数字企鹅号），必须配置 api_url String 通过兼容的API平台获取的API地址，必须配置 api_key String 通过兼容的API平台获取的密钥，必须配置 command_help bool 插件自带Help指令的开关,默认打开 bot_qq: 123456 api_key: 'sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' command_help: true help_config.yml (选择配置) 配置项 类型 描述 help_text String 用户执行/?显示的文本

后期会改善在配置文件中配置的便利性

help_text: "Bot指令列表：\n\nAI绘画：\n◆ /image <关键词> # 新的AI绘图\n◆ /change v <数字1-4> <可选：绘图ID> # 从四宫格绘图中的第{数字}幅图为底生成新的绘图\n◆ /change u <数字1-4> <可选：绘图ID> # 放大四宫格绘图中的第{数字}幅图\n◆ /change r <可选：任务ID> # 重新绘制四宫格绘图\n\n在 image 指令中添加 --niji <数字1-5> 参数，数字越大二次元浓度越高\n在 change 指令中如果不填写绘图 ID ，默认为该用户上一次生成的四宫格绘图" 3 开始使用

重新运行 MCL 主程序，现在可以开始使用了。

功能 由用户唤起的绘图请求，并在绘图结束后获得四宫格的图像 由用户唤起的绘图修改请求，并在绘图结束后获得四宫格的图像或单图像

⚠ 绘图指令受到 PG-13 分级的限制，如果关键词超出这个限制将不会生成图像，并弹出警告。 （某些瑟瑟的人呐，小心机器人封号）

四宫格图像

1695580369782414.jpg

上图可见为四宫格图像，从左到右从上到下被定义为图1、2、3、4。

单图像

1695584776767642.jpg

上图为单图像，经过放大四宫格图像操作得到（例如上图是/change u 1）。

指令 指令用法 描述 /image <关键词> 新的AI绘图 /change v <数字1-4> <可选：绘图ID> 从四宫格绘图中的第{数字}幅图为底生成新的绘图 /change u <数字1-4> <可选：绘图ID> 放大四宫格绘图中的第{数字}幅图 /change r <可选：任务ID> 重新绘制四宫格绘图

在上述指令中有一个可选参数绘图ID，绘图ID在每次绘图生成时被附带生成。如果在输入指令时未输入该ID，插件会尝试使用上一次用户生成的绘图的ID，未找到时将不会执行请求。

出现问题

如果有任何问题、建议、Bug提交，请在 Issues 中提出。

开源协议

本项目基于 AGPLv3 协议 开源。

八天后，十月六号，你肯定会感慨，为什么放假的时间过得这么快，一转眼第二天又要上班了，要是能回到放长假前的那个下午就好了。

那么现在，恭喜你回到了放假前的那个下午，请再一次开始享受你的假期吧！

050706a1-41ad-4204-b1ad-3094d4924b9b-546b103a179284e4d932a446e0c9381.png

（ 转发自 心惊报 并使用了 fixedjpstick 贴纸包 >_< ）

mirai插件的部分功能需要挂梯子
使用几分钟后账号消息会被风控
有无好的解决办法

win10电脑端部署mirai
clash for windows 翻墙

E/console:io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.163.51:8080

大家都是code之类的，我直接连不上了是网络的问题吗

前段时间好好的

使用qsign部署了8.9.73版本的服务，但fix-protocol-version无法下载8.9.73的协议

2023-09-30 19:41:20 W/fix-protocol-version: java.lang.IllegalStateException: 从 https://raw.githubusercontent.com/RomiChan/protocol-versions/master/android_pad/8.9.73.json 下载协议失败 java.lang.IllegalStateException: 从 https://raw.githubusercontent.com/RomiChan/protocol-versions/master/android_pad/8.9.73.json 下载协议失败 at fix-protocol-version-1.9.9.mirai2.jar//xyz.cssxsh.mirai.tool.FixProtocolVersion.fetch(FixProtocolVersion.kt:319) at fix-protocol-version-1.9.9.mirai2.jar//xyz.cssxsh.mirai.tool.FixProtocolVersionCommand.fetch(FixProtocolVersionCommand.kt:15) at jdk.internal.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at kotlin.reflect.jvm.internal.calls.CallerImpl$Method.callMethod(CallerImpl.kt:97) at kotlin.reflect.jvm.internal.calls.CallerImpl$Method$Instance.call(CallerImpl.kt:113) at kotlin.reflect.jvm.internal.KCallableImpl.call(KCallableImpl.kt:108) at kotlin.reflect.jvm.internal.KCallableImpl.callDefaultMethod$kotlin_reflection(KCallableImpl.kt:159) at kotlin.reflect.full.KCallables.callSuspendBy(KCallables.kt:74) at net.mamoe.mirai.console.internal.command.CommandReflector$findSubCommands$6$1.invokeSuspend(CommandReflector.kt:339) at net.mamoe.mirai.console.internal.command.CommandReflector$findSubCommands$6$1.invoke(CommandReflector.kt) at net.mamoe.mirai.console.internal.command.CommandReflector$findSubCommands$6$1.invoke(CommandReflector.kt) at net.mamoe.mirai.console.command.descriptor.CommandSignatureFromKFunctionImpl.call$suspendImpl(CommandSignature.kt:84) at net.mamoe.mirai.console.command.descriptor.CommandSignatureFromKFunctionImpl.call(CommandSignature.kt) at net.mamoe.mirai.console.internal.command.CommandManagerImplKt.executeCommandImpl(CommandManagerImpl.kt:168) at net.mamoe.mirai.console.command.CommandManager.executeCommand$suspendImpl(CommandManager.kt:131) at net.mamoe.mirai.console.command.CommandManager.executeCommand(CommandManager.kt) at net.mamoe.mirai.console.command.CommandManager$INSTANCE.executeCommand(CommandManager.kt) at net.mamoe.mirai.console.terminal.ConsoleThreadKt$startupConsoleThread$3.invokeSuspend(ConsoleThread.kt:187) 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.net.UnknownHostException: raw.githubusercontent.com at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:567) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) at java.base/java.net.Socket.connect(Socket.java:633) at java.base/sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:304) at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:178) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:532) at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:637) at java.base/sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:266) at java.base/sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:380) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:193) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1242) at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1128) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:179) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1665) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) at fix-protocol-version-1.9.9.mirai2.jar//xyz.cssxsh.mirai.tool.FixProtocolVersion.fetch(FixProtocolVersion.kt:294) ... 25 more Suppressed: java.io.FileNotFoundException: https://ghproxy.com/https://raw.githubusercontent.com/RomiChan/protocol-versions/master/android_pad/8.9.73.json at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1993) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) at fix-protocol-version-1.9.9.mirai2.jar//xyz.cssxsh.mirai.tool.FixProtocolVersion.fetch(FixProtocolVersion.kt:303) ... 25 more

qsign服务部署是没问题的

项目地址:ChatLearning
下载地址:ChatLearningReleases
官方网站:官网
交流QQ群：734450830 可在群内提出遇到的问题，bug和改进建议

使用ChatLearning前请先安装并配置好mirai-api-http插件，为避免出错，mirai-api-http插件请尽量使用2.3.3版本

完成配置后打开ChatLearning目录下的data.json文件填入配置信息：

{ "Key": "xxxxx", //在mirai-api-http中设置的密钥 "host": "127.0.0.1:8080", //mirai-api-http中设置的地址（若设置成0.0.0.0，请填写127.0.0.1） "port": "8080", //mirai-api-httpmirai-api-http中设置的端口 "qq": "xxx", //所登录mirai的QQ号 "session": "xxx" //任意，由程序自动获取 }

以上步骤完成后，Windows用户点击Chatmain.exe运行

Linux用户则使用python运行Chatmain.py脚本 （python版本需为3.5以上）

输入help来查看命令列表

详细说明请见README

来自@daisy524 提供的创意点子
感谢@FuYon 制作的网站

以下是ChatLearning的效果图（收集了大约一天的词库，图中绿牌是bot，甚至还能斗图）
73126921-7ddf-4140-8b78-5c0d3e69242c-IMG_20220223_021125.png
905df16e-90ae-4b80-ae81-7b97b3d7eb0c-IMG_20220223_021144.png 8ede119a-7ba5-4d0b-bbb9-26a33c26a65a-IMG_20220223_021230.png 048d36f2-2c25-4a4e-8624-e91564f0c59f-IMG_20220223_021250.png

欢迎提出bug和提供后续更新意见！

我使用的mirai版本是：2.16.0-RC
用的是ANDROID_PAD协议，版本是8.9.63
然后用的服务是unidbg-fetch-qsign
使用签名服务前两天能够正常自动登陆，第三天自动和手动登陆都报CODE=45
Mirai日志：

...

Mirai日志：
/login 账号 密码 ANDROID_PAD

2023-09-28 22:19:02 I/KFCFactory: create EncryptService(id=2750556895), protocol=ANDROID_PAD(8.9.63) by fuqiuluo/unidbg-fetch-qsign from file:///D:/mirai-dice-classic/KFCFactory.json

2023-09-28 22:19:02 I/KFCFactory: unidbg-fetch-qsign by http://127.0.0.1:8080 about

{

"code": 0, "msg": "IAA 云天明 章北海", "data": { "version": "1.1.9", "protocol": { "qua": "V1_AND_SQ_8.9.63_4194_YYB_D", "version": "8.9.63", "code": "4194", "package_name": "com.tencent.mobileqq" } }

}

2023-09-28 22:19:02 I/Bot.2750556895: Loaded account secrets from local cache.

2023-09-28 22:19:03 I/UnidbgFetchQsign: Bot(2750556895) initialize by http://127.0.0.1:8080

2023-09-28 22:19:05 I/UnidbgFetchQsign: Bot(2750556895) register, Instance loaded successfully.

2023-09-28 22:19:05 I/UnidbgFetchQsign: Bot(2750556895) initialize complete

2023-09-28 22:19:06 I/Bot.2750556895: Loaded account secrets from local cache.

2023-09-28 22:19:07 I/Bot.2750556895: Loaded account secrets from local cache.

2023-09-28 22:19:07 W/UnidbgFetchQsign: with CoroutineName(SendMessage)

java.lang.RuntimeException: Bot(2750556895) callback trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

at fix-protocol-version-1.12.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:104) 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: 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) 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) ... 4 more

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.components.SsoProcessorImpl$login$1.invokeSuspend(SsoProcessor.kt) ... 9 more Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2750556895), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, 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) ... 9 more Suppressed: java.lang.IllegalStateException: Fast login failed: Error(bot=Bot(2750556895), code=16, title=登录失败, message=你的用户身份已失效，为保证账号安全，请你重新 登录。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl.doLogin(SsoProcessor.kt:528) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ... 9 more [CIRCULAR REFERENCE:net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2750556895), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=)]

2023-09-28 22:19:07 I/UnidbgFetchQsign: Bot(2750556895) destroy, Instance destroyed successfully.

2023-09-28 22:19:07 I/Bot.2750556895: Bot cancelled: Bot closed

Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.

2023-09-28 22:19:10 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.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) Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2750556895), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, 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) ... 9 more Suppressed: java.lang.IllegalStateException: Fast login failed: Error(bot=Bot(2750556895), code=16, title=登录失败, message=你的用户身份已失效，为保证账号安全，请你重新 登录。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl.doLogin(SsoProcessor.kt:528) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ... 9 more [CIRCULAR REFERENCE:net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2750556895), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=)]

签名服务日志

...

Microsoft Windows [版本 10.0.19045.3448]

(c) Microsoft Corporation。保留所有权利。

D:\unidbg-fetch-qsign.3\unidbg-fetch-qsign-1.1.9>bin\unidbg-fetch-qsign.bat --basePath=txlib\8.9.63

FEBond sum = 7680

Load Package = Protocol(qua=V1_AND_SQ_8.9.63_4194_YYB_D, version=8.9.63, code=4194, packageName=com.tencent.mobileqq)

22:03:37.922 [main] INFO ktor.application - Autoreload is disabled because the development mode is off.

22:03:38.271 [main] INFO ktor.application - Application started in 0.38 seconds.

22:03:38.277 [main] DEBUG io.netty.util.internal.logging.InternalLoggerFactory - Using SLF4J as the default logging framework

22:03:38.296 [main] DEBUG io.netty.util.internal.PlatformDependent0 - -Dio.netty.noUnsafe: false

22:03:38.297 [main] DEBUG io.netty.util.internal.PlatformDependent0 - Java version: 11

22:03:38.298 [main] DEBUG io.netty.util.internal.PlatformDependent0 - sun.misc.Unsafe.theUnsafe: available

22:03:38.298 [main] DEBUG io.netty.util.internal.PlatformDependent0 - sun.misc.Unsafe.copyMemory: available

22:03:38.299 [main] DEBUG io.netty.util.internal.PlatformDependent0 - sun.misc.Unsafe.storeFence: available

22:03:38.299 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.Buffer.address: available

22:03:38.300 [main] DEBUG io.netty.util.internal.PlatformDependent0 - direct buffer constructor: unavailable: Reflective setAccessible(true) disabled

22:03:38.300 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.Bits.unaligned: available, true

22:03:38.301 [main] DEBUG io.netty.util.internal.PlatformDependent0 - jdk.internal.misc.Unsafe.allocateUninitializedArray(int): unavailable: class io.netty.util.internal.PlatformDependent0$7 cannot access class jdk.internal.misc.Unsafe (in module java.base) because module java.base does not export jdk.internal.misc to unnamed module @7af707e0

22:03:38.302 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.DirectByteBuffer.<init>(long, int): unavailable

22:03:38.302 [main] DEBUG io.netty.util.internal.PlatformDependent - sun.misc.Unsafe: available

22:03:38.329 [main] DEBUG io.netty.util.internal.PlatformDependent - maxDirectMemory: 2107637760 bytes (maybe)

22:03:38.330 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty.tmpdir: C:\Users\A\AppData\Local\Temp (java.io.tmpdir)

22:03:38.330 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty.bitMode: 64 (sun.arch.data.model)

22:03:38.331 [main] DEBUG io.netty.util.internal.PlatformDependent - Platform: Windows

22:03:38.332 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty.maxDirectMemory: -1 bytes

22:03:38.332 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty.uninitializedArrayAllocationThreshold: -1

22:03:38.333 [main] DEBUG io.netty.util.internal.CleanerJava9 - java.nio.ByteBuffer.cleaner(): available

22:03:38.333 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty.noPreferDirect: false

22:03:38.463 [main] DEBUG io.netty.channel.MultithreadEventLoopGroup - -Dio.netty.eventLoopThreads: 16

22:03:38.469 [main] DEBUG io.netty.util.concurrent.GlobalEventExecutor - -Dio.netty.globalEventExecutor.quietPeriodSeconds: 1

22:03:38.472 [main] DEBUG io.netty.util.internal.InternalThreadLocalMap - -Dio.netty.threadLocalMap.stringBuilder.initialSize: 1024

22:03:38.472 [main] DEBUG io.netty.util.internal.InternalThreadLocalMap - -Dio.netty.threadLocalMap.stringBuilder.maxSize: 4096

22:03:38.476 [main] DEBUG io.netty.channel.nio.NioEventLoop - -Dio.netty.noKeySetOptimization: false

22:03:38.477 [main] DEBUG io.netty.channel.nio.NioEventLoop - -Dio.netty.selectorAutoRebuildThreshold: 512

22:03:38.482 [main] DEBUG io.netty.util.internal.PlatformDependent - org.jctools-core.MpscChunkedArrayQueue: available

22:03:38.510 [main] DEBUG io.netty.channel.DefaultChannelId - -Dio.netty.processId: 19036 (auto-detected)

22:03:38.513 [main] DEBUG io.netty.util.NetUtil - -Djava.net.preferIPv4Stack: false

22:03:38.513 [main] DEBUG io.netty.util.NetUtil - -Djava.net.preferIPv6Addresses: false

22:03:38.602 [main] DEBUG io.netty.util.NetUtilInitializations - Loopback interface: lo (Software Loopback Interface 1, 127.0.0.1)

22:03:38.602 [main] DEBUG io.netty.util.NetUtil - Failed to get SOMAXCONN from sysctl and file \proc\sys\net\core\somaxconn. Default: 200

22:03:38.608 [main] DEBUG io.netty.channel.DefaultChannelId - -Dio.netty.machineId: d4:3b:04:ff:fe:58:aa:ca (auto-detected)

22:03:38.616 [main] DEBUG io.netty.util.ResourceLeakDetector - -Dio.netty.leakDetection.level: simple

22:03:38.616 [main] DEBUG io.netty.util.ResourceLeakDetector - -Dio.netty.leakDetection.targetRecords: 4

22:03:38.634 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.numHeapArenas: 16

22:03:38.634 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.numDirectArenas: 16

22:03:38.634 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.pageSize: 8192

22:03:38.634 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.maxOrder: 9

22:03:38.634 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.chunkSize: 4194304

22:03:38.634 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.smallCacheSize: 256

22:03:38.635 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.normalCacheSize: 64

22:03:38.635 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.maxCachedBufferCapacity: 32768

22:03:38.635 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.cacheTrimInterval: 8192

22:03:38.635 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.cacheTrimIntervalMillis: 0

22:03:38.635 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.useCacheForAllThreads: false

22:03:38.635 [main] DEBUG io.netty.buffer.PooledByteBufAllocator - -Dio.netty.allocator.maxCachedByteBuffersPerChunk: 1023

22:03:38.646 [main] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.allocator.type: pooled

22:03:38.647 [main] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.threadLocalDirectBufferSize: 0

22:03:38.648 [main] DEBUG io.netty.buffer.ByteBufUtil - -Dio.netty.maxThreadLocalCharBufferSize: 16384

22:03:38.666 [DefaultDispatcher-worker-1] INFO ktor.application - Responding at http://127.0.0.1:8080

22:05:04.725 [eventLoopGroupProxy-3-1] DEBUG io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkAccessible: true

22:05:04.725 [eventLoopGroupProxy-3-1] DEBUG io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkBounds: true

22:05:04.730 [eventLoopGroupProxy-3-1] DEBUG io.netty.util.ResourceLeakDetectorFactory - Loaded default ResourceLeakDetector: io.netty.util.ResourceLeakDetector@5ce883a9

22:05:04.796 [eventLoopGroupProxy-3-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.maxCapacityPerThread: 4096

22:05:04.796 [eventLoopGroupProxy-3-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.ratio: 8

22:05:04.799 [eventLoopGroupProxy-3-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.chunkSize: 32

22:05:04.804 [eventLoopGroupProxy-3-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.blocking: false

22:05:04.805 [eventLoopGroupProxy-3-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.batchFastThreadLocalOnly: true

22:05:06.141 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.BaseJniExtractor - Deleting leftover folder: C:\Users\A\AppData\Local\Temp\nativelib-loader_4069085358442131152

22:05:06.150 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.NativeLibraryUtil - processor is INTEL_64 os.arch is amd64

22:05:06.151 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.NativeLibraryUtil - architecture is WINDOWS_64 os.name is windows 10

22:05:06.151 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.NativeLibraryUtil - architecture is WINDOWS_64 os.name is windows 10

22:05:06.152 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.NativeLibraryUtil - platform specific path is natives/windows_64/

22:05:06.152 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.BaseJniExtractor - mappedLib is unicorn.dll

22:05:06.154 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.BaseJniExtractor - URL is jar:file:/D:/unidbg-fetch-qsign.3/unidbg-fetch-qsign-1.1.9/lib/unidbg-android-105.jar!/natives/windows_64/unicorn.dll

22:05:06.154 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.BaseJniExtractor - URL path is file:/D:/unidbg-fetch-qsign.3/unidbg-fetch-qsign-1.1.9/lib/unidbg-android-105.jar!/natives/windows_64/unicorn.dll

22:05:06.155 [eventLoopGroupProxy-4-2] DEBUG org.scijava.nativelib.BaseJniExtractor - Extracting 'jar:file:/D:/unidbg-fetch-qsign.3/unidbg-fetch-qsign-1.1.9/lib/unidbg-android-105.jar!/natives/windows_64/unicorn.dll' to 'C:\Users\A\AppData\Local\Temp\nativelib-loader_17248491636897764305\unicorn.dll'

QSign-Unidbg 白名单模式

[FEKit_]info: device_token_entry.h:87 initUin 2750556895

[FEKit_]info: device_info.h:583 start create xwid

[FEKit_]info: device_info.h:610 create xwid complete

[FEKit_]info: device_info.h:620 start create xwid step2

9月 28, 2023 10:05:08 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve

警告: Couldn't find file: /mnt/sdcard/jly1/

9月 28, 2023 10:05:08 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve

警告: Couldn't find file: /mnt/sdcard/jly1/a

[FEKit_]info: device_info.h:629 create xwid step2 complete ret is 71

[FEKit_]info: device_token.h:89 create new xwId complete

[FEKit_]error: o3_channel_encrypt.h:275 gen new channel

FEBound.transform(ac3d4779b87f770f889fe358e959fecd940e4bdd0294dc281e5bf57c6dbd2d61) => 70d1fff068dad596e3bd4a5ad0f0c9d4c7acf9942638c9aec111cfb044bc110e

[FEKit_]error: o3_channel_encrypt.h:491 est check: 57f6bc4b31127f9490dd904dc88ceb3da7a967d9a7e539570c1b22a63559a76902a82eaaeb057e432027bb36284d5e09

[FEKit_]error: ChannelManager.cpp:72 o3cm@S: GetSecConf, trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

uin = 2750556895, id = 0, sendPacket(cmd = trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, data = 0a0a476574536563436f6e66122102be84bcb1ab045f3bad0708534fd8dd3201e21742f4c3216311c7a2f3b033a21922423833633536323337366539323963626161353837383730666262373264386337663363666539373731646631343830386562333061613931373932336664643563652a48cda93630b607595b42eaeb55f5d3655464163e030b55674aa24c9eee6d32946fa13ccf7cf2ffc4a34ffdadcced09ea12c8c321b769d9cd27d088b81788faf6b29f0da18e312a99343220d9c90b0df21c1191719c7c80ee342b2cbf9cb318123b47f670fb549ab6934cee3a3057f6bc4b31127f9490dd904dc88ceb3da7a967d9a7e539570c1b22a63559a76902a82eaaeb057e432027bb36284d5e09)

FEBound.transform(7e0401020000032ec1c8c10005d430917d340c28060e1b00000000214e295000000000) => 19a920af2d951eaad574b6940112dc5e18d92a0d259cba951d951dd9ced0bc832ea62e

[FEKit_]error: device_info.h:179 jniGetAppVersionName:8.9.63

[FEKit_]info: device_info.h:538 538

[FEKit_]info: device_info.h:540 540

[FEKit_]info: device_info.h:542 542

[FEKit_]info: device_token.h:247 begin pack

[FEKit_]info: device_token.h:249 pack buff result len:1412

[FEKit_]info: device_token.h:264 begin sendmessage : len :1412

[FEKit_]error: o3_channel_encrypt.h:442 ecdh repeat establish

FEBound.transform(940e43952664f82938215f9e5836a42d472a3acadb2ea16d8346091e1c54bbc2) => c7acf3ca5558aca053306b6bbbefe774fb6fc58e0f6c937fecf21ceb1df28ad8

[FEKit_]error: o3_channel_encrypt.h:491 est check: cc97626f4aec7fa70c476a5d85bb6c3538a954ea57e410cc3ed966ddda67be857b21ccd7db1e472bece06f5f5a929be8

[FEKit_]error: ChannelManager.cpp:72 o3cm@S: getToken, trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

uin = 2750556895, id = 1, sendPacket(cmd = trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, data = 0a08676574546f6b656e122102be84bcb1ab045f3bad0708534fd8dd3201e21742f4c3216311c7a2f3b033a21922423833633536323337366539323963626161353837383730666262373264386337663363666539373731646631343830386562333061613931373932336664643563652acf0b63ec2a912921d9a22a83ee109fb8661445b0ba0f741a820866f472986d52314fd89a291f796a0604cacfd8ef14d757b5b9eaa0592bf034077903e3c84ef6b214e574d51db859120985aca26f77bf979cb0d6c5741440516f16eef3865645fd105a32db582ac0f416f0836006eb70df4f94e1c0105c3e54b830d831c2f1d2d141c2e5422e881b88a450e61f84e2b4c287a9bfdb9dc4c1f3805cbe9b7f30cd43ce21e2cf8b210d603ee87e8880b62e461a975b7258f766ab29c4a9ff93b967a063ef3484c9d535f4f67a4dfe8aa43447c65cac0a0f32b2765f433c7c0802cd7f5f8966d0c638c8220c0f04c1689a6b8d39aabc0665c50399a1bbc2d9ce5faed45ccbbf56fffa9926a81364b950ff5dd9675ce53a63ec12a6a70d99bfef8a3e7dfc0c1512da69169fe24fd51b240605a326022204a478b0ca0c2bcf229a0185238d36c0ed52294dca7120d23145d1f285953ba5b90fed4a2aefdfe861f5609b0bb6e2c5a10a38b73a7087dfc4846b36b1e2bc9326f160c1c852a2bc84ab96320f713a6c2cc8ee7a8b68d82b95204218343c55ba422dd0bc892458a6273d0960b5dd4a7abea2e1f618b06defeffb8b525d0fda1d2377297822bef469a233ff2a25ee64e7e5cf6da215a8f712d9f659bfb89f37f6c754aa85279bc60613f9faae29bf1572bd652d052b976d842a5eb1355915f95b4aa2c5ea443c17319a161c85961a78a375b210e6b905722f8b4d8ec24296188b6e05b3fc4aeb915202894ed094892cf20d01c0dbb1a3847ee8897b7b2920ce24c8e706f98d2d6fd639d303c6ea1e61698489e3342500a8a6d7652928d84bca222cbfef00270729536021abd6b0f41f1454188003db06a8750910ef369220591d08b195a19b2431c44968636aea7d5c25c93394453d1ccde91d13c8c90e8a3320e1e63693d4bd42e4f4f1b9a6a026787cebd7c55b79796f30d3b3f9b167a0d683475bcbe5f1086e99ced4e104384cbebbf7927fe201534758ac9a8aabaabe8bf768b314b936a574bebdb27eea2055086482032598f9b590b1330311375c0e8fc2b075766612fa90a9e56bf86794038bf7db2bbf1d280d3db83ebab2038c027fdca39ed268eca87b50d99e29908df474323848460fe996cb407147a7ed43e801f0499c9849eb8be9c2bc5eb23f1c30bdc7e3105340a66cd4135bf64a725ac3e4c47f6b21e278ee724fc773d7a46fef691b66789972da0a1c88814e68e16be83b3d937665fe2c550a7f11a5fae654db7a269c7b4ab52db31c308c22f7308f60ad490b4679ee6418b4d65d54bd4c211b21787e7215ebecca2edb49f291f67fa8e64a861f5e0d128c7a46aea034c5ab848cf608d91296a92c112ee92c3e5d5b07aa00dea35ff470e6147abc9fb7e59a69ee8e62d947fb4087c5fc9865dae590f304f556e140b19a0c5e70c1b4f4855ba7a4fd093ff3ca3312497c7689a67a4586f9a8aa97ef8047cf3bcb58e5dd1fb0530f6718d4db80a5d56b132b8773b011369f3959466389def37343a0393c67b9cc189e27b5f4fc195521f54285e4ad22587b126a73a22ffaf280ccf822eab17427dd52ccb54a54b1a8e1f26f39513ff900b994f5e2be5397dceef657040f7f0cb5f304a163168bcfad0789e17e3ca492bc4a4f58db651b556752592c816c8e43b57432da26d75ec4d8832bb5f54bdae725e07d8488ff51f0f5a42e27d7e9c2579ef20c632c2cbfc58343ee060f3bba5d636beacbbcaa06d6e3b76438ca46dcbc70c1b9e3b13ccc0dcead9ded25a33a2a2a3ff42c8bf7a0faf6f965e798a16bd1a02814aafa15ec7cb18a8405024dab1dc5d09a42ed420174f5fce141e42ce06bb43b8c009b5f3f0172999e423c587f3fa646ddd5b8bda261eccedcd2fc2b619aba5d8658dd93f6607a501fd28ce8a0c4f57c7047d9d64693ead6321f0d6f20708deb97a51f7f1066435b26af417f38f2358abe91fb8f5400c4f46f6db329b8f1330af0deaa01b3ad3b7bb8f6ff474bc584ca9ef4615577cc9d1be9dac2e1cc7918d659e5fb54958f4bd38f6b962c224a80daa7f8321c323c9654218183bcbff4fdc74321b9f126ea9b77c148c61650053220d9c90b0df21c1191719c7c80ee342b2cbf9cb318123b47f670fb549ab6934cee3a30cc97626f4aec7fa70c476a5d85bb6c3538a954ea57e410cc3ed966ddda67be857b21ccd7db1e472bece06f5f5a929be8)

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:wtlogin.exchange_emp

FEBound.transform(bb220102000003f5e8a168000f2ad074a513a16889f068000000007036783800000000) => b36320af2d951e8263a0a7940fdd6c107f50401d4a457c951d951db4fa7ed4832ea62e

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

FEBound.transform(9e310102000003c3fddcfd00044d90e2e2e6436a1fe7a500000000723d784100000000) => c9de20af2d951e6db6cfce94085c9ca84c78f31e73e990951d951dbef47efb832ea62e

FEBound.transform(b330010200000323f2c7c200067c287665fe70fdc133c5000000004568496e00000000) => b5d620af2d951eadb979b3940a73141baf1c8e34f2ff30951d951dfc4b50a9832ea62e

[FEKit_]info: ChannelManager.cpp:97 origin cmd:GetSecConf ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

[FEKit_]error: ChannelManager.cpp:100 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:GetSecConf

[FEKit_]info: task_handle.h:74 TaskSystem not allow

9月 28, 2023 10:05:10 下午 com.github.unidbg.linux.AndroidSyscallHandler getPipePair

信息: Return default pipe pair.

9月 28, 2023 10:05:10 下午 com.github.unidbg.linux.ARM64SyscallHandler fork

信息: fork

9月 28, 2023 10:05:10 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve

警告: Couldn't find file: /data/app/~~vbcRLwPxS0GyVfqT-nCYrQ==/com.tencent.mobileqq-xJKJPVp9lorkCgR_w5zhyA==/lib/arm64

[FEKit_]info: task_handle.h:74 TaskSystem not allow

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:wtlogin.login

FEBound.transform(bd060102000003e7c3f6d3000785c82315f190391cd27f00000000333e354500000000) => b8a820af2d951e08dc22da9406a534725f1eded070bbdb951d951d27fee5f0832ea62e

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

FEBound.transform(bf320102000003e9361326000c5ff825bd136d33f8106f00000000726f787200000000) => b1d320af2d951e005edb89940dfbc471b85057d788a57b951d951dbe4f7e4d832ea62e

QSign-Unidbg 白名单模式

[FEKit_]info: device_token_entry.h:87 initUin 2750556895

[FEKit_]info: device_info.h:583 start create xwid

[FEKit_]info: device_info.h:610 create xwid complete

[FEKit_]info: device_info.h:620 start create xwid step2

9月 28, 2023 10:19:04 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve

警告: Couldn't find file: /mnt/sdcard/jly1/

9月 28, 2023 10:19:04 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve

警告: Couldn't find file: /mnt/sdcard/jly1/a

[FEKit_]info: device_info.h:629 create xwid step2 complete ret is 71

[FEKit_]info: device_token.h:89 create new xwId complete

[FEKit_]error: o3_channel_encrypt.h:275 gen new channel

FEBound.transform(7d483d9f6002e61e12a317a884c902c8c53410a7920813d11629cc8df7275026) => 18f4c7c91d9b02cac9abe01a58c00ddf6fd96eecb696be14ce36b50126d9bc7b

[FEKit_]error: o3_channel_encrypt.h:491 est check: 0a230eaf5b01c3a5969ee75f91edfc44082414300484fa409b06a8bb029a99beeb5f85fd199886f340b81d1b12e2c19c

[FEKit_]error: ChannelManager.cpp:72 o3cm@S: GetSecConf, trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

uin = 2750556895, id = 0, sendPacket(cmd = trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, data = 0a0a476574536563436f6e66122102efb76ee599af6dbbe6aa1eba0a3bc8911248f8d7c75ed2bb673e9d35144d03c322423833633536323337366539323963626161353837383730666262373264386337663363666539373731646631343830386562333061613931373932336664643563652a48a1f0d5f456e85c685e00c19f0e8fccf89253594384d85f49c7c2ab43ea3baa15a2921ea4b8f9a7488d45fe020076364a035436a8fbb89c999eef6dee392ae2cdc8b5aea06928b58432205e368fc8d5be350f17631bef3aaa3f629cf752c82ff9d6eba8e4abce22cdbdf53a300a230eaf5b01c3a5969ee75f91edfc44082414300484fa409b06a8bb029a99beeb5f85fd199886f340b81d1b12e2c19c)

FEBound.transform(ffe00102000003e7deebae0005c0a896b9ebd7e2a1041a0000000039363d3c00000000) => 917620af2d951e089161249401c4e45bb675efbf9298b4951d951d2dfaecd8832ea62e

[FEKit_]error: device_info.h:179 jniGetAppVersionName:8.9.63

[FEKit_]info: device_info.h:538 538

[FEKit_]info: device_info.h:540 540

[FEKit_]info: device_info.h:542 542

[FEKit_]info: device_token.h:247 begin pack

[FEKit_]info: device_token.h:249 pack buff result len:1412

[FEKit_]info: device_token.h:264 begin sendmessage : len :1412

[FEKit_]error: o3_channel_encrypt.h:442 ecdh repeat establish

FEBound.transform(79bfc268ecdf16dff206de86927cc65cd43ec742f5f5be26662d80635b0cae3a) => 16e7361dd0bab216b992d402a3733f9987dc3f2f814ee1acae389d47b283e9cd

[FEKit_]error: o3_channel_encrypt.h:491 est check: 6708aad9c79cad943b7fcf05c2fdafe180ac62b9f2f51a419117ec280ad9ff4f5c7bf8b5b822d1f6832f4edda462941c

[FEKit_]error: ChannelManager.cpp:72 o3cm@S: getToken, trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

uin = 2750556895, id = 1, sendPacket(cmd = trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, data = 0a08676574546f6b656e122102efb76ee599af6dbbe6aa1eba0a3bc8911248f8d7c75ed2bb673e9d35144d03c322423833633536323337366539323963626161353837383730666262373264386337663363666539373731646631343830386562333061613931373932336664643563652acf0b1bc9a2c418bbb817f00108cedba25d6a6880a6f97ec39e1604aeb798dac136279de80033ad91ad0e2cf264b55bd50e13f5f16294ce06b1d2b99db92ce539712cd1f3bb28605a0e9f38500800188049a60ed0e73fb410f68d2e3c5a3c0f2aa34268e903ae4bee53c7c144205e986ba442fea5a41c881afad960adee3e19a07f269d2aa1819338f55daa0d3ed287eb41719b48fee7923368c57cfb68eb4666d48e59f525930e94356b88f2e033c6d57787da2ab3bc1278eae6e39c8d840921d98182a0907ba86dc3c3c75acc9255e8ff23209f130aefd3cf3025c607cbf8240cdf12fa123b2a836f3dfbf5ff6a6a189f0640c52c529f088e6007956db235d9cbb54d05269edc96a82c5f8d39e3304353e11242fdb7b6ebea14046646317e3b32a3c1b87c9599eadbc82c81be3c2b3dfec69471f19abebc99902af35e0eb09e4036aae6e1e59164aecee2c169dc33166bedd76fea9b920584dda3f6f132e0e033e04eaa9a05faaa1ec7f1b136f31210a4a036e6f4587f1065c631efc653aec87a37f4374e145a518eebb756add81509711ea20bb34411017e708eb9adcfd10b49132c96e4f7da67f1aef8333d2a0f21bc2947fb211851b1f79379af4eaca32fb8bed7bb113e9aeb5d923e01b78c3c6492fdcb2212899dd1d57b61f019d7ecbf212cf395a6f02ced9ed10e460fab233bfa8f61ea0a11405ff49653631fe067310fd003199e5d91299dde02d20de026b2cfedd81007dd4fc62b5029a5c8a0f01b7235320d7e5b62772612fd2214f702141322d1acceed77cb84f4194882079bfed669e6c613369ae351c7dbb41d63d17dccee35cfb455c44609511984b6d35487479464337d03ccff8dcb1ba7b58dde607559f9f8aa714369e3ba3b27d94bd568c0e074f0080f0f9e7a9b3b1553e19fd0392c36b1eb3e52da78d8abc73e44034cdc9d6cd8871b75ede408132e41c86a085766bef1de48a4b3621c5e5f8d8f4ad07182a2537e846d0e037b1b6cbe17a416593ac4a7af3526a6991fe868f19c4f3a2790089fcc7a8b0c29ed72bb4577059b08f3eb1d9f2cf8abcc107b03269b40d2d9e95cf72a2a968b53ee09589ead683528e98233e83a52c3dc26d43db892da7563a07a4a336d0542faf64309106394f713c3a2feaf5f78ad1699b4357668fc44758dedfd55b83c87b0dacb83d2a9404d8440542dc608e397481508d152f1c3b38a9b106c1cf22023ec8349fb603f7c3bfe2ee1f3f30f23db109112a29a59cf1a00a8c8ed9475db722721d9a438dd208ff81ca134215a7afcf3629f32f5a24127f445ea6bd1cdc72c9297a65d037c003cc0d9ad789987a1365634c488844dcddb08077b58d83173fa5e0605dfef8069bd8cba2e770436088de714f9201d1eb4994f568914c155f1b6c7db4e9c543da9a791786ec8deca245e16d999d8e3b6566a4263fe8d2c624b2c3efd498dbe219257d318407b1483f159240bb4cb654bff3e486ddccf405e6d058416ad202385934e1461014f1c9eeff23132951756519a34380b4ab849febea62a41fb7e6c5f8eb2e68bc236ea30287e10aa64a891d1e2dae0786abcf79c2f63599982e20c91b7cc2051f5179e4fa67362fbb073353850661333aff9a231f58c40f29376b5f25eddd701fd7cdeafd783f5ecd78feb8a37b4e4efbe83663e52c4d13fcce1f86943d3eae71f19e05a4ac142342d9ed2e269f4e2a144c4b0291ed2ea54654c5e1519ef22e3dba52e765e0d28f30ce55d6a265a441112c13466a144ed3ab25b3614117c9e96949169f78f58107755f0a78b69acc4136344d5625691b896e5f543932ada46e7ce577aca3cbedebc252fe37aa02e845de4d26b566bb9e809b02ed0778b73b43bdbe1caa2b6b2bc6341f95242680c70403f28a1c71712597d1811a5b247956e21a9fef1c7b370701e107125dd9905eb7feba7b67f81fc115f2fbb6efc829ba2bd361316ce67dff63ee81e67df2cb45a598fb034c304011ee810f93951bb758415d49f03d66716fb6b0e075e99f3d2b345b9c3bbf2df00389431b487172bd774a484509b49287a834534637ea3a3b10bec44950e13ac611728841107ad10996532205e368fc8d5be350f17631bef3aaa3f629cf752c82ff9d6eba8e4abce22cdbdf53a306708aad9c79cad943b7fcf05c2fdafe180ac62b9f2f51a419117ec280ad9ff4f5c7bf8b5b822d1f6832f4edda462941c)

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:wtlogin.exchange_emp

FEBound.transform(fb720102000003f5e7a297000db7b89d0740d9c1cebd17000000003226382a00000000) => 938320af2d951e826aaef09404b984542bf6e181fb82b5951d951d2e9aee12832ea62e

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

FEBound.transform(ff910102000003eaf4c5f4000242206505fdf11dc63a7700000000323e384200000000) => 919e20af2d951e03b77ac19403581c012f11a074f5f4d5951d951d2efeeefd832ea62e

FEBound.transform(ff7b0102000003c7c0c9c00003f7a039ba383e3bddb69c000000007224742c00000000) => 918520af2d951e68dd76bd940799ecccb2d4cbd60e8149951d951dbe987218832ea62e

[FEKit_]info: ChannelManager.cpp:97 origin cmd:GetSecConf ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

[FEKit_]error: ChannelManager.cpp:100 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:GetSecConf

[FEKit_]info: task_handle.h:74 TaskSystem not allow

9月 28, 2023 10:19:06 下午 com.github.unidbg.linux.AndroidSyscallHandler getPipePair

信息: Return default pipe pair.

9月 28, 2023 10:19:06 下午 com.github.unidbg.linux.ARM64SyscallHandler fork

信息: fork

9月 28, 2023 10:19:06 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve

警告: Couldn't find file: /data/app/~~vbcRLwPxS0GyVfqT-nCYrQ==/com.tencent.mobileqq-xJKJPVp9lorkCgR_w5zhyA==/lib/arm64

[FEKit_]info: task_handle.h:74 TaskSystem not allow

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:wtlogin.login

FEBound.transform(b849010200000330c0c9c00002f5d0a813b169f6b610cc0000000065636b6600000000) => b4fb20af2d951e55dd76bd9403956c4f55ee513b65a539951d951d4c4737af832ea62e

[FEKit_]info: qq_sign.h:132 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish

FEBound.transform(bf44010200000323c7c2f70006d9e8e50840918eb9e1a00000000073247b2500000000) => b1f920af2d951eadda7ec0940a1054a124f6d0586ae39d951d951db7987710832ea62e

Arknights Helper

基于 Mirai Console 的 明日方舟 助手插件

Release
Downloads
MiraiForum
DataHolder Test

使用前应该查阅的相关文档或项目
Arknights Helper 在2.0版本进行了重构 需要重新配置订阅 详见 方舟蹲饼

User Manual Permission Command Chat Command 指令

注意: 使用前请确保可以 在聊天环境执行指令
带括号的/前缀是可选的
<...>中的是指令名，由空格隔开表示或，选择其中任一名称都可执行例如/抽卡 十连
[...]表示参数，当[...]后面带?时表示参数可选
{...}表示连续的多个参数

本插件指令权限ID 格式为 xyz.cssxsh.mirai.plugin.arknights-helper:command.*, * 是指令的第一指令名
例如 /方舟公招 远程位 支援 的权限ID为 xyz.cssxsh.mirai.plugin.arknights-helper:command.ark-recruit

助手抽卡指令 指令 描述 /<gacha 抽卡> <one 单抽> [times]? 单抽times次，默认为1 /<gacha 抽卡> <one 十连> [times]? 十连times次，默认为1 /<gacha 抽卡> <detail 详情> 查看卡池规则 /<gacha 抽卡> <set 设置> [name] 设置卡池为name, 默认为NORMAL /<gacha 抽卡> <pool 卡池> [name] [set]? {rules} 设置卡池name的规则为rules，当set为true时设置为当前卡池

抽卡每一抽会消耗600合成玉，合成玉可以通过答题获得

ArknightsGachaCommand 卡池规则rules参数格式

rules参数从第二行起，按行分割
每行格式为规则干员名|星级|other|...:概率或者注释#...
星级用连续的*表示，例如*****表示五星干员，需要单行设置，设置的概率不包括已设置干员名
other表示剩余的其他干员
概率用小数表示，全部行的概率加起来的概率要为100%，即1.00
例子

/抽卡 卡池 限时寻访深悼 浊心斯卡蒂|凯尔希:0.014 赤冬:0.04 ******:0.006 *****:0.04 ****:0.48 other:0.42 助手答题指令 指令 描述 /<ark-mine 方舟挖矿 方舟答题> [type]? 机器人会提出一个问题 /<ark-question 方舟问题> <detail 详情> [name] 查看自定义问题的详情 /<ark-question 方舟问题> <list 列表> 列出已经设置的自定义问题 /<ark-question 方舟问题> <delete 删除> 删除指定问题 /<ark-question 方舟问题> <add 添加> 与机器人互动，输入条件，设置新问题 /<ark-question 方舟问题> <count 统计> 答题情况统计 回复选项序号A~Z，即算回答问题 type是提问问题类型，默认为全部类型
可选值 BUILDING, PLAYER, TALENT, POSITION, PROFESSION, RARITY, POWER, ILLUST,
VOICE, SKILL, STORY, ENEMY, WEEKLY, MUSIC, OTHER 回答了当前问题才会出现下一个问题 快速回答(规定时间的1/3内)会有相应奖励 群聊模式的其他群员亦可回答题目，但题目只能被回答一次，且其他人作为抢答者有相应奖励和惩罚 题目结构如下 [类型](得分) 问题 A. 选项 B. 选项 ... 助手公招指令 指令 描述 /<ark-recruit 方舟公招> {words} 查看关键词words的公招干员 words的数量为1~5
例如 /方舟公招 远程位 支援 助手材料指令 指令 描述 /<ark-item 方舟材料> [name] [limit]? [now]? 查看材料的关卡掉落率 /<ark-stage 方舟关卡> [name] [limit]? [now]? 查看关卡的材料掉落率 /<ark-zone 方舟章节> [name] [limit]? [now]? 查看地图所有关卡的材料掉落率 limit 是显示前多少项查询结果 now 是是否只显示当前开启关卡，默认为 true 助手蹲饼指令 指令 描述 /<ark-guard 方舟蹲饼> <detail 详情> 查看蹲饼详情 /<ark-guard 方舟蹲饼> <blog 微博> [contact] {blogs} 设置微博蹲饼内容 /<ark-guard 方舟蹲饼> <video 视频> [contact] {videos} 设置视频蹲饼内容 /<ark-guard 方舟蹲饼> <announce 公告> [contact] {announces} 设置公告蹲饼内容 /<ark-guard 方舟蹲饼> <weekly 周常> [contact] {weeklies} 设置周常蹲饼内容 contact 为群号或Q号 blogs 可选值为 ARKNIGHTS(官号), BYPRODUCT(朝陇山), MOUNTEN(一拾山), HISTORICUS(泰拉记事社)
例如 /方舟蹲饼 微博 123456 ARKNIGHTS MOUNTEN, 就订阅了官方号和一拾山 videos 可选值为 ANIME, MUSIC, GAME, ENTERTAINMENT
例如 /方舟蹲饼 视频 123456 GAME MUSIC, 就订阅了PV和音乐单曲 announces 可选值为 ANDROID, IOS, BILIBILI
例如 /方舟蹲饼 公告 123456 ANDROID, 就订阅了官服的公告 weeklies 可选值为 EVOLVE, MATERIAL, SPECIAL
例如 /方舟蹲饼 周常 123456 EVOLVE MATERIAL, 就订阅了物资筹备和芯片搜索 助手数据指令 指令 描述 /<ark-data 方舟数据> <clear 清理> 清理缓存 /<ark-data 方舟数据> <cron 定时> 重载定时设置

位于 Mirai-Console 运行目录下的 config/xyz.cssxsh.mirai.plugin.arknights-helper 文件夹下的 cron.json 文件

助手表情指令

** 需要 Meme Helper 作为前置**

指令 描述 /<ark-face 方舟表情> <random 随机> 随机发送一个表情 /<ark-face 方舟表情> <detail 详情> 查看表情详情 配置文件

位于 Mirai-Console 运行目录下的 config/xyz.cssxsh.mirai.plugin.arknights-helper 文件夹下的 config 文件

安装 MCL 指令安装

./mcl --update-package xyz.cssxsh:arknights-helper --channel maven-stable --type plugin

手动安装 从 Releases 或者 Maven 下载 mirai2.jar 将其放入 plugins 文件夹中 TODO 配置问题类型出现的概率 记录答题正确率 21/06/10 关卡规划 周常提醒 游戏公告 数据来源 游戏数据 Kengxxiao/ArknightsGameData 掉落数据 企鹅物流数据统计 语音数据 PRTS WIKI

Rss Helper

基于 Mirai Console 的RSS订阅插件

Release
Downloads
MiraiForum

指令

注意: 使用前请确保可以 在聊天环境执行指令
带括号的/前缀是可选的
<...>中的是指令名，由空格隔开表示或，选择其中任一名称都可执行例如/rss add https://github.com/cssxsh.atom
[...]表示参数，当[...]后面带?时表示参数可选
{...}表示连续的多个参数 下列指令的 URL 参数可以使用 base64 编码 后的形式

RssBaseCommand 指令 描述 /<rss> <add> [url] 添加一个订阅 /<rss> <list> 列出订阅列表 /<rss> <interval> [url] [duration] 设置订阅间隔, 单位分钟 /<rss> <stop> [url] 取消一个订阅 RssGithubCommand 指令 描述 /<rss-github> <releases> [owner] [repo] 添加一个Releases订阅 /<rss-github> <commits> [owner] [repo] 添加一个Commits订阅 /<rss-github> <tags> [owner] [repo] 添加一个Tags订阅 /<rss-github> <activity> [user] 添加一个Activity订阅 /<rss-github> <private> [user] [secret] 添加一个Private订阅 RssMikanCommand 指令 描述 /<rss-mikan mikan> <my> [token] 添加一个MyBangumi订阅 /<rss-mikan mikan> <classic> 添加一个Classic订阅 /<rss-mikan mikan> <bangumi> [id] [sub]? 添加一个Bangumi订阅 /<rss-mikan mikan> <search> [word] 添加一个Search订阅

指令基于 蜜柑计划

RssMoeCommand 指令 描述 /<rss-moe> <recent> 查看当季番剧TAG /<rss-moe> <search> [name] 搜索TAG /<rss-moe> <tags> {ids} 添加一个Tag订阅

指令基于 萌番组

RssTestCommand 指令 描述 /<rss-test> <build> [url] 测试一个订阅 /<rss-test> <ssl> 测试SSL /<rss-test> <clear> 清空种子文件 RssMiraiCommand 指令 描述 /<rss-mirai mirai> <category> [value] 添加标签订阅 /<rss-mirai mirai> <plugin> 添加插件发布订阅 /<rss-mirai mirai> <other> 添加其他项目发布订阅 RssHubCommand 指令 描述 /<rss-hub rsshub> <add> 交互添加RssHub订阅

交互过程举例

1748(1438159989) 23:29:58 /rsshub add QQBot(3337342367) 23:30:02 request returned 1899 routes QQBot(3337342367) 23:30:03 请输入路由名 1748(1438159989) 23:30:07 755 QQBot(3337342367) 23:30:07 (0, /755/user/:username) QQBot(3337342367) 23:30:08 /755/user/:username, 输入:username (置空可以输入#) 1748(1438159989) 23:30:21 akimoto-manatsu QQBot(3337342367) 23:30:26 1748 /rsshub add RSS订阅任务[秋元真夏(乃木坂46) - 755]已添加

配置文件 RssHubConfig.yml 可以配置rsshub的域名，即可以配置rsshub的源
此配置只对新的rsshub订阅订阅行为有效

配置 RssHubConfig domain rsshub 服务器的域名，默认为官方的 rsshub.app HttpClientConfig doh Dns Over Https Url (为空时关闭Doh，使用系统DNS since 1.0.0-dev-6) sni 需要移除 SNI HostName 的域名的正则表达式列表 proxy 代理列表 host: proxy, host=127.0.0.1时是全局代理 ipv6 doh 开启ipv6 支持 (since 1.0.3) RssContentConfig limit 订阅内容输出到QQ消息的最大长度，超过则只会输出 内容过长 TODO 翻译功能 代理支持 Doh支持 将Html转化为Mirai的MessageChain(主要目的是显示图片) 安装 MCL 指令安装

./mcl --update-package io.github.gnuf0rce:rss-helper --channel stable --type plugin

手动安装 运行 Mirai Console 生成plugins文件夹 从 Releases 下载jar并将其放入plugins文件夹中

Hammer Mirai Help

一个用以组织 Mirai Console 装载的插件们的帮助信息的 Mirai Console 插件；
为 Mirai Console 的用户提供统一的、简单的、可高度自定义的帮助信息展示方式；
为 Mirai Console 的插件开发者提供简单且统一的帮助信息展示方式和接口。
详细信息请查看 GitHub 页面 。

本插件针对的一些问题 用一个帮助指令显示机器人所有功能会让对话十分冗余； 自行编写并维护一个帮助指令比较麻烦，且可能容易漏掉新加的插件，对于硬编码实现的帮助指令每次需要重新构建部署； 大部分自动生成的帮助指令只能对插件注册的命令进行帮助提示，无法对基于事件系统的指令进行提示； 需要修改其他插件提供的帮助信息； 可能需要使用自定义图片的作为帮助指令，并且需要热重载来实时进行修改； 等。 功能 安装新插件后，用户只需要执行一行指令即可自动配置该插件的帮助信息： 对于接入本插件接口的插件，本插件会按照其配置的帮助信息进行配置； 对于未接入本插件接口的插件，本插件会依据其注册的指令自动生成帮助信息。 对于用户来说，只需要通过修改配置文件就可以修改如下的信息： 触发帮助的指令前缀（可以使用正则表达式匹配）； 指定插件的帮助信息是否启用； 指定插件的名称以及别名； 指定插件的详细帮助信息内容（可以设置为图片）； 用户想要看到指定插件的帮助信息所需要的权限（可以为空）。 对于插件开发者来说，接入本插件十分简单： 对于 JVM 插件，通过本插件提供的 SDK 在插件代码添加几行代码即可进行配置； 对于其他插件，只需要在指定目录生成一个配置文件即可。 无插件依赖要求，接入本插件的接口后不安装本插件无法使用 help 功能，但可以正常运行。 效果图

preview1.png
preview2.png
preview3.png

如果觉得有用的话求个Star和回帖啵啵QwQ

更新

使用Pandora_chatGPT白嫖gpt3.5
也可选择使用chatGLM api，用的多的话每个月需要爆几块钱金币
搜图优化，现支持sauceno、TraceMoe、Ascii2D、iqdb、e站
搞了个搭建工具，可能会方便一点

项目地址

项目地址

功能

发送@bot 帮助 以查看功能列表

图片相关 获取壁纸 @bot [数量]张[tag] #获取[数量]张标签为[tag]的图，可传r18参数但可能发不出 2张(壁纸|图) # 区别于上一个指令，这里不用艾特且出图完全随机。满足如下正则表达式即可触发 r".*(壁纸|图|pic).*(\d+).*|.*(\d+).*(壁纸|图|pic).*" 图片评级(成人指数) ping[图片] 搜图 搜图[图片] ai回复 /p[你的文本，不要带括号] config/token.txt中填写你的token，获取方式见https://ai-20230626.fakeopen.com/auth /poe[你的文本，不要带括号] 你需要填写api.yaml中的内容，抓取方式看https://github.com/avilliai/Poe_QQ /rwkv[你的文本，不要带括号] 需要在本地部署rwkv模型，具体看https://www.bilibili.com/video/BV1hM4y1v76R/?vd_source=b41b8c06d400241b8d0badbe1f821ec9 自定义回复 开始添加 #此指令用于开始词库添加，仅在当前群生效 删除#关键词 #例如　删除#孙笑川 用于删除指定回复　 del#关键词 #直接删除整个关键词以及所有回复 *开始添加 #为所有群的词库添加 *del#关键词 #为所有群的词库删除 导入词库　　　　　　　#从config/词库.xlsx导入词库 nameXXX #设定bot对你的特殊称谓为XXX，例如 name丁真珍珠　

除此之外，你也可以打开data/autoReply/lexicon进行修改，完成后在群内发送 导入词库

在这个文件夹下，分为三类词库

共有词库 专有词库 初始词库 public.xlsx 群号.xlsx init.xlsx 专有词库无匹配结果时使用共有词库 各群群内专用 各群创建专有词库时的初始添加内容 字符串相似度匹配 正则匹配 /

总之就是所有群创建专有词库的时候，都是从init.xlsx复制而共有词库是bot内部预设的一大堆回复。

你可以添加语音回复，但回复本身就有一定几率转为语音回复。

vits语音合成

使用sp查看所有可用角色，或@bot 可用角色

xx说 yourText # 通过角色名，指定一个角色模型 xx中文yourText # 此模式下输出为中文 xx日文yourText #输入日文，输出日文 你也可以不带角色名直接@bot 说 或者使用其他两个指令 导入模型：

在vits/voiceModel文件夹下新建一个文件夹放置.pth文件和config.json文件，重启main.py即可

信息查询 碧蓝档案wiki ba查询[角色名] # ba查询优香 查询一个角色信息 战双wiki 战双查询[角色名] 明日方舟wiki 方舟查询[角色名] 历史上的今天 @bot 历史上的今天 # 满足正则表达式 r".*史.*今.*|.*今.*史.*" 即可触发 天气查询 查询cityName #例如查询郑州 新闻 @bot 新闻 摸鱼人日历 @bot 摸鱼 nasa每日天文 @bot 天文 好友与加群管理 加好友与加群 群内发送 签到 #跟随指引完成签到后大概一分钟后可添加好友，签到2天后可邀请bot加群

这将需要你的城市信息，仅用于获取天气信息以完善签到图片

群管 关键词审核 添加违禁词XXX 删除违禁词XXX @bot 查看违禁词 涩图审核撤回 设置审核密钥[apiKey] #需要先在群内设置一个单独的密钥以开启此功能,示例：设置密钥207b10178c64089dvzv90ebfcd7f865d97a #从https://www.moderatecontent.com/获取,master使用此指令无论输入什么密钥都将默认采用api.yaml中的审核密钥。例如 设置审核密钥1163yyfahf /moderate #开启/关闭本群涩图审核 /阈值50 #设置撤回阈值为50，越涩的图对应的数值越高。阈值越小越容易撤回图片 定时任务 小功能 截图#url #打开指定网页并截图 meme #抽取一张meme图 运势 #是阿喵喵版本的运势卡 今日塔罗 #塔罗牌 /苏联笑话 #还有/法国笑话 等类似指令 /cp user1 user2 # xxs最喜欢的cp文，但有一说一文笔真不咋地(不是我写的) 干员生成 #我超，粥 原神，启动 # 原神抽签 @bot 诗经 #获取一篇诗经 @bot 周易 #高科技算命 master指令 设定角色#角色名 #为语音功能设置一个默认的角色 授权#qq号 #给一个用户授权(群内发送) 授权群#群号 #授权群的同时会自动创建一个词库 退群#群号 #退出指定群 /bl add qq号 #拉黑一个用户 /bl remove qq号 #取消拉黑 /blgroup add 群号 /blgroup remove 群号 notice # 群发通知用

以上是项目中实现的功能
如果想要实现bot菜单上的所有功能，你还需要额外安装以下几个插件

Mirai点歌插件 PetPet fireWatch

https://github.com/mamoe/mirai上
关于mirai使用的指导是这么写的：

快速使用：
用户手册: UserManual
如果你希望快速部署一个 Mirai QQ 机器人，安装插件、并投入使用，请看这里
论坛: Mirai Forum
Mirai 只有唯一一个官方论坛 Mirai Forum
在线讨论: Gitter

这个手册只告诉我们怎么下载一个MCL和部署使用它，但是这个MCL和https://github.com/mamoe/mirai/releases一点关系没有，如果我想用最新的mirai，或者某个指定版本的mirai，不应该是从https://github.com/mamoe/mirai/releases下载，安装部署再使用吗？

跪求大侠指导

JNIEnv->FindClass(com/tencent/mobileqq/channel/ChannelProxy) was called from RX@0x40552ee4[libfekit.so]0x1d2ee4 2023-09-26 08:41:13 I/QSecJni: Accept com/tencent/mobileqq/channel/ChannelProxy->sendMessage(Ljava/lang/String;[BJ)V JNIEnv->GetMethodID(com/tencent/mobileqq/channel/ChannelProxy.sendMessage(Ljava/lang/String;[BJ)V) => 0x1577dfe1 was called from RX@0x40553434[libfekit.so]0x1 d3434 JNIEnv->SetByteArrayRegion([B@72e206d2, 0, 1688, RW@0x41125000) was called from RX@0x40553460[libfekit.so]0x1d3460 2023-09-26 08:41:13 V/QSecJni: uin = 2922898334, id = 2, sendPacket(cmd = trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, data = 0a08676574546f6b656e1221 02d27c5c92fca0ee72a82509b3f67635485425392abfc89fc77412e961172af7fe22423833633536323337366539323963626161353837383730666262373264386337663363666539373731646631 343830386562333061613931373932336664643563652ace0b43e811544f5f463b50e7f05913fbdb8489fbb69771931ce7371ba8a5d350bf1cdbf360067a89fcef326e119d6a7283f8c0e3442f15c2 43f277af264442beb1bf6447b53e767b354a64932d5a01bef87ee74d7731fc2f7ac0c4f3573ef8da74cf09b9b8d8528e653589c14ad5cc5b003c67605919ba798c085053d534fb46bc8cc07bf374d9 f989e468828e2aa6677ccf7f5187b79b1b86645aca1d7824eb95ac0c89713622a61bb9acaa95b98b6d890ffe485fa638f285de768a3e629dbcc3de1809c5a40c03690a3808d6e6080cbcf56dd52758 f9d5dd77f440826ff36d7d90691ee3d7ca574e92d2ec95f5bcdb9d0702e3ad75ee8917499a7ad629d034d1faa1f0fb212d5d98b557be2c73db9e74a7d241f6596a421ce4921011398f477d548f0e97 ab8765d31bed5edf320fcac420e265935fc975797cc490b1e16f9de48b43da501abe2b93e55552c7b5f26ef2064b1cd5cbc2613ec06416b77c39b5690b7dc242f04e700b30beee9862c820a7f21378 5ea77cf8d0dc5a29ae588eed37260000b60be8394adfff9d09086ffaecd7c6cd15615ca08b0b692894e60fd42c78b4ba0bd094440d5d6e02d680a91f9b0ee33bd2ba1e4572b3a581e40ca272a0d1dc 9a4172afede58766faa8cb7990cc746c81fbbab97f11d15204b2bffb10545e66ffdee0aa8575051ba2ff0a5a11f362b36ac10764bcfa25f5f26cb23f886814de71f0cfa91682c1eb94a72ccd7647de 9420f470e72be377d2a52bd5302d87a9b22c3ceffc0c3ca0c5fd6bf8765f88d7428a301f3b86e3c564ffbf482d5d0ba2de6d33bc4a9aab8d1eb41216fd0a6b70960c55b61322a03c66262e3613be10 df96d56020476eb485426bd05d84ca8f5fba8fbf3183beb00020d9358665528041906fc189df3e59b4b3add576f2e496b82fe0394bb69c685e7e45707f857d997a3154f97ad3ae3598f3b3eae00f01 c565701b684efa54c581b37bf44fe03b79383e5133ad51d363f8778a0d12805e86a5a4ec49b38e3e8eb72762f84a4b2f2e083e8bcd444a0a19ac9b4ca0c4eb11eebf9dbbcdcf44fd0d85b70fd150f2 f95868d66c0817d5217bea389867b19b23517628de2f2ea24928ed1357ab0010c5e18e459e355d8cd8a4abcf72a383857c8c8ee4c4ccce976c950c38deb38a7c3d9b2d7b919b436f31734cb584b6e8 ba977830b65f47454166746b679d3e0cea7bc2d3f363c0f3c421aaada5dcc44f647cd81a86bab6228704135527c6789fc06828a43e2b5def4fd6121f1d16ce6b1f7bf8bd0df9efa4d0fc718d98dd85 ab50e62c7fbf01db97e443d6c4b6dec37590e1ae7ac9587d287e152a43000f019c7c2e182d6e1141209bc74f9454152c58bc356a2114957962b4a1b9cef4ab543b5b81a982790940ec00d4c32722b5 371599926bd7c16bc554fec8d0bb889ece5cb2fba65d17760c68a2676151731ca2853528900ad6a0d977f39810024f58db75ccaf6b3bc683d24b31d06ccf428724cc24e008267b84a89e9e5a9aac2c 814b497bf04a4698f8178791212063590368c3e4152477aeea9ce45ba5df627513001d6df22c4ef1efde1712f3336b584ff528699524d49adca496f3826e84519689f24cc30581b0abf41f872d968bb74bf03b658521ea718e506fa60e3072c9f89329e2649aafd1cdc2124d29aba74ef1228ef7fe5e262b0ea8c032342bf3c935060a9fa4cf5a3833930566f9e37abf076cc5a69ce2d86d1dd437d99c48c33e7a11279eed4c69a53b8a80e217c6773380655f0ac83bed12a5f24b84443fd57f545147d0b8e07683c0dace6d21f8a2f1f2d56e7e51925a2fa2624760e07795c88e9487e3e8f82b53ab96ff0d9464a0f243890b1c0fa4b36f6a67c1b6995d14c568c4fb4cb4409b3ee5a4d76ac0fb8b1ed6095c59b60a66319810699fa27ce39ada6378ea920dfb74e80a320c69f988314f5ad5dc70d221886f890829ee979be2b9911abc449ead53b35b2d4c7d7809c630f82918b530ce2601458abbb2fc8e3fa7d34e3c6f014bc1f13e8f4e3598fea7a8d3dacbc4b7709f80528a2a8dbc2cb9285bf41cab1c44aadecf7b746bdcab15181f6a2e523220f5110d854bd8c07eca53f6f243326ac3ec76201dc53763dbb632d37b88c0de353a30e98bba341d8e5c0da64412b29bccb6c05cb0260a0c76b8e7874f92a65d2833a117b071af6c106c13633f6df1614081094001) JNIEnv->CallVoidMethodV(com.tencent.mobileqq.channel.ChannelProxy@726d1f4e, sendMessage("trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish", [B@72e206d2, 0x2L)) was called from RX@0x4050e7e8[libfekit.so]0x18e7e8 JNIEnv->NewStringUTF("T3AlcS/C21Pm") was called from RX@0x404e9c98[libfekit.so]0x169c98 JNIEnv->CallVoidMethodV(com.tencent.mobileqq.qsec.qsecurity.QSec@1645d636, updateO3DID("T3AlcS/C21Pm")) was called from RX@0x4050e7e8[libfekit.so]0x18e7e8 JNIEnv->NewByteArray(12) was called from RX@0x404e92bc[libfekit.so]0x1692bc JNIEnv->SetByteArrayRegion([B@1d19ea97, 0, 12, unidbg@0xbffff241) was called from RX@0x404e92f8[libfekit.so]0x1692f8 JNIEnv->SetObjectField(com.tencent.mobileqq.sign.QQSecuritySign$SignResult@3d610aab, token [B => [B@1d19ea97) was called from RX@0x404e9ac0[libfekit.so]0x169ac0 JNIEnv->GetArrayLength([B@7f2fbb70 => 1326) was called from RX@0x404e24cc[libfekit.so]0x1624cc JNIEnv->GetStringUtfChars("8.9.73") was called from RX@0x404efcdc[libfekit.so]0x16fcdc JNIEnv->GetStringUtfChars("wtlogin.login") was called from RX@0x404efddc[libfekit.so]0x16fddc JNIEnv->NewStringUTF("[FEKit_]") was called from RX@0x4072a434[libfekit.so]0x3aa434 JNIEnv->NewStringUTF("qq_sign.h:142 [GetSign] cmd:wtlogin.login") was called from RX@0x4072a434[libfekit.so]0x3aa434

WifeYouWant

项目地址：https://github.com/MrXiaoM/WifeYouWant

「你想要的插件」系列作品

本插件移植自 椛椛 ᴮᴼᵀ

...

名场面
WifeYouWant.png

特性 每天可以从群友里随机抽一次老婆 (渣男!) 不想要的可以换 (渣男!!) 可设置只能抽和自己性别相反的人，也可以无视性别 可以设置能抽到自己 可以设置能 NTR (重复抽到群友) 安装

到 Releases 下载插件并放入 plugins 文件夹进行安装

2.11 或以上下载 WifeYouWant-*.mirai2.jar

2.11 以下下载 WifeYouWant-legacy-*.mirai.jar
安装完毕后，编辑配置文件作出你想要的修改。在控制台执行 /wuw reload 重载配置即可~

配置文件内有详细的注释，详见 源码

用法

随机挑选一位群友，在明天之前，无论怎么抽都是那位群友

抽老婆

抛弃老婆，重新抽一位群友

换老婆

关键词可在配置文件中修改

捐助

前往 爱发电 捐助我。

...

来自群组: SkyNet1748