MiraiForum

    • 注册
    • 登录
    • 搜索
    • 热门
    • 最新
    • 未解决
    • 标签
    • 群组
    • 友情链接
    1. 主页
    2. smilecat2788
    3. 帖子
    S
    • 资料
    • 关注 0
    • 粉丝 0
    • 主题 1
    • 帖子 8
    • 最佳 0
    • 有争议的 0
    • 群组 0

    smilecat2788 发布的帖子

    • RE: GitHub Helper / GitHub Notice 订阅插件

      非法参数
      command owned by github-helper v1.4.1
      net.mamoe.mirai.console.command.descriptor.CommandArgumentParserException: 无法解析 mamoe/mirai 为 Format

      这种报错是什么情况
      日志:
      2023-12-08 19:35:10 I/github-helper: repo-commit with 212famliy/Mecanum-wheel run start
      2023-12-08 19:37:33 V/Bot.483392198: Group(480460678) <- 非法参数
      command owned by github-helper v1.4.1
      net.mamoe.mirai.console.command.descriptor.CommandArgumentParserException: 无法解析 mamoe/mirai 为 Format

      发布在 插件发布
      S
      smilecat2788
    • RE: qsign —— 签名 不要指望用来解决code=45

      我尝试更新了java,没有出现那些问题了
      image.png
      但是有了新的报错
      image.png
      2023-10-10 23:48:58 I/Bot.483392198: Bot cancelled: Bot closed
      2023-10-10 23:48:58 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: java.lang.IllegalStateException: running
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.AbstractEmulator.emulate(AbstractEmulator.java:352)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.thread.Function64.run(Function64.java:39)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.thread.MainTask.dispatch(MainTask.java:19)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.thread.UniThreadDispatcher.run(UniThreadDispatcher.java:175)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.thread.UniThreadDispatcher.runMainForResult(UniThreadDispatcher.java:99)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.AbstractEmulator.runMainForResult(AbstractEmulator.java:340)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.arm.AbstractARM64Emulator.eFunc(AbstractARM64Emulator.java:262)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.Module.emulateFunction(Module.java:163)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.linux.android.dvm.DvmObject.callJniMethod(DvmObject.java:135)
      at qsign-1.1.0-beta.mirai2.jar//com.github.unidbg.linux.android.dvm.DvmObject.callJniMethodObject(DvmObject.java:93)
      at qsign-1.1.0-beta.mirai2.jar//com.tencent.mobileqq.qsec.qsecdandelionsdk.Dandelion.energy(Dandelion.kt:11)
      at qsign-1.1.0-beta.mirai2.jar//moe.fuqiuluo.api.UnidbgFetchQSign.customEnergy(UnidbgFetchQSign.kt:38)
      at qsign-1.1.0-beta.mirai2.jar//moe.fuqiuluo.api.UnidbgFetchQSign.customEnergy$default(UnidbgFetchQSign.kt:27)
      at qsign-1.1.0-beta.mirai2.jar//top.mrxiaom.qsign.QSignService$encryptTlv$1.invokeSuspend(QSignService.kt:65)
      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 qsign-1.1.0-beta.mirai2.jar//top.mrxiaom.qsign.QSignService.encryptTlv(QSignService.kt:64)
      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)
      ... 6 more
      Caused by: [CIRCULAR REFERENCE: java.lang.IllegalStateException: running]

      2023-10-10 23:50:58 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

      发布在 插件发布
      S
      smilecat2788
    • RE: qsign —— 签名 不要指望用来解决code=45

      大佬,能不能帮我看看我这是什么情况,我在仓库里提交了issue,https://github.com/MrXiaoM/qsign/issues/14

      smilecat2788 created this issue in MrXiaoM/qsign

      closed mira启动报错 #14

      发布在 插件发布
      S
      smilecat2788
    • RE: 求助:如何使用jvm参数

      但是还是报code45禁止登录

      发布在 使用交流
      S
      smilecat2788
    • RE: 求助:如何使用jvm参数

      好的好的,谢谢大佬,我一直用的./mcl启动命令,怪不得加参数报错

      发布在 使用交流
      S
      smilecat2788
    • 求助:如何使用jvm参数

      446296fa-a85a-4ffe-883c-ff814c417ad7-image.png
      cssxsh大佬让我参考这个改一下超时时间,但是我不会用这jvm参数

      发布在 使用交流
      S
      smilecat2788
    • RE: Mirai Administrator 机器人管理插件,好友/群管理,黑名单,宵禁

      这个上线通知怎么触发,/perm add * xyz.cssxsh.mirai.plugin.mirai-administrator:online.include还是没有通知

      发布在 插件发布
      S
      smilecat2788
    • RE: Minecraft游戏服务端-QQ群消息代理插件[MinecraftServerListener]

      支持liunx吗

      发布在 插件发布
      S
      smilecat2788
    • 1 / 1