Can confirm for 1.12...
Appears to be fixed in 1.12
Why is this a security issue? Couldn't you just have some sort of verification thing? I'm surprised on what the server depends on (stuff like giving skin urls) and what the client depends on (sending inventory to server repeatedly).
Wow. This is basically the equiv. of the 15w34c memory allocation crash (in my opinion as a server manager). This REALLY needs to be fixed IMMEDIATELY. Can confirm for macOS .jar.
Question: Can you revamp the command so that it is /fill <coordinates> <name> [dataValue|state] replace [<blockToReplace> [dataValue|-1|state|*]] [fillBlockDataTag]
?
(It is easy to detect a <code>{</code> vs a different character for starting an item technical name in my opinion)
So, if you wanted to replace wood planks with chests (with a bow inside) between 0, 0, 0 and 1, 1, 1, you would do {{/fill 0 0 0 1 1 1 chest 0 replace planks * {Items:[0:{Slot:0,Item:"minecraft:bow",Count:1b,Damage:0s}]} }}.
However, if you wanted to fill chests regardless of planks, you would remove the planks *
.
Yes
Okay... how do I delete this
Attachment: http://i.imgur.com/lo5FouI.png
Command:
/give @p diamond_sword 1 0 {display:{Lore:["This","Lore","is","VERY","long","to","help","fix","bugs","and","with","this","lore","We","can","fix","bugs","because","of","this","very","long","lore","that","is",":?:","lines","long","so","we","can","fix","MC","-","92527","with","this","very","very","very","very","very","long","lore","so","let","'s","go","fix","it","!"]}}
Appears to be fixed as of 1.13