mojira.dev
MC-44904

Mobs Can Spawn With The Same UUID As Other Mobs In World

I Used The Command

/summon Zombie ~ ~ ~ {UUID:11111111-1111-1111-1111-111111111111}

And A Zombie With That UUID Was There, But When I Summoned Multiple And Used /kill @e[type=zombie] It Only Killed One, And In The Console It Sayed IT Killed All Of Them. When You Type /kill @e[type=zombie] Again, It Will Say 'Could Not Find Entity' A Bunch Of Times.These Are Not Ghost Mobs, And They Will Attack, Deal Damage,And Get Hurt By Anything.

Linked issues

Attachments

Comments 20

Please do not mark unreleased versions (anything starting with "Future Version") as affected. You don't have access to them yet.
Also, are you certain these other zombies weren't assigned other UUIDs, considering they are supposed to be unique?

Yes, There At The Same UUID, Because The [UUID] Test Works for Testfor / Tp ect

Still in 14w03b.

The bug here is that you had multiple entities with the same UUID, not that you couldn't kill them. There should only be one entity per UUID.

Can't you just make it that there can only be one entity per UUID?

10 more comments

this error is fixed in 15w31c by making summon check if it can summon a mob with that uuid and will respond with:"Unable to summon object" if a mob with that uuid already exists.

UUIDs can no longer be specified via commands (it is now ignored).

Not quite true, see Searge's comment on MC-86082.

UUIDs are now truly unique. It's no longer possible to spawn an entity with a particular UUID if one already exists with that UUID. I believe this was fixed in one of the early snapshots, though I'm not sure which one.

The UUID nbt tag is no longer parsed check MC-86082, Sarge commented there. It is fixed in version 33c.

Joshua cooper

(Unassigned)

Community Consensus

mob

Minecraft 14w02b, Minecraft 14w02c, Minecraft 14w03a, Minecraft 14w03b, Minecraft 1.8.1, Minecraft 1.8.3, Minecraft 1.8.8

Minecraft 15w47c

Retrieved