How command blocks work!
Bolt was almost finished with his puzzle and maze map when he heard a menacing laugh from Omega. It was a mistake doing his map on a server. Omega had set up command blocks causing the entire map to blow up, the source being a volcano Bolt had spend one week building, followed by a spooky sound and a game crash.
When you put a command into a command block and power it by redstone, that command activates. For instance, if someone did "/give @p stone" the game would give the closest player, @p, a block of stone when the command block is powered. There is a lot of things that you can do with these special blocks. For a more complicated example, if someone did /summon Fireball ~ ~-2 ~ {ExplosionPower:10,direction:[0.0,2.0,0.0]}. It would spawn a powerful Fireball heading straight down until it hits something then it would explode. If I did /give @p diamond_sword 64 0 {ench:[{Id:16,lvl:10000},{Id:34,lvl:10000}]}. It would give the nearest player a 64 brand new diamond sword with sharpness level 10,000 and unbreaking level 10,000. Bolt even once made a command that give a player a block of ice that is named "Let It Go" and has a lore of "Can't Hold It Back Anymore." This command is /give @p ice 1 0 {display:{Name:"Let It Go",Lore:["Can't Hold It Back Anymore"]}}.
Some people may be wondering, "Why should I use command blocks instead of just typing the command?" Well, the answer is, if you put a command into a command block, it will stay in there until you change it or you delete the block. Unlike the command where you have to keep typing it. Also you can use multiple command blocks at once, and you can only do one command at once. There is one thing about command blocks that you can only do with player written commands though. You cannot do /op, /deop, /ban, and /kick on multi-player command blocks. You also need to be in creative mode and made and operator. This restrains people from messing up a server with command blocks.
Bolt was almost finished with his puzzle and maze map when he heard a menacing laugh from Omega. It was a mistake doing his map on a server. Omega had set up command blocks causing the entire map to blow up, the source being a volcano Bolt had spend one week building, followed by a spooky sound and a game crash.
When you put a command into a command block and power it by redstone, that command activates. For instance, if someone did "/give @p stone" the game would give the closest player, @p, a block of stone when the command block is powered. There is a lot of things that you can do with these special blocks. For a more complicated example, if someone did /summon Fireball ~ ~-2 ~ {ExplosionPower:10,direction:[0.0,2.0,0.0]}. It would spawn a powerful Fireball heading straight down until it hits something then it would explode. If I did /give @p diamond_sword 64 0 {ench:[{Id:16,lvl:10000},{Id:34,lvl:10000}]}. It would give the nearest player a 64 brand new diamond sword with sharpness level 10,000 and unbreaking level 10,000. Bolt even once made a command that give a player a block of ice that is named "Let It Go" and has a lore of "Can't Hold It Back Anymore." This command is /give @p ice 1 0 {display:{Name:"Let It Go",Lore:["Can't Hold It Back Anymore"]}}.
Some people may be wondering, "Why should I use command blocks instead of just typing the command?" Well, the answer is, if you put a command into a command block, it will stay in there until you change it or you delete the block. Unlike the command where you have to keep typing it. Also you can use multiple command blocks at once, and you can only do one command at once. There is one thing about command blocks that you can only do with player written commands though. You cannot do /op, /deop, /ban, and /kick on multi-player command blocks. You also need to be in creative mode and made and operator. This restrains people from messing up a server with command blocks.