mojira.dev
MC-121868

UUID references to other entities are not stored as UUIDMost and UUIDLeast for tamable entities

The bug

Some entities which store UUID references to other entities do not store them as combination of UUIDMost and UUIDLeast but instead as string.

Storing it split is done by all newer entities like area_effect_cloud, evocation_fangs and llama_spit.

Affected entities

  • horses, mules, donkeys...: OwnerUUID

  • tamable entities (wolves, ocelots, ...): OwnerUUID

Comments 3

Also, player heads, plus all of the other ones that use playernames, not UUIDs

Noting: as of 18w01a, both Thrower and Owner on items no longer are strings and are compounds with L and M longs, being the uuid least and moost respectively.

It's not the same issue as here, but the way the UUID is stored is different on more than just string or longs:

What

UUID least

UUID most

UUID string

All entities

UUIDLeast

UUIDMost

Riding mobs

RootVehicle.AttachLeast

RootVehicle.AttachMost

Leashed mobs

Leash.UUIDLeast

Leash.UUIDMost

Breding mobs

LoveCauseLeast

LoveCausedMost

Tamed mobs

OwnerUUID

Converting zombie villager

ConversionPlayerLeast

ConversionPlayerMost

Thrown items

Owner.L

Owner.M

Llama spit

Owner.OwnerUUIDLeast

Owner.OwnerUUIDMost

Shulker bullet owner

Owner.L

Owner.M

Shulker bullet target

Target.L

Target.M

Dropped item owner

Owner.L

Owner.M

Dropped item thrower

Thrower.L

Thrower.M

Area effect cloud

OwnerUUIDLeast

OwnerUUIDMost

Evocation fangs

Owner.OwnerUUIDLeast

Owner.OwnerUUIDMost

Note the inconsistent usage of

...:{L,M}
...:{...Least,...Most}
...Least,...Most

Would be good if the way it was saved was consistent with these

In 20w18a they are all stored in the new format as an array of 4 Integers. This bug report can be closed.

marcono1234

(Unassigned)

Confirmed

(Unassigned)

UUID, tamable

Minecraft 17w45b, Minecraft 18w01a, Minecraft 18w11a, Minecraft 1.13-pre1

Retrieved