A number of mapmakers have been using the "/summon" command to swap out blocks, which was dependent on the odd properties of falling sand. However, it was recently revealed by Jeb that this was never intended to be used for block replacement, and that the delicate nature of the command makes it prone to breaking, especially during updates. However, using commands to replace blocks will, in turn, become much easier in the future.
It was recently revealed that the next Snapshot will have a "/setblock" command, using the following format:
- /setblock x y z block data method dataTag
Jeb explains each of the above:
Quote from
- x y z are coordinates, can be relative using tilde, as usual
- block is the block id (ofcourse), which in the future will be mod-safe (for example, instead of having the value 1, you can have "minecraft:stone")
- data is the block data, 0-15 as normal
- method is special and can have three values: replace, keep, destroy. "replace" will simply replace the current block, and throw an error message if nothing happened (occurs when the new block/data is identical to the old one). "keep" will only place the new block if the target space is empty, and "destroy" will first destroy the target block (and spawn resources) before placing the new block.
- dataTag is the NBT tag were you put information for tile entities such as chests. For example, "{Items:[{id:"minecraft:potato",Count:2}]}", and so on.
So, in short, the ability to add, remove, replace, and otherwise affect blocks with commands will get its own special command set, instead of relying on an unrelated script which may or may not bug out block replacement in future updates. Pretty awesome stuff for you mapmakers out there!
________________________________
The Gamepedia wiki network - which includes the Minecraft Wiki - is one of the most awesome wiki networks ever, thanks in no small part to all the awesome contributing editors! Wouldn't it be cool if you could win a free gaming console just for being a good wiki editor? Wait, you can?! Click here for details!
You do know that there are people out there who don't like mcedit, right?
You ask a question and it isn't answered, so you leave a snarky second post instead of just re-submitting the question (usually that will get you an answer if you're polite and a little patient).
Your comments just go downhill until here where you're making threats?
Jeeze. Your poor parents.
YES.
A new gamerule that can change whether or not TNT damages blocks and another that's the same but with players. (You could use TNT to kill players, but not break blocks in adventure maps and such.)
Also, there should be something like @p.x and @r.y @a.z, and so on. You could trap players, where ever they may be, in a bedrock box. You could also use command blocks to clear, say Fire Resistance, and use a comparator output to make a house appear around them. It would be cool in an adventure map to just throw a potion of Fire Resistance at your feet and immediately have a mansion or whatever appear around or near you!
Thanks!
-TechnoWiz2Cubed
What do you have against blondes?
Basically, it's a command that lets you place one block with a certain ID at specific coordinates.
And dataTag is for stuff like placing items in chests.
Unless Falling Sand keeps its odd properties (I hope it does!).
But now we can finally spawn blocks! I'm going to go edit my map...
Anyway, I already was aware that this was coming because of Jeb's twitter, but still, this is exciting news nonetheless.
The possibilities are endless...
You don't know how much I want commands to be able to use commands with player realative coordinates! Also using scores kinda like "variables" would be super cool.
YES.
YES YES YES YES YES YES *explodes in a puff of yessiness and excitement*
<3 Mojang. You just made my
dayweekmonthyear. So excited to use this now!!!!!