Command Blocks in Minecraft Bedrock: Types, Modes, Mistakes

Contents
  1. Mistake 1: looking for a crafting recipe
  2. Mistake 2: setting Repeat where you need Impulse
  3. Mistake 3: a chain with no stop condition
  4. Mistake 4: fighting redstone where it isn’t needed
  5. Mistake 5: counting time in seconds

A command block in Minecraft: Bedrock Edition has 3 types and two mode switches, and most broken minigames come down to picking the wrong type - not writing the wrong command. The command is often fine. It’s just running at the wrong time, the wrong number of times, or in the wrong order from what the map maker intended.

Below are five mistakes almost everyone trips over the first time they drop a command block into their own arena or parkour course. Each one comes as a pair: how people usually do it, and how it should be done.

Mistake 1: looking for a crafting recipe

The typical story: a player opens the creative inventory, searches for “command”, finds nothing, goes looking for a recipe, and loses an evening to articles claiming it’s “supposedly” crafted from obsidian and redstone.

That recipe doesn’t exist. You can’t get a command block the normal way - according to Microsoft’s documentation, the only way to get one is the command:

/give @p command_block

You can run it in a world with cheats turned on. That’s the main requirement: with cheats off, the command won’t work, and there’s no workaround for that. If you’re not sure how cheats and game rules even work in Bedrock, start with our guides on cheats and commands and game rules.

How to do it right: turn on cheats in the world settings first, then give yourself the block with the command, and only then start building your logic. Not the other way round.

Mistake 2: setting Repeat where you need Impulse

The second mistake costs more. A player wants pressing a button to hand out a reward, places a block and, without understanding the types, switches it to Repeat - because the word sounds “more reliable”. The reward starts pouring out non-stop.

The Block Type setting has exactly 3 options, and they work in fundamentally different ways:

Type When it runs the command What it’s for
Impulse on a redstone signal one-off actions: starting a round, giving an item, changing the weather
Chain when the block pointing into it activates steps in a chain that must run in strict order
Repeat every game tick ongoing checks that need to run all the time

How to do it right: anything that should happen once per player action is Impulse. Anything that should happen right after the previous step is Chain. Leave Repeat only for things that genuinely need to be checked constantly, and always ask yourself “what happens if this fires again a moment later?”

This is also where the arrows come in. A Chain block doesn’t react to redstone - it reacts to the block pointing into it firing. That’s why the arrows on the sides of a command block aren’t decoration: they set the direction of the chain. When you place a block, look at which way it’s “facing”, and put the next block in the chain exactly there. A chain where the second block sits off to the side of the first one’s direction looks complete but doesn’t work: the first one fires, the second doesn’t.

Mistake 3: a chain with no stop condition

The most telling beginner mistake is spelled out directly in Microsoft’s documentation: a repeating chain with no final step that tags the player will hand out 20 emeralds a second. Not “a lot”, not “too many” - exactly 20 a second, which is simple arithmetic from Repeat firing every game tick and there being 20 ticks in a second.

Anyone who’s built their first map knows the scene: a player walks up to a chest, the reward fires, and then the inventory - and soon the floor around it - fills up with items until the world starts lagging.

The Condition setting is what saves you here. It has 2 options:

  • Conditional - the block only runs after the previous block in the chain succeeds.
  • Unconditional - the block runs regardless of the previous one.

How to do it right: make the last step in the chain tag the player, and have the first step in the chain check for that tag. A player without the tag passes the check, so the chain continues and tags them at the end. A player who already has the tag fails that check, and the Conditional steps after it simply don’t run. The reward is given once per player, not 20 times a second.

A simple way to check yourself before launching a map: mentally run the chain twice in a row. If the second run gives the same result as the first, there’s no stop condition.

Mistake 4: fighting redstone where it isn’t needed

The fourth mistake runs the other way. A player wires redstone to every block in the chain, reasoning that “the block needs to get a signal”, then wonders why half of it fires on its own and the other half doesn’t fire at all.

That’s governed by a separate setting - Redstone - which also has 2 options:

Setting Options What it controls
Condition Conditional / Unconditional whether the block depends on the previous step succeeding
Redstone Needs Redstone / Always Active whether the block needs a redstone signal to work

The key detail: Chain blocks have Always Active turned on by default. A Chain block isn’t meant to wait for redstone - its job is to wait for the block pointing into it.

How to do it right: run redstone to the starting block of the chain - the Impulse one. Leave the rest of the chain on Always Active and connect it with arrows, not wire. The map becomes more compact, and the execution order stays predictable, because it’s set by the blocks’ geometry rather than whichever path the signal happened to travel fastest.

Mistake 5: counting time in seconds

The fifth mistake is quiet, and it only shows up after the map’s already published: the creator sets a delay or duration “by eye”, in seconds, while the game counts in ticks.

A command block’s delay is set in ticks, and so is duration inside the commands themselves. The rate is always the same: Minecraft runs at 20 ticks per second. The example from the command reference makes it clear - /weather thunder 600 sets a thunderstorm for 30 seconds.

Here’s an example of our own, simpler than any tutorial. You’re building an arena where the round runs under a thunderstorm:

  1. A button on the wall sends a signal to the first block - Impulse, Needs Redstone. Its command is /weather thunder 600.
  2. The second block is Chain, arrow pointing from the first, Always Active. It announces the start of the round.
  3. The third block is Chain, Conditional, pointing from the second. It only fires if the second one succeeded.

The round will last exactly as long as set in ticks, not however long it felt like by eye. And if you want to double the duration later, you multiply the ticks, not the seconds.

One more practical detail: don’t automatically carry the same syntax and settings over from videos filmed in a different edition of the game. Bedrock and Java differ both in commands and in how some blocks behave - we’ve got a separate breakdown of the differences between editions. Check the setting in your own world before you build your whole map around it.

Command Blocks in Minecraft Bedrock: Types, Modes, Mistakes

Frequently asked questions

How do you get a command block in Minecraft: Bedrock Edition?

Not the normal way - there's no crafting recipe. According to Microsoft's documentation, the block comes from the command /give @p command_block in a world with cheats turned on.

What's the difference between Impulse and Repeat?

Impulse fires on a redstone signal, so once per press. Repeat runs its command every game tick, so continuously as long as it's active.

What does Conditional mode do?

A block set to Conditional only runs its command after the previous block in the chain succeeds. Unconditional runs regardless of what happened before it.

Why does a Chain block work even with no redstone nearby?

Because Chain blocks have Always Active turned on by default. A Chain block isn't waiting for redstone - it's waiting for the block pointing into it to activate.

How many game ticks are in a second?

20. That's why durations in commands are counted in ticks: /weather thunder 600 sets a thunderstorm for 30 seconds.

Why does my chain keep giving out items endlessly?

That's the classic mistake of a repeating chain with no end step. The documentation warns about this directly: without a step that tags the player, a chain like that will hand out 20 emeralds a second.

Sources