Bytenka
- BluHugo
- bluhugo
- Europe/Stockholm
- Yes
- No
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
MC-111328
If you summon a ArmorStand with a head rotation set like
{Head:[45f,0f,0f]}, it will work fine. But if you want to edit it with /entitydata or /tp command, it won't work. It's not a visual glitch because I quit and log back to the world and nothing happend...
EDIT:
Commands:
/entitydata @e [type=ArmorStand,r=3] {Pose:{Head: [45f,0f,0f] }} [WORK FINE]
/tp @e [type=ArmorStand,r=3] ~ ~ ~ ~ 45
Let's do a experiment :
Place 3 command blocks that you'll activate in this order :
/summon armor_stand ~ ~1 ~
{Tags:["A"],Marker:0}/entitydata @e[tag=A]
{Tags:["B"]}/execute @e[tag=B] ~ ~ ~ say test
Everything will work as expected, and the armor_stand will say "test".
Now kill the armor_stand, and change the 3rd command with this :
/execute @e[tag=B] ~ ~ ~ kill @e[r=0]Reactivate all the command blocks.
Strangely, the armor_stand won't be killed, and "Failed to execute 'kill @e[r=0]' as Armor Stand" will appear in the command output.
Kill the armor_stand again, and just set the marker's value in the 1st command block to 0.
Reactivate all the command blocks.
Now, the armor_stand was killed...
Initially, I thought that this bug is related to MC-88533, but the basic /summon armor_stand ~ ~1 ~
{Tags:["A"],Marker:1}& /execute @e[tag=A] ~ ~ ~ kill @e[r=0] works perfectly.
Let's do a experiment :
Place 3 command blocks that you'll activate in this order :
/summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:0} /entitydata @e[tag=A] {Tags:["B"]} /execute @e[tag=B] ~ ~ ~ say testEverything will work as expected, and the armor_stand will say "test".
Now kill the armor_stand, and change the 3rd command with this :
/execute @e[tag=B] ~ ~ ~ kill @e[r=0]Reactivate all the command blocks.
Strangely, the armor_stand won't be killed, and "Failed to execute 'kill @e[r=0]' as Armor Stand" will appear in the command output.
Kill the armor_stand again, and just set the marker's value in the 1st command block to 0.
Reactivate all the command blocks.
Now, the armor_stand was killed...
Initially, I thought that this bug is related to MC-88533, but the basic
/summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:1}&
/execute @e[tag=A] ~ ~ ~ kill @e[r=0]works perfectly.
Let's do a experiment :
Place 3 command blocks that you'll activate in this order :
/summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:1} /entitydata @e[tag=A] {Tags:["B"]} /execute @e[tag=B] ~ ~ ~ say testEverything will work as expected, and the armor_stand will say "test".
Now kill the armor_stand, and change the 3rd command with this :
/execute @e[tag=B] ~ ~ ~ kill @e[r=0]Reactivate all the command blocks.
Strangely, the armor_stand won't be killed, and "Failed to execute 'kill @e[r=0]' as Armor Stand" will appear in the command output.
Kill the armor_stand again, and just set the marker's value in the 1st command block to 0.
Reactivate all the command blocks.
Now, the armor_stand was killed...
Initially, I thought that this bug is related to MC-88533, but the basic
/summon armor_stand ~ ~1 ~ {Tags:["A"],Marker:1}&
/execute @e[tag=A] ~ ~ ~ kill @e[r=0]works perfectly.
I tested it again and it happend randomly... I think I have been unlucky in the video because I needed about 7 attempts until it happend again. Other thing : 30s before, they realize that they can jump... And yes, it seems like bugging only with repeating command blocks... Realy strange
My bad, I miserably failed the command.
Correct command is /entitydata @e[type=ArmorStand,r=3] {Pose:{Head:[45f,0f,0f]}}
...
But the command /tp @e[type=ArmorStand,r=3] ~ ~ ~ ~ 45 still won't work and I don't now why...
Back (or still, idk) in 16w42a for me.
Sorry for the mistake I've made... In the first command, the tag "marker" must be set to 1.
Still in 1.11-pre1. The only way to bypass that is by using @e[r=1,c=1]
Hum, you're certainly right. It seems like more MC-88533 related
(
{Tags:["A"],Marker:1}/summon armor_stand ~ ~1 ~
/execute @e[tag=A] ~ ~ ~ kill @e[r=0]
won't work now.
)
Still in 1.11, 1.11.1 and 1.11.2
Still in 1.11, 1.11.1 and 1.11.2