Harrison Martinson
Assigned
Reported
MC-217496
Beacon block states not observable/detectable
Duplicate
MC-101249
Target selectors ignore invalid arguments
Fixed
MC-99881
You can jump over walls with Elytra
Duplicate
MC-77493
Resource pack gloves don't show in first person mode
Duplicate
MC-49138
The "Back to game" button was temporarily not working
Cannot Reproduce
MC-49137
Black and purple textures
Invalid
Comments
This bug seems to be back again. Now it requires 2 boat passengers to freeze the game. Same result (server side frozen). Here's the command I used:
/summon Pig ~ ~10 ~ {Passengers:[{id:Boat,Passengers:[{id:Boat}]}]}
I got this problem on a realm. I can't go to a certain area or I'll crash. Definitely unmodded.
You realise this means that misspelled target selector data tags are ignored? If I did:
/kill @e[naem="foo"]
it would kill every entity. If I did:
/kill @e[name="foo"]
it would kill only entities named "foo". One letter difference and there goes all of that work. No entities have the tag "customName", but it runs as if they do. Why isn't that considered a bug? It's scary enough that I never use the @e selector, unless the glitch result wouldn't be that bad. This makes the @e tag pretty much useless to me.
Sorry if I'm bothering you.
@CubeTheThird
customName is an argument, but not for target selectors. It's a summon argument. It converts itself to "name" after the entity is summoned.
I would expect that any invalid argument would return as negative, but what happened is it returned as all entities. This is why I never use the kill command with @e, cause if I mistype one character, it kills all entities.
Using custom arguments is possible, so I see no reason that invalid arguments should be ignored. "customName" could be a custom argument, if it didn't exist already.
It IS a known block, it just glitched the texture.
I had this bug in 14w32d. Here's a video: http://youtu.be/8X9DBKCY5NA
Can i delete this page? Additionally, how do i delete this page? Sorry, i'm a noob here
Can i delete this page? And, how do i delete this page?
What would this be a duplicate of?
It is way too risky to use the @e selector with commands like kill and tp. I never use it. People with dyslexia might consider the @e selector unusable and therefore pointless, because one mistake ruins all entities. It would be easy to change the parser, and a lot safer.
If a command doesn't work as you want it to, and you don't realize that, would you want the command to fail and give an error message so that it doesn't mess up anything, and let you know you messed up, or would you rather mess up the world?
I'm sorry if this is wasting your time, but this is really important, at least to me.
Are you guys (including Grum) willing to reconsider if this is WAI or not? Or should I give up, even if I bring up an entirely new point?