NoAI Shulker Peek tag can't register when summoned riding normal Armor Stands
Summoning shulkers which rides normal-size armor stands won't register its Peek tag value.
To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Passengers:[{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}
Created Issue:
NoAI Shulker; Peek Tag bugs when summoned riding Armor Stands
Case 1:
Summoning shulkers which rides normal-size armor stands won't register its Peek tag value.To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Passengers:[{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}Case 2:
Summoning shulkers which rides small armor stands and has a Peek value greater than or equal to 1 acts normally, but if you die, visually it resets back to 0, but internally it is still the same (proven by overwriting with /data merge).
Also, when trying to step on it in this case, it somehow acts like glitched barriers.To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Small:1b,Passengers:[{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}
/kill
/data merge entity @e[type=minecraft:shulker,limit=1,sort=nearest] {Peek:100b}
Stepping on top of that closed shulker will glitch the player in terms of position
Case 1:
Summoning shulkers which rides normal-size armor stands won't register its Peek tag value.To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Passengers:[{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}Case 2:
Summoning shulkers which rides small armor stands and has a Peek value greater than or equal to 1 acts normally, but if you die, visually it resets back to 0, but internally it is still the same (proven by overwriting with /data merge).
Also, when trying to step on it in this case, it somehow acts like glitched barriers.To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Small:1b,Passengers:[{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}
/kill
/data merge entity @e[type=minecraft:shulker,limit=1,sort=nearest] {Peek:100b}
Stepping on top of that closed shulker will glitch the player in terms of positionSummoning shulkers which rides normal-size armor stands won't register its Peek tag value.
To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Passengers:[\{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}
NoAI Shulker Peek Tagbugswhen summoned riding Armor StandsNoAI Shulker Peek Tag can't register when summoned riding Normal Armor Stands
Summoning shulkers which rides normal-size armor stands won't register its Peek tag value.
To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Passengers:[\{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}Summoning shulkers which rides normal-size armor stands won't register its Peek tag value.
To reproduce:
/summon minecraft:armor_stand ~ ~ ~ {Passengers:[{id:"minecraft:shulker",NoAI:1b,Peek:100b}]}
is duplicated by
relates to
relates to
Dupe of
Not sure if this is quite as useful, but I've found that this actually has some interesting buggy effects on NoAI Shulkers too. When teleported by the /tp command, the shulkers appear to close, yet they keep the Peek NBT. This might not be related, but it also seems to cause shulkers that are riding a teleported entity to do the same. What is problematic is that this also causes MC-254449, where the shulkers retract due to being teleported with their vehicle on the client but remain open on server (which can cause sort-of softlocks where the ghost-block like effect makes you unable to move).
Please only report 1 issue per ticket.
Aight, editing this.
The name is kind of misleading, this seems to happen when shulkers are spawned riding any mob and causes (possibly seperate issue) them to reset their peek after using /ride. This is only client side though, which causes your character to start glitching through like it's a ghost block.
This isn't an issue with the /ride command, but for the /summon. Never tested with different mobs though, only armor stands.
I think I found the cause! Likely related to MC-216251, Shulkers will close when moved at all. Normally this works fine, but if the shulker is the passenger of an entity and the entity moves, the shulker still closes as if it was teleported. The server doesn't register this (nor does its nbt data if it is NoAI) causing the ghost-block-like effect that relates this to MC-156980.