Jake Potrebic

I would open an issue on the tracker specific to your issue here, I couldn't find one that exactly matches up. Worst case it gets closed and duplicate and linked...

> I've already created an issue on the Mojang bug tracker, currently waiting to see where that goes. Oh lol, somehow I missed that at the bottom of your issue....

Are you sure the entities are **actually** despawning? Setting that tag isn't the only thing the game uses to know if the entity can be despawned.

Yes, the from bucket check should be enough to prevent despawning.

Yeah, [upstream](https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/2a381856b95784163eaca2213707bb48e1e2003e#nms-patches/net/minecraft/network/protocol/common/ServerboundCustomPayloadPacket.patch) just decided to remove the custom handling and handle everything as unknown.

It's possible this PR fixes the issue, but I haven't tested that exactly yet. https://github.com/PaperMC/Paper/pull/9258

Ok, I did verify that this is the case. I tested on 2 vanilla clients with no plugins. I did what was shown in the video, flew straight away, and...

I'm not sold on the format for the config with this change. There are several options that I can think of that I'd prefer ```yaml despawn-ranges: monster: hard: xz: 30...

To give a little more context, the broken and not good bukkit serialization system tries to deserialize that string as a list since it looks like `[item1, item2]`.

The EntityPickupItemEvent is just wrong right now. It is incorrect to pass the Item (entity) as the thing being picked up because in vanilla, the stack actually being kept by...