Arguments:
•x y z: The coordinates of the block that will be powered. Block must be an opaque block or a redstone components. Tilde notation is allowed.
•duration: The amount of time that the signal will last, measured in redstone ticks.
•strength (optional): The signal strength. Must be between 1 and 15 inclusive. If not specified, defaults to 15.
•isStrongPower (optional): If set to true, the block will be strongly powered (i.e., it can power any adjacent redstone component).
Examples:
•/redstone 0 64 0 10 12 true:
Strongly powers the block at location 0 64 0 for 10 redstone ticks (1 second), with a signal strength of 12.
•/redstone ~5 ~ ~5 35:
Powers the block at the players height and 5 blocks away on each axis, with a duration of 35 ticks (3.5 seconds) and a strength of 15.
•duration: The amount of time that the signal will last, measured in redstone ticks.
Observer blocks emit redstone power for 1 game tick.
•isStrongPower (optional): If set to true, the block will be strongly powered (i.e., it can power any adjacent redstone component).
If you do /redstone 0 64 0 10 12, and a redstone wire is on 0 64 0, and that redstone wire has other wires connected to it, then the connected redstone wires won't be powered?
Seems pointless when you can use the setblock command. The extra convenience isn't worth adding in a new command. If that's how it worked Minecraft would have an overflow of commands.
A command that exerts a redstone signal on a block. Command blocks can execute this command.
Syntax: /redstone <x y z> <duration: int> [strenght: int] [isStrongPower: bool]
Arguments:
•x y z: The coordinates of the block that will be powered. Block must be an opaque block or a redstone components. Tilde notation is allowed.
•duration: The amount of time that the signal will last, measured in redstone ticks.
•strength (optional): The signal strength. Must be between 1 and 15 inclusive. If not specified, defaults to 15.
•isStrongPower (optional): If set to true, the block will be strongly powered (i.e., it can power any adjacent redstone component).
Examples:
•/redstone 0 64 0 10 12 true:
Strongly powers the block at location 0 64 0 for 10 redstone ticks (1 second), with a signal strength of 12.
•/redstone ~5 ~ ~5 35:
Powers the block at the players height and 5 blocks away on each axis, with a duration of 35 ticks (3.5 seconds) and a strength of 15.
Observer blocks emit redstone power for 1 game tick.
If you do /redstone 0 64 0 10 12, and a redstone wire is on 0 64 0, and that redstone wire has other wires connected to it, then the connected redstone wires won't be powered?
Seems pointless when you can use the setblock command. The extra convenience isn't worth adding in a new command. If that's how it worked Minecraft would have an overflow of commands.