Before 16w07a I could make a bunch of command block minecarts with some commands and one with kill command to clear them out.
/summon MinecartCommandBlock ~ ~ ~1
{
Command:"/say start",
Passengers:[
{id:"MinecartCommandBlock",Command:"/say 1"},
{id:"MinecartCommandBlock",Command:"/say 2"},
{id:"MinecartCommandBlock",Command:"/say last"},
{id:"MinecartCommandBlock",Command:"/kill @e[type=MinecartCommandBlock,r=0]"}
]
}Since 16w07a they doesn't disappear. In 16w06a they worked fine. Ran once and all disappeared after running the /kill minecart. Now kill with r=0 doesn't kill anything.
Linked issues
is duplicated by 2
relates to 1
Comments 17
I found out that even typing into chat /kill @e[r=0] doesn't kill you. It should kill all entities with same position as me including me.
This seems to be the same as MC-88533 which now effects all entities, not only marker armor stands.
I'd say collect them there
Could be, but It might be different. Before marker armor stand was a problem. Now r=0 is a problem.
But since it's the same issue (r=0 cannot find the executor) I just suggest to merge them.
+ it has a detailed description and is assigned already
I will give a free hand to Mod. He will know better.=]
I am probably the cause for the change in behavior of "r", since I submitted MC-95352. My apologies.
In the strict sense, the "r" argument is now working as it should. Let me explain. Whenever you execute a command, it is not really executed at the entities location, but rather the exact center of the block the entity is in. This has always been the case. That means that with the new behavior of "r", that with r=0, you will only target an entity if that entity is at the exact center of the block.
However... I do understand that many people, including me, used r=0 as a way to target all entities within a certain block. Many of my contraptions are broken too. I therefore hope that r=0 will maybe get an exception to the new and improved behavior of the "r" argument, and get it's old behavior back. Or that dy=0 replaces that functionality. However now we don't seem to have any way to interact with entities in a particular block anymore.
I can't check right now, but does r=1 now function as r=0 did?
For example, here are two 1.8 pictures where an armor stand is running r=0 to locate a player:
1. Successful because I'm in the same blockspace: http://i.imgur.com/cksEzR0.png
2. Unsuccessful because I'm not in the same blockspace: http://i.imgur.com/dxekC57.png
If r=0 is swapped out with r=1 in the latest snapshot, does it behave the same way?
It seems you are mostly right, I have only little time to test. But it behaves for x & z directions the same in 1.8 and 1.9. For y direction it behaves in 1.9 as it should.
For x and z directions:
in 1.8
Test: /execute @e[type=ArmorStand] ~ ~ ~ testfor @p[r=0]
Armorstand at pos 0 0 0
player at pos 1 0.5 0 or 0 0.5 1
(this is where I first get succesfully detected, if I tp a little bit down or up or to the sides I dont get detected any more).
in 1.9
Test: /execute @e[type=ArmorStand] ~ ~ ~ testfor @p[r=1]
Armorstand at pos 0 0 0
player at pos 1 0.5 0 or 0 0.5 1
(this is where I first get succesfully detected, if I tp a little bit down or up or to the sides I dont get detected any more).
For y direction:
in 1.8
Test: /execute @e[type=ArmorStand] ~ ~ ~ testfor @p[r=0]
Armorstand at pos 0 0 0
player at pos 0 1 0
(this is where I first get succesfully detected, if I tp a little bit up or to the sides I dont get detected any more).
in 1.9
Test: /execute @e[type=ArmorStand] ~ ~ ~ testfor @p[r=1]
Armorstand at pos 0 0 0
player at pos 1 1.5 0
(this is where I first get succesfully detected, if I tp a little bit up or to the sides I dont get detected any more).
There seems to be a weird offset for the dx and dz arguments still though.
@GamerGruppy thanks for explain. So r=0 before could target more than it should (not only all in the same position, but all within a block). Now r=0 it's targeting less than it should (should target all entities in the same position, like stacked minecart command blocks)
This been sorta fixed in 16w07b as radius now extends by 0.25 blocks from the center of the block. Entities can be 0.25 blocks from the center of a block via r=0 and be targeted, so the command example is now working. But if an entity is still technically inside the block space but is more than 0.25 blocks from the center, they cannot be targeted with r=0; r=1 would need to be used instead.
Considering this fixed.
/kill @e[r=0]is still broken, so does
/execute @a ~ ~ ~ kill @e[r=0,type=!Player], so annoying and pls fix! (I think the r=0 is the broken, nothing seems to work with r=0)
The problem is that command is executed in middle of block instead of where the entity is executing command.
Ok, I made a new report to point the problem.
MC-97316 - Executing a command from command block minecart and via /execute is running from middle of block instead of the position of entity
Cause in 1.9 pre 3 r=0 no longer counts as r=0.25, this bug is back. r=0 can't find anything, even when entity is in the same spot where distence is counted from.
MC-95352 should (or will soon) cover that.
I've finally managed to find time to update it. Thanks for the help and patience, redstonehelper.
Possibly related to the fix of MC-95352.