Brad Larson

This may be related or may not be but this doesn't work on arrows.

execute @e[type=Arrow] ~ ~ ~ execute @e[type=Arrow,c=1,r=0] ~ ~ ~ say hi

There are still some border anomalies which my new video will cover. In my opinion to avoid issues it is still important to avoid chunk borders.

Just FYI I was the first one to bring up the whole 63 block thing. https://youtu.be/d58Ta7yg3Dc?t=13m32s You have to remember the clocking blocks on chunk borders will be counted for both chunks, so its wise to have no blocks clocking on chunk borders for this reason. On a side note I will be releasing a more updated best practices and optimizations video soon. This video will include info on this subject as well as lots of other areas.

http://prntscr.com/5t7nt6 Screenshot of arrows bouncing back

Confirmed still broken in 1.8.2 pre4. Its really easy to hit them with a arrows.

Perhaps projectiles should ignore armorstands with marker tags?

Please Reopen so I can vote!! =)

New crash report

I also see this happening in my vanilla client

Yes Ideally using an execute detect should work regardless of dimension. Cross dimension commands could be improved upon across the board.

Execute works on a person in the nether if the command is executed from within the nether as far as i can tell. The problem is more that I feel like if your in the nether NO command should execute positive from the overworld, or they should all execute correctly from the overworld.

Currently the problem I am having with it is if your in the nether, the detect bedrock and layer 0 does execute positive, if done from the overworld regardless if there is bedrock at layer 0 ( while in the nether ).

I hope it makes sense its a little bizarre and hard to explain.

A potential workaround if or until they can fix this.

How I did it was I got all the entities that I wanted to select ( by team ) and changed their scoreboard score to 1. then selected them based on that scoreboard score.

/scoreboard players set @e[r=3,type=ArmorStand] somescoreboard 1

/tp @e[type=ArmorStand,score_somescoreboard_min=1] ~ ~ ~ ~50 ~ ( or whatever you want to do )

I agree that targeting by team would be easier but this is a solution I am using till the decide if they want to make it possible or not.

Aaron PLEASE stop editing your comments after you post, re-read them carefully before you submit your posts. Every time you edit them it sends everyone watching this Bug which is 30 people.

So far I have gotten 20+ emails of you editing the post you made, this is pretty irritating.

Thank you.

I guess if everyone is happy with decorative entities being breakable by default then your correct its a feature request.

to be clear what I want is a solution not a workaround. I am not asking to make entities that are decorative, into blocks. You can agree with Searge if you like but I can also agree with Anon. Are banners and skulls blocks? Do you think they should be breakable too?

Currently the "workaround" technically works but is not ideal for these reasons.

1. Makes entity unbreakable for everyone not limited to Adventure mode players.
2. To summon these items that are decorations takes a lengthy command or command block. For artists or creative players this is a huge headache. One example is lets say I want to create a visual display of a few game recipes using a 3x3 grid of item frames, wow that will take a while, or make a town and put paintings in all the buildings.
3. Can you give someone an item with the ability to break an invulnerable entity? like you can give them the a shovel with the ability to only dig up dirt?

Invulnerable makes total sense and should stay in the game, and works great for entities that are animals and npcs and such, makes less sense for entities that are decorations, and technically is a WORKAROUND, but I think its not a solve.

I am not sure why your so passionate about keeping it harder for people who already have it hard. I am beginning to think you either don't understand what I am saying, or your just trolling. Hopefully this clears it up, if not ... well played troll.

I don't think it should matter what they are technically in the code. A cow is not a decoration, a sheep is not a decoration, a painting is a decoration. This obviously creates a development challenge for Mojang no one is disputing that. Thus the reason a bug exists. If they can make bunnies they can fix this.

I quote:

"[Mod] Anon Ymus added a comment - 14/Jul/14 7:09 PM

Paintings and Item Frames are entities that are used to represent a block, so they should never be breakable in Adventure Mode."

Case and Point.

I am not asking for it to be harder for people that want it to be breakable in adventure mode. I just want it to be a LOT easier to make it unbreakable for those of us who are using these entities ( that act as blocks ) for decorations for people in adventure mode. If it was unbreakable by default and you guys had to use summon commands to make breakable ones that would still be a shitty solution imo, I am sure Mojang will find a better way.

So why is everyone saying that is the correct workaround and proper method? I am confused.

I am still not on board with idea adventure mode players being able to break DECORATIVE blocks like paintings is working as intended.

So invulnerable tag only effects people in adventure mode, not people in creative or survival?

-Brad

I feel like there needs to be an easier way to make decorative blocks like paintings, item frames, etc. Without having to write a command block every single time I want to make one.

Are you able to give yourself an item that has this tag in creative then use it multiple times? Currently the only way I have been able to do it is by using a command block for each one individually, which seems pretty crazy.