• This issue is not solved in a development build

Describe the bug
When server starts, more often than not i get an error when attempting to connect to server on my minecraft account.
Happens too often, and usually stops happening after i can attempt to sucessfully connect once.

To Reproduce
Steps to reproduce the behavior:
On connection to server, first connection gives out error,
On next connections it connects the player to the server normally, but can take a while and many attempts.
After first sucessfull connection usually player can connect normally untill next server restart

Expected behavior
Normal connection to server.

Screenshots
[17:47:15 ERROR]: Couldn't place player in world
net.minecraft.ReportedException: Sending packet
at net.minecraft.server.network.ServerGamePacketListenerImpl.send(ServerGamePacketListenerImpl.java:2169) ~[?:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.send(ServerGamePacketListenerImpl.java:2147) ~[?:?]
at net.minecraft.server.players.PlayerList.sendPlayerPermissionLevel(PlayerList.java:1143) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.players.PlayerList.sendPlayerPermissionLevel(PlayerList.java:1128) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.players.PlayerList.sendPlayerPermissionLevel(PlayerList.java:987) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.players.PlayerList.placeNewPlayer(PlayerList.java:297) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.network.ServerLoginPacketListenerImpl.placeNewPlayer(ServerLoginPacketListenerImpl.java:202) ~[?:?]
at net.minecraft.server.network.ServerLoginPacketListenerImpl.handleAcceptedLogin(ServerLoginPacketListenerImpl.java:183) ~[?:?]
at net.minecraft.server.network.ServerLoginPacketListenerImpl.tick(ServerLoginPacketListenerImpl.java:85) ~[?:?]
at net.minecraft.network.Connection.tick(Connection.java:593) ~[?:?]
at net.minecraft.server.network.ServerConnectionListener.tick(ServerConnectionListener.java:234) ~[?:?]
at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1573) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:447) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1394) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1171) ~[paper-1.20.jar:git-Paper-17]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:318) ~[paper-1.20.jar:git-Paper-17]
at java.lang.Thread.run(Thread.java:1570) ~[?:?]
Caused by: java.lang.NullPointerException: type cannot be null
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:907) ~[guava-31.1-jre.jar:?]
at com.comphenix.protocol.injector.StructureCache.getStructure(StructureCache.java:138) ~[ProtocolLib.jar:?]
at com.comphenix.protocol.events.PacketContainer.(PacketContainer.java:126) ~[ProtocolLib.jar:?]
at com.comphenix.protocol.injector.netty.manager.NetworkManagerInjector.onPacketSending(NetworkManagerInjector.java:96) ~[ProtocolLib.jar:?]
at com.comphenix.protocol.injector.netty.channel.NettyChannelInjector.processOutbound(NettyChannelInjector.java:553) ~[ProtocolLib.jar:?]
at com.comphenix.protocol.injector.netty.channel.NettyChannelInjector$2.doProxyRunnable(NettyChannelInjector.java:456) ~[ProtocolLib.jar:?]
at com.comphenix.protocol.injector.netty.channel.NettyEventLoopProxy.proxyRunnable(NettyEventLoopProxy.java:43) ~[ProtocolLib.jar:?]
at com.comphenix.protocol.injector.netty.channel.NettyEventLoopProxy.execute(NettyEventLoopProxy.java:252) ~[ProtocolLib.jar:?]
at net.minecraft.network.Connection.sendPacket(Connection.java:440) ~[?:?]
at net.minecraft.network.Connection.send(Connection.java:383) ~[?:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.send(ServerGamePacketListenerImpl.java:2161) ~[?:?]
... 16 more

Version Info
Latest spigot and latest release build
Tested on paper 1.19.4 to 1.20.4
Have same error on all builds and minecraft server versions i tested on.

Additional context
Add any other context about the problem here.

Please try again with the latest development build from https://ci.dmulloy2.net/job/ProtocolLib/lastSuccessfulBuild/artifact/build/libs/ - the issue should be fixed there