Tutorials/Command blocks and functions

The Command Block is a way to help support Adventure Mode, SMP automation, and custom maps. To find out more in detail, visit the Command Block page.

Video

Tutorials/Command blocks and functions/video

Singleplayer applications (SSP)

Command blocks can be used in single player to change the difficulty, change the state of the weather, or give you predesignated items. They are particularly useful for the /weather and /time set x commands, as they are only available in cheat mode otherwise. The /time set x command is especially useful, as it allows one to change the current time to a preset time at the press of a button. Command blocks can also be used to make text appear in the person's chat menu. To do this, dig 2 blocks down in the ground, place a command block at the bottom of the hole, type this into the command block: tell @p <message> or tell <username> <message> then place a block on top and place a pressure plate on that block. If you typed @p when someone steps on it whoever stepped on it will get a message but not anybody else. If you typed in <username> when you or any other person steps on it whoever the username is will be sent the message: @ whispers to you: <message> in that form of text.You can also type: tell <your username> @p and whenever someone walks over it is will say: ''@ whispers to you: <username of whoever stepped on it>. If a mob steps on the pressure plate it will say the username of the closest person to the command block, and if you want to change the difficulty then do /difficulty x and use 0-3 or the name of the difficulty (ex. /difficulty peaceful). Another way to use Command Blocks in singleplayer is to use /tp @p <coordinates> to warp between different bases in your world. You can use the warp by powering the command block.

Elevator

You can also make an elevator using /tp ~0 ~y ~0, where y is the vertical difference between the upper and lower elevator entrances. The elevator can also be made to tp a player to any x y z coordinate just by leaving out the ~ before the numbers. When ~ is left in the command, the normal x y z is set to 0 0 0 where the command was made, such as standing on a pressure plate or wherever the player is standing when the command block received power. If a pressure plate was at the x y z coordinates of -36 96 -12 that ran to a command block with a command of /tp @p ~3 ~4 ~5 it would tp the player to the coordinates of -33 100 -7. The same outcome can be achieved by having the command of /tp @p -34 100 -8 one block must be subtracted from the x and z axis to get to the right coordinates.

Security System for Players

Command blocks can also be used to make a security system. Just put a pressure plate which triggers a command block in front of an iron door, which will be the entrance to your house. Insert the command: /tp @p[r=<radius>,name=!<yourname>] <x> <y> <z>. For mobs, a simple fence or lava moat will do.

Moving Sidewalk

A similar concept to the elevator but made to move a player along the x or z coordinates. This can be created by:

• Build an obsidian strip
• Place a command block halfway down the strip and enter this command:

/tp @p ~1 ~0 ~0 [r=(sidewalk length / 2)] to move along the x axis, or

/tp @p ~0 ~0 ~1 [r=(sidewalk length / 2)] to move along the z axis

• Attach the block to a clock

This will make it look like and act like the person is on a moving sidewalk. It will be very noisy unless you first turn command block output off. /gamerule commandBlockOutput false

Eternal Day

File:Time reseter .png

Note: As of 13w24a, there is a gamerule, doDaylightCycle, which can be used to obtain eternal day by typing in the chat, "/gamerule doDaylightCycle false", and then "/time set 6000".

By using Cobweb and a minecart, you can skip nights using /time set 0. A minecart takes 31 seconds to fall through a cobweb. Therefore, by using 23 stacked cobweb with a Detector Rail and several Powered Rail will keep the sun in the sky.

Alternatively you can use an item de-spawning on a wooden pressure pad. The item de-spawns off of the pad every 5 mins, at this time it triggers a command block reset of the time to 0, also it triggers a dispenser (or dropper) to drop a new item on the wooden pad. 5 Mins is the day cycle and will trigger before mobs spawn. This method however is limited to 64x9 = 576 cycles = 48 IRL hours of gameplay with that chunk loaded. In the snapshot 13w01a and higher, hoppers are added into the game that can pick up items and deposit them into blocks with an inventory. A mob grinder can keep the dispenser full with gunpowder, arrows, and zombie flesh. Another technique is to simply use a command block to create the item out of thin air (e.g.: "/summon Item ~1 ~0 ~1 {Item:brown_mushroom}" without quotes). The advantage to this is that it has no 64x9 item limit like using dispensers does.

Both of these methods require the chunk to be loaded to allow the system to work.

Alternatively, you could connect the command block to a repeating redstone pulse, such as a five-clock, some type of loop, or a daylight sensor as seen on the right. To prevent this filling up the chat box, set the gamerule "commandBlockOutput" to false using the command /gamerule commandBlockOutput false. Note: This method can be used to set a variety of things by using a different command. (I.E. to have eternal sun, add another command block to the loop and use the command /weather clear)

Also, to make it toggle-able, use one of these designs, but put an AND Gate before the command block, with a lever on one side, and the mechanism on the other side.

Using the Daylight Sensor block is a more direct approach for eternal day.

The sensor deactivates the Redstone torch which will activate the Command Block which will set the time to 80000 when there's not enough light for the sensor to power the Redstone torch across the far distance. In other words, the Command Block will set the time to Noon when it's dark enough. The light level when the command will be activated varies with the distance of the Redstone wire. The time it sets to varies with the time typed in the Command Block.

To make it, first, you place the Daylight Sensor on an open area. Then you place some Redstone wire away from it. The distance of the Redstone wire depends on your need of precious time. You can only have a max of 15 blocks of Redstone. Next, you put a block on the other end of the Redstone. Put a Redstone Torch on the block's side and a Command Block on top of the torch. Right click the command block and start with "/time set" and enter a valid time value and the end. The value depends on when you want to set the time to. 14000 is night and 8000 is noon.

This design can be used in maps to keep it a certain time of day/night. This simple contraption can only be used in Creative mode or when you enable Cheats.

There is an alternative, more compact design. If you put a comparator facing away from the sunlight detector and a 15 strength redstone line (one redstone with a torch) into the second input. Then set the comparator to subtraction mode. The comparator will activate right after noon.

Wireless redstone

Wireless Redstone can be achieved in vanilla Minecraft using command blocks and the scoreboard system. The process involves using a scoreboard variable that is searched for by a command block attached to the output of a clock circuit. A comparator is then used on the wireless output command block that will trigger when the variable is found true.

Wireless Redstone can also be achieved by using objectives instead of variables. If the output command block is set to try and remove a non-existent objective, a redstone signal can be created by adding said objective via command block or chat command. The advantage to this method over the variable method is that it is not dependent on players.

To do this, place a command block at the input and type the command: /scoreboard objectives add <objective name> dummy. At the output location, place a command block, type /scoreboard objectives remove <objective name>, hook it up to a clock, and put a comparator then a repeater leading out of the command block. Then just use the repeater as an output.

• Wireless Redstone 01.png

  Off state.

• Wireless Redstone 02.png

  On state.

• Wireless Redstone 03.png

  On state command.

• Wireless Redstone 04.png

  Off state command.

• Signal catcher.png

  Wireless output setup.

• Wireless Redstone 06.png

  Wireless output command.

• Sigurd4-Wireless Redstone.png

  Another way of having wireless redstone using the "/summon" command. The command used here is /summon FallingSand -118 150 -60.5 {TileID:76,Time:1,DropItem:0}

As of 1.7 you can achieve wireless redstone even easier by using the setblock command instead of the scoreboard system. All you have to do is letting the command block set a redstone_block to the destination coordinates - together with an air block being set to the same coordinates from a command block connected to the inverted signal.

Starter Kits

By using m=, you can make a kit on a server/custom map that can only be obtained once! First, dig 3 squares down in the ground, then place a row of command blocks (one for each item in the kit). In the GUI, type /give[m=<starting gamemode, in number form>] <item id> <amount>. Do this for each item you wish to give. Make an extra command block that has the command /gamemode <a different gamemode than the starting mode>, then string redstone across all of the command blocks (this can be done easily by sneaking and placing). Fill in the hole and place a pressure plate over it. When players walk over it, they will get the desired kit of items and it will change their gamemode so they cannot receive it anymore (unless cheats are used) (Note: This method can also be done by using the method above only using (First name your kit do /scoreboard objectives add <kitName> dummy <kitName>) scoreboard commands! /give @p[score_<kitName>_min=0] <item id> <amount> for the row of command blocks giving you the items and /scoreboard players add @p <kitName> <any number above 0> to make it a one time use. Also you can make more than one kit if you repeat the steps and use a different <kitName>).

As a replacement for pressure plates

Don't you hate how there's only 4 materials that pressure plates blend in with? (stone, oak wood, iron and gold) Now you don't have to put up with that. Pressure Plates can be replaced with a command block by using the commandblock-only command "testfor" with a range and a clock circuit. The command /testfor @p[r=2] will test to see if any players are within a range of 2 (the command block itself plus 2 more blocks in every direction). Range 2 is the range you want for a command block under a floor. Keep in mind that it will produce a globe shaped trigger area (rather than a cube), so a range of 2 makes an approximately 5x5x5 area and a range of 1 makes a 3x3x3 area (more like a + pattern with an extra block above and below the center). Alternately you can specify xyz coordinates in the code (e.g. /testfor @p[x=50,y=64,z=46,r=1] but be warned that you cannot shrink the range to the 1-block point. As with the non-xyz version range means center block plus range number of blocks around it, which makes sense from a command block (where "just the center block" would mean you have to be standing IN the command block) but doesn't make sense here. At any rate a range 1 sphere (+ pattern with an extra block on top and bottom) can be buried underground with just the top sticking out, provided you know no one will be walking through the bottom 2 layers of the globe. Trying this with the non-xyz version of the code would require the command block itself to be imbedded in the surface of the floor where it can be seen. One last drawback: this doesn't have that satisfyingly sphincter-clenching trigger sound that pressure plates have. :)

Edit: spotted the solution on a YouTube video. If you intentionally cause an integer overflow by using the number 65536 in the range it wraps around and shrinks it to 1 block.
Edit 2: Fixed in snapshots for 1.8. Now you use range 0. Using range 65536 will now actually search that range instead of overflowing.

Using Command Blocks in Single Player Non-Creative Maps

By swapping gamemode it is possible to use command blocks in single player outside of creative mode. Simply swap to creative mode with the /gamemode 1 command, set the command block command to whatever you want, then swap back to /gamemode 0. The command block only needs to be set in creative, but will still function once back in normal.

It can also be used to teleport to certain areas (for ex. a far-away Stronghold, a deep mining operation, or a floating island). If it took you a very long time to get there, and if you don't mind sort-of cheating, then you can set up a teleport system. Make sure that you are on Creative mode while setting it (use the command /gamemode 1. If you don't have cheats enabled, open the LAN and set the cheats on), but you can still activate it in Survival mode. Type this command in when having the Command Block GUI open /tp @p x y z . Then, activate the command block with redstone (including buttons, levers, and pressure plates), and you will be sent to your far-away destination. You can set up multiple different teleports. This can also be used when doing a big project that spans over a very large area or if you are transferring chests to from an old house to a newer house.

Adventure Map Making

If one wishes to create a Single Player adventure map, do /publish to allow all other commands (see below) to be used.

Multiplayer applications (SMP)

This section details the applications of the Command Block in multiplayer.

• Teleportation/Transport

Through /tp, one can create teleporters for public use on a server. Can be applied to a range of scenarios. For example, one could make a system of portals in a particularly large world in which all portals link to a central hub, which contains portals to all other portal locations creating a sort of "Fast Travel Hub"

• "Stop-Motion Animation"

By using /tp and an external minecraft world editing program, such as MCedit one can copy a landscape, paste it in a faraway location, and change a few blocks. Wire a pressure plate or tripwire at each site, so that after a short delay to admire the scenery, the player is teleported using the /tp command in the command blocks. If a large amount of these copied and altered locations are wired so that the player teleports to them in sequence with a slight delay in between each, then this creates the illusion that the scenery around the player is moving, similarly to the techniques used in stop-motion animation.

[Note that if you are using 1.8 or its snapshots, you could use /clone with lots of different copies of it, slightly altered bit by bit, and then just clone the areas into one spot in sequence. That way the player doesn't have to be teleported, but the landscape around them can be animated as the clone commands copy the various animation "frames" near the player sequentially.]

• Lottery

Through /give @r, one can create a lottery. Keep in mind that now, /give will directly put items into one's inventory, instead of throwing them on the ground in front of the character.

• LotteryII

As mentioned above one can create a lottery but that lottery is usable by the public. A simple edit can change that... First create a new objective. (For example: /scoreboard objectives add Lottery dummy Lottery ) Then use this command on a command block /scoreboard players add <playerName> lottery 1 to enter players into the lottery then do /give @r[score_Lottery_min=1] to start the lottery and only the players you choose can be in the lottery!

• Jails

By rigging a clock to a command block and using /tp a whole bunch, you can force a player to stay at a certain place. If you do this it would be advisable to either turn off commands in your chat settings or do /gamerule commandBlockOutput false. Using the "Range" and "Minimum Range" parameters, you can have it teleport players back only when they're a certain distance away.

Alternatively, giving the player certain status effects at high levels using the /effect command can mimic the effect of a jail. Use /effect @p 2 <insert duration of effect> 128 to keep the player from moving, and /effect 4 <insert duration of effect> 127 to keep the player from breaking things. If you really want to kick it up a notch, poison the player (use one of the previous two commands, but replace the first number with 19).

• Admin Only

By using the parameter [m=1], only players in Creative will be affected by the command block.

• Fun anti-creative mode trap

If you place a command block connected to a redstone pulse you can set tp @p[m=1] ~0 ~1 ~0 for hilarious results. This could be a way to get creative mode people to change to survival and is also really fun to watch.

• Announcements

By using /me in a command block one can create announcements that could play even when the admin/owner wasn't there.

• Security Scan

By using /clear, you can scan people for items. If you want to remove certain items, use /clear @a(or <playername>) <itemid>. For example, on a server that doesn't want griefing you could have a clock connected to a command block set to /clear @a 259.

• Race Referee

Using /say @p, the command block can report the nearest player. If the command block is placed after a finish line, it will say the finishers in order. As of patch 1.7, you can also do /tellraw @p "THIS IS A MESSAGE" and when activated the message "THIS IS A MESSAGE" will come up on the chat system.

• Creative Area/World Guard

Creating a "Creative Only" zone is possible through command blocks, but it is complex and more of a case-by-case basis. The basic idea would be to create a "fence" of command block affected zones so that, once a player flies in creative through it, they would be changed to survival or adventure mode. A "World Guard" zone would be a lot simpler, just have a command block do /gamemode 2 @a[x y z r m] and when people leave, just have a button to change them to survival.

• Improving PvP without Plug-Ins

You can use /gamerule keepInventory true so players cannot steal each other's items. Also, using /spawnpoint [x y z] and /tp [x y z] to help move players around while in PvP competitions.

• Starter Kits

You can easily give people a starter kit with a button without plug-ins: "/give @p[r=2] 274". To prevent people pressing the button a second time and again getting their kit you can make two command blocks activated in order: 1. "/give @p[r=2 m=2] 274" 2."/gamemode 0 @p[r=2]"

• Special Colourful Words

Although you are not directly able to obtain colored/bold/italic text when typing into the Command Block GUI, through McEdit filters you can edit the text to have those properties just like how plug-ins change chat text properties on servers. SethBling's McEdit Filter: ColourCommandBlockText

• Alarm System

When a player walks over a pressure plate, it can trigger a command block with /say @p.

• Remove Players

Using coordinate and maximum parameters you can teleport everyone within a specific area to another specific area.

• Reward Room

If a certain player has been very nice,regular,or helpful to the server but not quite meeting the requirements to be promoted to an admin, you could have a room full of buttons connected to Command Blocks with helpful effects, like giving the helpful player a stack of diamonds or a bedrock block, then have it connected to another command block, sending them to the spawn point. (It is VERY important this room is reinforced with bedrock, hidden, and you can only get in by teleporting to its co-ordinates to avoid abuse).

• Weather Machine

(Command: /toggledownfall and /weather thunder (to start or stop a thunderstorm)) Assuming only admins can get to it, a weather machine can be quite useful, you can turn rain on and off at will. One of the more helpful uses of this technique would be to use a combination of villagers and some form of redstone machinery to create and automatic rain disabler, this would allow you to shut off the rain almost immediately without needing to use the command, or to have an admin present. It can also be used to create, and/or end, a scenario where it is more advantageous to have rain as opposed to sunlight, and vice versa; such as during a forest fire, or when a thunderstorm is spawning monsters.

• Obstacle Course prizes

with tp @p and give @p, you could make an obstacle course or maze that when finished will give a player a prize, and will teleport them back to spawn or some other area.

• Time Machine

By making two similar places on one map, you can have a button activate a command block to tp you from one to another, while also changing the time of day. This can be used to look like time travel.

• Proximity Mine

By using a condition such as /testfor @p[r=5,name=!<placing player>] hooked to a short clock and one or more TNT blocks via a comparator, the command block can act as an undetectable proximity mine against all players except the placing player.

• Secure Doors

By using a condition such as /testfor @p[r=5,name=<owner>], the command block can detect a door's owner within a certain radius and open a door for them, and only for them.

• Infinite items in survival

As of the snapshot 13w36a, you can put NBT tags in the /give command. You can obtain an infinite stack of blocks by typing
/give <ID> <Any number> {amount=-1} in a command block.

Application in custom maps

This section details the applications of the Command Block in custom maps.

One map that takes advantage of a lot of the features of the Command Block is SethBling's TF2 Map "Dustbowl" in Minecraft.

http://www.youtube.com/watch?v=_f2brU8hBWc&feature=plcp

Another example is the Hypixel's Gladiator Arena in which the fighting system is almost only based on the Command Block.

http://www.youtube.com/watch?v=jryJkWcqmzM

• Silent Command Block

Sometimes it's important in a map to keep the command blocks silent, may it be to keep the magic of the suddenly appearing items in the inventory, or because the channel telling that the player was teleported, it can break the mood of a map. To keep them silent (except when you ask them to speak), just use the /gamerule commandBlockOutput false.

• Safe Haven/Arena Fight Zone

Using pressure plates or tripwire, make areas (like a castle for instance) a different difficulty (for this instance I will use peaceful). the doors could have tripwire hooked to a command block that changes ones difficulty to peaceful, creating a sort of "Safe Haven". one could also do it the other way around, creating a more dangerous zone, such as arenas having the difficulty of hard, rather than normal or easy.

• Detecting Cheaters

Using parameter [m=1], you can affect those who are in Creative, or survival with parameter [m=0].

• It's bigger on the inside

This is a simple one, just have a system of tp-ing command blocks at the entrance/exit of a place, and you can build the interior somewhere else, allowing you to cheat space restriction. (example of use: you want interior walls to be wool, but exterior walls to be wood (normally 2m thick walls). You can make the outside of the house be 8x10 m, and the inside of the house be 8x10 m.) Or, have the inside of the house 20x20m instead!

• Save game

By using the /spawnpoint command, one can easily make a button-activated checkpoint.

• Lava parkours

As said before, there is a command that makes the player able to keep their inventory upon death: /gamerule keepInventory true. Simply connect this to a pressure pad before a parkour level over lava and you don't have to use any kind of chest minecart (especially useful when the player has it's full inventory, which is bigger than a single chest).

• Still want a bed?

It is true that the /spawnpoint command is really useful because you don't have to wait for the night to create a checkpoint, but what if you want to have a BUD switch connected to the bed or something of the sort? Then, you just need to have a pressure plate (it's more discreet) connected to a block with the /time set 18000 command, and it will set the time to night so the player can sleep.

• Time and weather following the scenario

Let's say your map starts on a cold stormy night and when the player starts, for some random reason, there's a bright sun outside! Or what if you want to start on a bright day and the rain decides to join along? Fear not, for there is a weather command. Just use the /weather input command with, as input, clear, rain or thunder. Along with this, you can also use /time set input with as input a number: 23250 is sunrise, 6000 is midday, 12750 is sunset and 18000 is midnight.

• Detecting Players who switched to Peaceful

Create a hostile mob (so it disappears when switching to Peaceful) that never despawns if the player is far away. To do so, use a name tag on the mob (or third party software if you are playing in a version previous to 1.5.2) and place it on a pressure plate. Make sure it will keep it pressed infinitely, so make sure it can't jump or walk away. Make a redstone circuit that causes a command block to activate when input from pressure plate ceases to exist. Place a message inside the block that informs the player on chat that the map has been broken and must be redownloaded. This way, switching to Peaceful will cause the mob to vanish and activate the message. You can even make a teleportation command block so that a cheater is banished from the map to a small room without a way out as soon as he switches to Peaceful.

• Talking Adventure Map(featuring an easy Quest System!)

The /say command is really useful because it makes a text appear into the chat. It's maybe one of the greatest use of the Command Block as you don't need silly signs or long books to show the game rules. Just put a bunch of command blocks in lines with repeaters set to two or three ticks (so the player isn't spammed) and you can easily remove a chest of books or a lot of signs.

Another use of the command is talking NPCs and other mobs. Imagine you enter a butchery and you want the butcher to say something. Before, you needed to use signs or books, using some room in a butchery and putting objects that sometimes seemed random, but now... You just have to use the /say command and the butcher will talk. Maybe a pig behind the counter will even beg for mercy! Let's take another example: you are in a factory and an alarm suddenly rings and says that it's going to explode. Having it in the chat, especially if the text is long, keeps the stressfull mood; the same thing works for bomb timers. The player will get more into the map's mood if the chat displays '10...' '9...' '8...' also.

Last but not least, it makes it easier to create a Quest System. Let's say the player gets in a butchery. He activates through a pressure plate connected to a RS NOR Latch (so it can't be activated twice) and a command block with the /say command in which the butcher asks for the player's help: he needs to kill a pig (shame on him). The player gets to the pig that is standing on a stone pressure plate, that turns off when the pig is dead. So, when the player gets back to the butchery, he activates another circuit containing yet another RS NOR Latch and two command blocks with two commands. First, the /say command in which the butcher thanks the player, and other one, the /give command, so the player gets the reward. Along with that, don't forget to use the @p command so the butcher says the player's name. For example, if the command block is set to do this: /say Thanks, @p. You helped me a lot killing that pig., the channel will say: "[@]: Thanks, <name of the player>. You helped me a lot killing that pig." This makes the map way cooler and looks like it's made for the player as it says his/her name! You could also change [@] to [Butcher] by renaming the /say command block using an anvil.

• Making a Store

By using /give @p[lm=(level)] (item) (amount) and /xp -(level)l @p[lm=(level)] you can make a shop system that trades a certain amount of exp for items. For instance, if you made a command block with /give @p[lm=5] 2 64 and another with /xp -5l @p[lm=5] connected to the same redstone current, it will take 5 levels from the player, and in return, give them 64 grass blocks.

• • Subtracting xp CAN work as a currency, by using the command /xp -3l @p[lm=3] where l (L for level) is subtracted. The minimum xp for the command to work can be listed inside the brackets, where lm is short for minimum level necessary.!!!!

• Store part 2: Custom Villagers

Custom Villagers selling whatever you want can be created with command blocks.
e.g.: /summon Villager ~-2 ~0 ~0 {Profession:3,CustomName:BLACKSMITH,CustomNameVisible:0,Offers:{Recipes:[ {maxUses:13,buy:{id:388,Count:5},sell:{id:283,Count:1,tag:{ench:[{id:16,lvl:9},{id:20,lvl:6}],display:{Name:Molten Gold Sword}}}},{maxUses:13,buy:{id:388,Count:1},sell:{id:280,Count:1,tag:{ench:[{id:16,lvl:5}],display:{Name:Whuppin Stick}}}},{maxUses:13,buy:{id:388,Count:2},sell:{id:369,Count:1,tag:{ench:[{id:16,lvl:5},{id:20,lvl:10}],display:{Name:Radioactive Whuppin Stick}}}},]}} .
The part labeled "Buy" is what the villager is accepting as payment, the part that says "sell" is what he's giving in return. You can change the maxUses to 1000 if you never want the offer to run out, or to 1 if you want to make it a one-of-a-kind item. Note that the first item there (the gold sword) has an out of range enchantment (sharpness 9). Yes this works, but always research what exactly the enchantment does before making an out of range one as some stuff does nothing or even does negative effects (respiration's "see underwater" side effect makes everything a blinding white at high levels, as if you dove into slush-filled arctic waters). As for that gold sword, keep in mind that gold swords wear out insanely fast (there's a reason people call them b____r swords after all). A level 10 Unbreaking enchantment should bring a gold sword up to a decent durability level. Also notice that the other 2 "weapons" are actually a Stick and a Blaze Rod with weapon enchantments on them. Using any non-weapon as a weapon does the same damage as an empty hand (1 damage, aka half a heart) but the enchantments on these ones make them the equal of an unenchanted sword. Why bother? What's the advantage? Because unlike weapons, sticks and blaze rods HAVE NO DURABILITY RATING AND WILL NEVER WEAR OUT! The same trick can be used with mobheads and respiration 3 to make an infinite durability scuba mask.

New 1.7 uses

File:Legit Rails.png

Minecarts over floating rails created with the setblock command.

In 1.7, the command block gained an expanded potential. Namely, the /summon and /setblock commands have been added, and can be used to automatically build structures, fill chests, and spawn previously unavailable entities. The syntaxes for the commands are:

/setblock <x> <y> <z> <tilename> [datavalue] [oldblockHandling] [datatag] for setblock

/summon <EntityName> [x] [y] [z] [DataTag] for summon

Along with that, the setblock command also makes it possible to make traps with disappearing floors and sudden walls.

SETBLOCK EXAMPLES:

* MobSpawners pt 1: The Basics This code will create a zombie mobspawner 2 blocks from you in the x direction. Note that the name given for mobspawners in this code ("minecraft:mob_spawner") is the long version and you can leave out the "minecraft:" part.

/setblock ~2 ~0 ~0 minecraft:mob_spawner 0 replace {EntityId: Zombie}

This next code is also pretty basic but it includes the 6 basic parameters that can be set.

/setblock ~0 ~-1 ~-3 mob_spawner 0 replace {EntityId:Skeleton,SpawnRange:4,RequiredPlayerRange:16,SpawnCount:4,MaxNearbyEntities:6,MinSpawnDelay:200,MaxSpawnDelay:800}

A few things to note:
A) All times are in game ticks (20ths of a second). 200-800 is 10-40 seconds.
B) Keep in mind that they are in groups of 2 and won't work if their partner is missing. SpawnRange requires RequiredPlayerRange (and vice-versa), MinSpawnDelay requires MaxSpawnDelay, and I assume SpawnCount needs MaxNearbyEntities (although I haven't actually heard confirmation on that last one).
C) There is also a parameter called "Delay" which contains the amount of time before next spawn (20 ticks for the first time, whatever random number it picks between MaxSpawnDelay and MinSpawnDelay every other time).
D) the coordinates given are ~0 ~-1 ~-3 (so 3 blocks in the negative Z direction from the commandblock's current position and 1 block down). This presumably will imbed it in the surface of the floor. Keep in mind that a spawners "SpawnRange" setting only applies horizontally not vertically. Vertically it will only spawn at the same height or 1 lower or higher, so imbedding it in the surface of the floor cuts the available spawn area by 2/3rds (but can help hide it). Naturally occuring spawners have their height cut by 1/3rd due to appearing 1 block above the floor instead of 2.
E) All the values used here are the defaults.

* MobSpawners pt 2: Custom monsters Now we get into the SpawnData. That's the stuff that tells the spawner you want a non-standard version of a monster, like a Zombie with a Diamond Sword and a Chainmail Helmet.

/setblock ~ ~1 ~ mob_spawner 0 replace {EntityId:Zombie,SpawnData:{Equipment:[{id:276,Count:1},{},{},{},{id:302,Count:1}]}}

Using ~ without any number after it in the coordinates counts as zero. Since none of those 6 parameters from last example are used they will all be defaults.
Note that the 5 equipment slots are: Hand, Boots, Legs, Chest, Helmet. You must even specify empty slots (the { }, parts) unless they're after the last non-empty slot. So if you want him to have a helmet you have to specify all 5 slots, but if it's just a weapon you can leave off the other 4. Or if you want him to have leg armor you have to specify weapon and boot slots but not chest and helmet slots.
By the way, creatures that burn in sunlight are safe if they have a helmet on, although it damages the helmet instead.
About the Count tag: most codes can get away with leaving it out, however it is important. An item without a count tag is a stack of zero, better known in the community as a "Ghost Item". A player trying to use a ghost item will have it disappear out of his hands with it's first use (which is a failure). While monsters can use ghost items without problem (hence why codes get away with leaving it out sometimes) if they drop the items the player who picks it up won't be able to use it, SO INCLUDE COUNT!

Next up we have a Skeleton with an enchanted bow (Flame), a custom mobhead (Spider, internet connection required or it's just steve) with Protection 2, and riding a Skeletal Horse.

/setblock ~2 ~1 ~2 mob_spawner 0 replace {EntityId:Skeleton,SpawnData:{Equipment:[{id:261,Count:1,tag:{ench:[{id:50,lvl:1}]}},{},{},{},{id:397,Count:1,Damage:3,tag:{ench:[{id:0,lvl:2}],SkullOwner:MHF_Spider}}],Riding:{id:"EntityHorse",Type:4,Tame:1,SaddleItem:{id:329,Count:1,Damage:0}}}}

Well actually sitting on a Skeletal Horse, since the lower creature controls the movement and the horse isn't hostile. Don't try zombies on horseback, they just sit there ineffectually while the horse eats grass and snorts. Luckily this is a skeleton and can shoot you from wherever the horse decides to wander.
As for the horse itself, it's type 4 (skeletal horse), Tame is set to 1 (yes), and it's got a saddle (and the fact that they make us specify which saddle hints that they may eventually have more than one type). Technically you can have multiple levels of riders, although this gets silly quickly.

MobSpawners pt 3: SpawnPotentials Using the SpawnPotentials tag lets us create a mobspawner with multiple mobs in it. It will randomly pick one each time it resets the timer (a second after spawning the previous mobs). Since these codes contain multiple mobs they tend to be quite long codes. Thanks to some youtuber whose name escapes me (Dragnoz) the fact that you can "break up" your code is known (command blocks ignore line breaks, so you can start a new line to clarify where one section ends and another begins and it won't ruin your code). Here's a more easy on the eye version of a SpawnPotentials code

/setblock ~0 ~1 ~1 mob_spawner 0 replace {EntityId:Zombie,SpawnRange:6,RequiredPlayerRange:12,SpawnCount:1,MaxNearbyEntities:6,MinSpawnDelay:100,MaxSpawnDelay:600,SpawnData:{Equipment:[{id:268,Count:1},{id:301,Count:1},{id:300,Count:1,tag:{display:{color:5013401}}},{id:299,Count:1,tag:{display:{color:6717235}}},{id:397,Count:1,Damage:3,tag:{SkullOwner:Reimac}}]},SpawnPotentials:[

{Type:Zombie,Weight:4,Properties:{Equipment:[{id:268,Count:1,Damage:58},{id:301,Count:1},{id:300,Count:1,tag:{display:{color:5013401}}},{id:299,Count:1,tag:{display:{color:6717235}}},{id:397,Count:1,Damage:3,tag:{SkullOwner:Reimac}}]}},

{Type:Skeleton,Weight:2,Properties:{Equipment:[{id:267},{id:301,Count:1,tag:{display:{color:1644825}}},{id:300,Count:1,tag:{display:{color:1644825}}},{id:299,Count:1,tag:{display:{color:1644825}}},{id:397,Count:1,Damage:3,tag:{SkullOwner:2insanepeople}}]}},

{Type:Zombie,Weight:4,Properties:{Equipment:[{id:272,Count:1},{id:305,Count:1},{id:304,Count:1},{id:303,Count:1},{id:397,Count:1,Damage:3,tag:{ench:[{id:0,lvl:2}],SkullOwner:Flixnore}}]}},

{Type:Zombie,Weight:4,Properties:{Fire:2400,Equipment:[{id:283,Count:1,tag:{ench:[{id:20,lvl:1}]}},{id:317,Count:1},{id:316,Count:1},{id:315,Count:1},{id:86,Count:1,tag:{ench:[{id:0,lvl:2},{id:1,lvl:10}]}}]}},

{Type:Zombie,Weight:4,Properties:{Equipment:[{id:267,Count:1,tag:{ench:[{id:16,lvl:2}]}},{id:309,Count:1},{id:308,Count:1},{id:307,Count:1},{id:397,Count:1,Damage:3,tag:{ench:[{id:0,lvl:2}],SkullOwner:2zqa}}]}},

{Type:Zombie,Weight:1,Properties:{Equipment:[{id:278,Count:1,tag:{ench:[{id:16,lvl:4},{id:17,lvl:4},{id:18,lvl:4},{id:21,lvl:3},{id:34,lvl:3}]}},{id:313,Count:1,tag:{ench:[{id:1,lvl:4},{id:2,lvl:4}]}},{id:312,Count:1,tag:{ench:[{id:3,lvl:4}]}},{id:311,Count:1,tag:{ench:[{id:0,lvl:4}]}},{id:397,Count:1,Damage:3,tag:{SkullOwner:MHF_Herobrine,ench:[{id:0,lvl:4},{id:1,lvl:4},{id:3,lvl:4},{id:5,lvl:3},{id:6,lvl:1}]}}],CustomNameVisible:1,CustomName:Herobrine,PersistenceRequired:1}},

]}

Wow that's a mouthful! But then it is 6 seperate mobs. In order we have:
0) Before the "SpawnPotentials" tag: The starter, which will never pop up again after the first time. If we want to see him again we have to include him a second time under SpawnPotentials. He is just some random dude in bluejeans (blue dyed leather leg armor) and a cactus green shirt (green dyed leather tunic) with a wooden sword. He's a zombie under that random-dood-mobhead of his of course. They all are.
1) Same random dood, only this time his wooden sword is 2 hits away from breaking.
2) Hey who let a ninja into the game?!? This one is a skeleton under his mask, but he's been given an iron sword. All his leather armor is dyed ninja-black. Skeletons with swords close the gap quicker than zombies so watch out.
3) Stone Sword and Chain Armor guy. Protection II on his mobhead.
4) One of my favorates. Gold Sword, Golden Armor, Pumpkin Helmet, and ON FIRE!!! Originally I wanted to give him a flaming pumpkin helmet but I realized the Fire tag only applies to entities not armor. The pumpkin is enchanted with Protection II and Fire Resistance X (10!) in a desperate attempt to keep him on his feet and threatening the player for more than 5 seconds. It works but if the player plays keepaway then Mr Pumpkinhead does tend to burn to death. Oh his sword has fire aspect too.
5) Iron Sword and Armor guy. Sharpness II on his Sword, Protection II on his mobhead.
6) Diamond Weapons and Armor guy. Wait who is that. Is...is that...Oh Em Gee it is! Run!...No of course it's not really him. Because he doesn't exist. FakeHB here has highly enchanted Diamond Armor (Boots with Fire Protection IV and Feather Falling IV, Leggings with Blast Protection IV, Chestplate with Protection IV, Mobhead with Protection IV, Fire Protection IV, Blast Protection IV, Resperation III) and a Diamond Pickaxe enchanted with Sharpness IV, Smite IV, Spiderbane IV (oh fine Bane of Arthropods IV, you happy?), Looting III and Unbreakable III. He's also got the previously unseen CustomNameVisible (set to 1 for yes), a CustomName, and PersistenceRequired (set to 1 for yes). That last one will prevent him from ever despawning, although he can be killed normally. If you can get through that Diamond Armor. And level 4 resistances. Luckily he's rarer (see below).

Other than the ninja it's a straight tour of the 5 tiers of swords and armor. Note the Weight tag, used right after the mob name in each SpawnPotential. That determines how rarely it's picked. Specific numbers don't mean anything, just the ratios between the numbers. For example if you want all the potentials to have an equal chance just set all the weights to 1. Changing them all to 8 wouldn't do anything different (they're still all the same size as each other), however changing all but one to 8 would make that one 1/8th as likely as the rest. In this code 4 is the default. The ninja only has a weight of 2 (making him half as likely to be picked) and FakeHB has a weight of 1 (making him 1/4th as likely to be picked, and thank god!)

Further Resources

Feare_104's Command Block Tutorials

See also

• Command Block
• Multiplayer
• Adventure Mode
• Survival Mode