Bug http://paste.yu8.me/?529458af19f19be0#R5HrxQ8hNE6EdOLtsz3Y3bCwj11td7ycYHaGDEbpnrA=
Essentials v2.0.1-b501
spigot-1.12.1
Can confirm
@FrankHeijden What version of Essentials (/ess) and Spigot (/version) are you running?
@TheChampTF
Essentials v2.0.1-b501
CraftBukkit version git-Spigot-edd0396-2a927e8 (MC: 1.12.1) (Implementing API version 1.12.1-R0.1-SNAPSHOT)
This error just randomly occured at my console. and it spams like a lot. https://pastebin.com/BAX5xPgX
I see its a different error, but the same nullpointer
Same issue on just spigot 1.12.1 with essentials, latest version since I just pulled it from the devbuilds.
I'm seeing this same error a couple times a minute.
Essentials reloaded 2.0.1-b501.
CraftBukkit version git-Spigot-edd0396-2a927e8 (MC: 1.12.1) (Implementing API version 1.12.1-R0.1-SNAPSHOT)
This was caused by a removal of a deprecated method in Spigot 1.12.1:
Can confirm as well, happening on spigot 1.12.1.
Essentials dev 501
Paper dev 1170 (Spigot 1.12.1)
Pasting error on github so there is a copy here.
[13:43:27] [Server thread/ERROR]: Could not pass event PlayerInteractEvent to Essentials v2.0.1-b501
java.lang.NoSuchMethodError: org.bukkit.entity.Player.getTargetBlock(Ljava/util/HashSet;I)Lorg/bukkit/block/Block;
at com.earth2me.essentials.signs.SignPlayerListener.onSignPlayerInteract(SignPlayerListener.java:41) ~[?:?]
at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor252.execute(Unknown Source) ~[?:?]
at org.bukkit.plugin.EventExecutor$1.execute(EventExecutor.java:44) ~[patched_1.12.1.jar:git-Paper-1170]
at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:74) ~[patched_1.12.1.jar:git-Paper-1170]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[patched_1.12.1.jar:git-Paper-1170]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:514) ~[patched_1.12.1.jar:git-Paper-1170]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:499) ~[patched_1.12.1.jar:git-Paper-1170]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:235) ~[patched_1.12.1.jar:git-Paper-1170]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:202) ~[patched_1.12.1.jar:git-Paper-1170]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:198) ~[patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.PlayerConnection.a(PlayerConnection.java:987) ~[patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.PacketPlayInBlockPlace.a(PacketPlayInBlockPlace.java:26) ~[patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.PacketPlayInBlockPlace.a(PacketPlayInBlockPlace.java:5) ~[patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.PlayerConnectionUtils.lambda$ensureMainThread$0(PlayerConnectionUtils.java:14) ~[patched_1.12.1.jar:git-Paper-1170]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_144]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_144]
at net.minecraft.server.v1_12_R1.SystemUtils.a(SourceFile:46) [patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:843) [patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:424) [patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:767) [patched_1.12.1.jar:git-Paper-1170]
at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:665) [patched_1.12.1.jar:git-Paper-1170]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
Same problem
This server is running Paper version git-Paper-1170 (MC: 1.12.1) (Implementing API version 1.12.1-R0.1-SNAPSHOT)
I've submitted a PR (#1435) that should fix this. Could someone test the test build and confirm whether the issue is still there or is gone?
Worked for me!
Wouldn't it say EssentialsSpawn and EssentialsGEOIP are outdated if I only update the main plugin? @md678685
It did just startup normal for me
@Sikatsu Potentially, but since the test build doesn't change anything related to any of the other EssX modules, you can safely ignore it. You can also revert to the release build once the PR is merged.