CaaMoe / MultiLogin

外置共存
GNU General Public License v3.0
361 stars 56 forks source link

[错误报告] 无法在最新版 Velocity 上运行 #85

Closed MSDNicrosoft closed 1 year ago

MSDNicrosoft commented 1 year ago

BUG描述

环境

在启动服务端时抛出了如下日志内的异常,随后服务端关闭

重要声明

这个插件是初次使用

MultiLogin版本

0.5.2

系统架构

linux/amd64 与 windows/amd64

配置文件

与配置文件无关,第一次使用插件直接导致此问题

日志

[Velocity Async Event Executor - #0/ERROR] [multilogin]: An exception was encountered while loading the plugin.
java.lang.IllegalAccessError: class moe.caa.multilogin.velocity.injector.VelocityInjector tried to access protected field com.velocitypowered.proxy.protocol.StateRegistry.serverbound (moe.caa.multilogin.velocity.injector.VelocityInjector is in unnamed module of loader moe.caa.multilogin.loader.classloader.PriorAllURLClassLoader @6c15e8c7; com.velocitypowered.proxy.protocol.StateRegistry is in unnamed module of loader 'app')
    at moe.caa.multilogin.velocity.injector.VelocityInjector.inject(VelocityInjector.java:32) ~[?:?]
    at fun.ksnb.multilogin.velocity.main.MultiLoginVelocity.onInitialize(MultiLoginVelocity.java:58) ~[?:?]
    at fun.ksnb.multilogin.velocity.main.Lmbda$3.execute(Unknown Source) ~[?:?]
    at com.velocitypowered.proxy.event.UntargetedEventHandler$VoidHandler.lambda$buildHandler$0(UntargetedEventHandler.java:56) ~[velocity.jar:3.2.0-SNAPSHOT (git-697d08ba-b216)]
    at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:598) ~[velocity.jar:3.2.0-SNAPSHOT (git-697d08ba-b216)]
    at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:479) ~[velocity.jar:3.2.0-SNAPSHOT (git-697d08ba-b216)]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
    at java.lang.Thread.run(Thread.java:833) ~[?:?]

复现步骤

  1. 将插件移入 plugins 文件夹
  2. 启动最新版 Velocity

确认一遍

CaaMoe commented 1 year ago

感谢反馈,问题已修复,你可以在 Action 中获得修复版本下载链接

MSDNicrosoft commented 1 year ago

感谢,问题已解决。