QwertyuiopThePie
Assigned
Reported
Comments
In my case, it seems to always target the oldest entity that can be selected. For instance, if I spawn five armor stands, then a command that uses @r[type=armor_stand] will always run on the oldest armor stand that is currently present.
I'm not sure when this was fixed, but I've confirmed that it's fixed in 17w17b.
Confirmed for 17w17b
Confirmed for 17w17b
Confirmed for 17w17b
Confirmed for 17w17b
Ah, I always assumed they were. That's what I get for not testing. That does seem like a reasonable solution, since the hitboxes don't interact with anything. Preserves consistency and allows for anything done pre-change to also be done post-change.
The hitboxes in the first part of this bug report don't seem to have any actual impact on the entity, with the exception of passenger offset and nametag offset, as demonstrated here (the one on the left is marker): http://i.imgur.com/ehurOvY.png. Likewise with the second part. Oddly, in the fourth part, the visual hitbox is also the actual hitbox.
Copied my reply from the other bug report, since it's relevant here as well:
Seems intentional. It just relies on the visual appearance of the entity, instead of the collision hitbox. If people need a zero-height marker entity for labeling, they can always use an AreaEffectCloud. If anything, this adds an extra useful feature without taking anything away. It might break some old stuff, but so will the rest of 1.11.
...That is, of course, assuming the new hitbox doesn't interact with things. I'm not in a position to test right now but I'll give it a go tomorrow.
EDIT: Did some more research. It doesn't interact with things. I didn't realize that AECs don't actually do zero-height stacking, though.
Seems intentional. It just relies on the visual appearance of the entity, instead of the collision hitbox. If people need a zero-height stackable marker entity to use in mobs, they can always use an AreaEffectCloud. If anything, this adds an extra useful feature without taking anything away. It might break some old stuff, but so will the rest of 1.11.
...That is, of course, assuming the new hitbox doesn't interact with things. I'm not in a position to test right now but I'll give it a go tomorrow.
Items are entities, not blocks. They are most certainly intended to be summonable, as they are and have been for a long time on the PC version. This should be reopened, it's not working anywhere near how it was intended.
This bug also causes conditional command blocks to fail when they should succeed, and seems to affect all tileentities (not just chests).
Confirmed.
Confirmed for 1.9-pre4
@Adrodoc55 I'm afraid it does. Even a 10,000*10,000 selection area causes absolutely unplayably-slow tickrate, I know from personal experience.
It says fixed in "future version", not now. So, yes, probably the next prerelease, or the main release.
Confirmed fixed by 16w07b.
Confirmed in 16w07b.
Confirmed for 16w07b.
I can confirm that it's not just an issue with the dedicated server. I've had the same issues even when joining a game through LAN.