-
Bug
-
Resolution: Works As Intended
-
None
-
Minecraft 15w34d, Minecraft 15w39c, Minecraft 15w43a
-
Confirmed
When fixing this, please consider also disabling non-op player from using spawn_eggs or use another way to prevent MC-75630 from happening.
General overriding problem
When you use a spawn egg to override the Entity of a spawner, it will only replace the id tag in the id tag in the EntityTag of the spawn egg.
This means other tags are still contained.
/setblock ~ ~1 ~ mob_spawner 0 replace {SpawnData:{id:Sheep,Color:1},Delay:32767,MinSpawnDelay:32767,MaxSpawnDelay:32767,SpawnCount:1,SpawnRange:1}
– Changing to Guardian spawner –
{ MaxNearbyEntities:6s, RequiredPlayerRange:16s, SpawnCount:1s, SpawnData:{ Color:1, id:"Guardian" }, MaxSpawnDelay:32767s, Delay:19754s, x:-481, y:57, z:-496, id:"MobSpawner", SpawnRange:1s, MinSpawnDelay:32767s, SpawnPotentials:[ 0:{ Entity:{ Color:1, id:"Guardian" }, Weight:1 } ] }
Overriding with spawn_egg containing EntityTag
If the spawn egg contains other NBT data, it will ignore it and only change the id.
/give @p spawn_egg 1 0 {EntityTag:{id:FallingSand,Block:stone}}
- is duplicated by
-
MC-69879 Spawn egg names not saved when putting mob egg inside mob spawner
- Resolved
-
MC-102829 Custom spawn eggs not working on spawners
- Resolved
-
MC-186258 named spawn eggs do not work in spawners
- Resolved
-
MC-186618 Unable to switch between fox & artic fox within a spawner
- Resolved
-
MC-259947 Falling block spawn egg with BlockState will not used for monster spawner
- Resolved
-
MC-276526 When using custom spawn eggs made using new entity data component on a spawner, it ignores nbt data provided by the entity data component
- Resolved
- relates to
-
MC-85340 Passengers Tag doesn't work with entity_data component on items
- Open
-
MC-95437 Inconsistent entity data overriding when using spawn eggs on spawners
- Resolved