Environment
- Minecraft: 1.21.11, Fabric
- ClientID version: [1.1.4-1.21.11]
requireMod in config: [true]
- Server topology: TCPShield -> Velocity -> Fabric backend (mentioning for completeness, though this looks unrelated to networking)
Description
After switching our mod-list checker from another plugin to ClientID, we started seeing minecraft:barrier items appear in the world exactly at the location where a player joins/spawns in. They render like normal dropped items (the usual floating/bobbing animation - falling, rising, falling again) but cannot be picked up.
Steps to reproduce
- Join the server with ClientID installed on both client and server.
- Observe barrier "items" appearing right where you spawn in.
- Leave and rejoin - additional barrier items appear alongside the previous ones. They accumulate; old ones don't disappear.
- Reproduces identically on a completely fresh world with no prior player or world data, so it isn't tied to corrupted world/chunk data.
What we've ruled out
/kill @e[type=item] at the location has no effect on them.
/data get entity @e[x=<x>,y=<y>,z=<z>,distance=..3,limit=1] at the exact coordinates returns "No entity was found" - there is no real server-side entity there at all, of any type.
- Not caused by corrupted world/chunk data, since it reproduces identically on a brand-new world.
- This doesn't happen to player who are in player bypass list in config
Happy to provide full logs, a screen recording, or test specific builds if that helps track it down.
Environment
requireModin config: [true]Description
After switching our mod-list checker from another plugin to ClientID, we started seeing
minecraft:barrieritems appear in the world exactly at the location where a player joins/spawns in. They render like normal dropped items (the usual floating/bobbing animation - falling, rising, falling again) but cannot be picked up.Steps to reproduce
What we've ruled out
/kill @e[type=item]at the location has no effect on them./data get entity @e[x=<x>,y=<y>,z=<z>,distance=..3,limit=1]at the exact coordinates returns "No entity was found" - there is no real server-side entity there at all, of any type.Happy to provide full logs, a screen recording, or test specific builds if that helps track it down.