Can't /oi a specific player?
melaniebeedot opened this issue · 4 comments
Keep getting this error in console when we try to /oi this player:
[17:37:50 INFO]: melaniebeedot issued server command: /oi 1block2
[17:37:50 WARN]: [OpenInv] Task #1944167 for OpenInv v4.3.0 generated an exception
java.lang.NullPointerException: Cannot invoke "net.minecraft.server.level.WorldServer.getCraftServer()" because the return value of "net.minecraft.server.level.EntityPlayer.x()" is null
at net.minecraft.server.level.ServerPlayer.spawnIn(ServerPlayer.java:591) ~[?:?]
at com.lishid.openinv.internal.v1_19_R3.PlayerDataManager.loadPlayer(PlayerDataManager.java:127) ~[OpenInv.jar:?]
at com.lishid.openinv.OpenInv.loadPlayer(OpenInv.java:311) ~[OpenInv.jar:?]
at com.lishid.openinv.commands.OpenInvCommand.openInventory(OpenInvCommand.java:143) ~[OpenInv.jar:?]
at com.lishid.openinv.commands.OpenInvCommand$1$1.run(OpenInvCommand.java:98) ~[OpenInv.jar:?]
at org.bukkit.craftbukkit.v1_19_R3.scheduler.CraftTask.run(CraftTask.java:101) ~[paper-1.19.4.jar:git-Paper-484]
at org.bukkit.craftbukkit.v1_19_R3.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:483) ~[paper-1.19.4.jar:git-Paper-484]
at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1483) ~[paper-1.19.4.jar:git-Paper-484]
at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:447) ~[paper-1.19.4.jar:git-Paper-484]
at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1397) ~[paper-1.19.4.jar:git-Paper-484]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1174) ~[paper-1.19.4.jar:git-Paper-484]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:320) ~[paper-1.19.4.jar:git-Paper-484]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Not until I fix the bug on OI's end, yes. If the world has a different UUID it is a different world as far as MC's internals are concerned, even if the name matches.
You're trying to load a player who is in a world that no longer exists. Looks like Paper changed things again? We have a guard for Paper's patch of CB behavior already as discussed in #130, but I guess it isn't working properly any more.