NOT EXACTLY CRITICAL ERROR,UNLIKE LOG4J!!!
F3F5 opened this issue · 16 comments
[14:12:27 ERROR]: [org.bukkit.craftbukkit.v1_12_R1.CraftServer] null initializing ProtocolLib v5.0.0-SNAPSHOT-b618 (Is it up to date?)
java.lang.ExceptionInInitializerError: null
at com.comphenix.protocol.PacketType.getLookup(PacketType.java:749) ~[?:?]
at com.comphenix.protocol.PacketType.fromCurrent(PacketType.java:944) ~[?:?]
at com.comphenix.protocol.injector.packet.PacketRegistry.associatePackets(PacketRegistry.java:254) ~[?:?]
at com.comphenix.protocol.injector.packet.PacketRegistry.createOldRegister(PacketRegistry.java:146) ~[?:?]
at com.comphenix.protocol.injector.packet.PacketRegistry.initialize(PacketRegistry.java:283) ~[?:?]
at com.comphenix.protocol.injector.packet.PacketRegistry.getClientPacketTypes(PacketRegistry.java:314) ~[?:?]
at com.comphenix.protocol.injector.PacketFilterManager.(PacketFilterManager.java:117) ~[?:?]
at com.comphenix.protocol.injector.PacketFilterBuilder.build(PacketFilterBuilder.java:120) ~[?:?]
at com.comphenix.protocol.ProtocolLib.onLoad(ProtocolLib.java:175) ~[?:?]
at org.bukkit.craftbukkit.v1_12_R1.CraftServer.loadPlugins(CraftServer.java:323) ~[patched_1.12.2.jar:git-Reaper-a5f3c34]
at net.minecraft.server.v1_12_R1.DedicatedServer.init(DedicatedServer.java:223) ~[patched_1.12.2.jar:git-Reaper-a5f3c34]
at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:638) ~[patched_1.12.2.jar:git-Reaper-a5f3c34]
at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
at com.comphenix.protocol.PacketType.formatClassName(PacketType.java:880) ~[?:?]
at com.comphenix.protocol.PacketType.(PacketType.java:1099) ~[?:?]
at com.comphenix.protocol.PacketType.(PacketType.java:1078) ~[?:?]
at com.comphenix.protocol.PacketType$Play$Client.(PacketType.java:413) ~[?:?]
... 13 more
b614 my last used and after deleting new version not working( i don't know maybe b615 and new works) but last no
I don't think changing the title to a BS clickbait in an attempt to gain the dev's attention will bring you any closer to a fix.
Report the issue after checking it hasn't been reported before, provide useful information like server version and stay patient.
Я не думаю, что изменение заголовка на BS clickbait в попытке привлечь внимание разработчика приблизит вас к исправлению. Сообщите о проблеме после проверки того, что о ней не сообщалось ранее, предоставьте полезную информацию, такую как версия сервера, и сохраняйте терпение.
many owners has same problem. for me this is critical
It's still not a critical error "like log4j". You try to frame this being like the exploits Log4J had that would allow hijacking a server and stealing data. It's not. So stop the BS, use a proper title and wait.
It's still not a critical error "like log4j". You try to frame this being like the exploits Log4J had that would allow hijacking a server and stealing data. It's not. So stop the BS, use a proper title and wait.
yeah, sorry
