[BUG] UUID error spawning armor stand millions of blocks away
v1-valux opened this issue ยท 1 comments
#### Issue Description:
Server console receives errors:
UUID of added entity already exists: class_1531['Armor Stand'/1643, l='ServerLevel[world]', x=22068880.50, y=1000.00, z=-4185487.50]
UUID of added entity already exists: class_1531['Armor Stand'/1644, l='ServerLevel[world]', x=16562064.50, y=1000.00, z=-22242911.50]
#### What happens:
Armor Stand spawns at given locations and is invisible.
I teleported to those positions and killed them with /kill @e[type=minecraft:armor_stand,distance=..100]
#### What you expected to happen:
No armor stand should spawn automatically (especially that far distances away from spawn/player)
#### Steps to reproduce:
- Install armor_statuses datapack
- Start server
...
Affected Versions (Do not use "latest"):
Minecraft: 1.19
Fabric Loader 0.14.8
Armor Statues: v2.8.4
Single Player and/or Server? Server
Optifine? No
Okay, I have cleared the issue..
it's not related to this datapack indeed.
Some other VanillaTweaks DataPacks like "Cauldron Concrete" and "Armored Elytra" contain this kind of behavior - And it's not a bug, it's a feature:
Have a look into the datapack (cauldron concrete for example).
There is a mcfunction named "summon_marker.mcfunction", which contains:
forceload add ~ ~
summon minecraft:armor_stand ~ ~ ~ {Marker:1b,NoGravity:1b,Invulnerable:1b,Invisible:1b,UUID:[I;-1600948966,746014296,-1654693205,1150598575]}
I guess it has to do with the feature of exchanging items when dropping them somewhere.. but don't ask me why..
remove the corresponding datapack, and your "problem" is gone :)
cheers