 |
VOOZH | about |
|
VOOZH | about |
Redstone mechanics describe the general concepts of redstone power, and how redstone-related blocks interact with one another. This article describes basic ideas such as redstone power, powering blocks, and activating redstone mechanisms.
Redstone is Minecraft's loose analog to electricity. There are a variety of blocks that are able to create a redstone signal or perform unique actions when provided with a redstone signal. Redstone-related blocks can be used in combination to create circuits and complicated mechanisms that can be used to make automatic farms, item sorters, flying machines, and more.
A game tick is the basic unit of time in Minecraft, and is equivalent to 1⁄20 seconds (0.05 seconds)(A tick calculator can be found here. Every game tick, various aspects of the game are updated such as player movement, block updates, mob spawns, etc.
In Java Edition, most (but not all) redstone-related events occur in multiples of 2 game ticks. A common convention is to measure times of redstone events in "redstone ticks" which are equivalent to 2 game ticks (0.1 seconds). Events that happen in 1 game tick are said to occur in 0.5 redstone ticks. "Redstone tick" is a community-created term, and not an official unit of time in Java Minecraft. The Minecraft game code and commands such as /tick use game ticks.
In Bedrock Edition, a redstone tick is a unit of time that describes a delay of two game ticks, creating a 1⁄10 of a second delay.
The redstone system is calculated on concurrent threads, meaning that redstone updates are processed independently of the main game loop. This architecture utilizes a two-phase tick system, known as produce ticks (P-Ticks) and consume ticks (C-ticks), or alternatively as Output Ticks and Input Ticks.
These two phases form a single redstone tick, which spans 2 game ticks. There are 10 redstone ticks per standard 20-game-tick second.
Tick cycle
Component Behavior
The transmission and timing of redstone signals are determined by these ticks, which govern when redstone devices output power and when they respond to input.
Conductivity is the idea that some blocks can be powered and some cannot. Conductive blocks are blocks that can be powered and non-conductive blocks are blocks that cannot be powered.
Conductive blocks are often called "opaque" blocks, because many common blocks that can be powered are opaque; for example, stone, dirt, wood. Non-conductive blocks are often called "transparent" blocks, because the most common example is glass. However, whether or not you can see through the block does not determine whether a block can be powered.
When some blocks receive a redstone signal, they can activate redstone mechanisms or provide a redstone signal to certain blocks. These blocks are said to be "powered".
Strongly powered blocks can power redstone dust, and weakly powered blocks cannot. Strongly powered is sometimes called "hard powered", and weakly powered is sometimes called "soft powered".
Redstone components are blocks that are used to create redstone circuits and advanced mechanisms.
A redstone signal is Minecraft's analog to electricity, and is generated by redstone power components. A redstone signal has a "signal strength", which is an integer between 1 and 15. The strength of a signal does not affect how redstone mechanism components operate. For example, a piston extends the same length and at the same speed regardless of whether it receives a redstone signal of 1 or 15. A redstone lamp produces the same amount of light, no matter the strength of the signal.
Only redstone power components can generate a redstone signal. Some components generate a continuous signal, while others generate a signal pulse. Some components generate a signal on demand, such as a lever or a button. Other components generate a signal when some condition has been met, such as a mob walking over a pressure plate, or an observer detecting a block change.
A redstone signal can be transmitted only by redstone transmission components such as redstone dust, redstone repeaters, and redstone comparators.
Redstone mechanism components are activated when they receive a redstone signal. This signal can be supplied by an adjacent power component generating a signal, a powered block, powered redstone dust being configured to point into the mechanism or placed on top of the mechanism, or a powered redstone repeater or a redstone comparator pointing into the mechanism. A mechanism component performs some kind of action when activated, such as moving, producing light, or making a sound.
Upon receiving a redstone signal, mechanism components may behave in different ways. Some mechanisms perform an action only once when they receive a signal, others continuously perform an action while receiving a redstone signal.
Some mechanism components perform an action only once upon receiving a redstone signal. These components do not perform another action until the signal stops, and they receive a new signal some time later. This type of behavior is referred to as rising edge because they occur when the signal goes from 0 then up to a positive value. The opposite is falling edge, where a signal goes from a positive value to 0.
Some mechanism components change state when they receive a redstone signal (rising edge activation) and return to their original state when the redstone signal stops (falling edge deactivation). These blocks have an initial deactivated state, and an activated state. For example, a redstone lamp starts producing light when it receives a redstone signal, and does not stop until it stops receiving the signal.
For blocks such as doors, fence gates, and trap doors, their deactivated state is closed, and their activated state is open. If one of these blocks is already open when it receives a redstone signal, it stays open, but closes when the signal stops.
A copper bulb exhibits mixed behavior. A copper bulb has two block states associated with it: lit, describing if the copper bulb is emitting light, and powered, describing if the copper bulb is currently receiving a redstone signal. Upon receiving a redstone signal (rising edge), the bulb toggles its lit state, and starts or stops emitting light. The bulb's powered state remains true until it stops receiving a redstone signal (falling edge).
Almost every mechanism component block needs a redstone signal to be supplied to the block itself in order to be activated. There are three exceptions in Java Edition: dispensers, droppers, and pistons. These three blocks can be activated by a redstone signal being supplied to them like other blocks, but can also be activated if a redstone signal is supplied to the block above them, even if that block is air.
Another way to think of quasi-connectivity, is to imagine that dispensers, droppers, and pistons have an "activation hitbox" similar to that of a door. A door is two blocks tall, and if either the top or bottom part of a door receives a redstone signal, it opens. Dispensers, droppers, and pistons are one block tall, but they can be activated as if they were two blocks tall.
A complication of quasi-connectivity is that there are scenarios in which, the dispenser, dropper, or piston should be activated by quasi-connectivity, but does not activate until there is a nearby block update. This occurs because redstone blocks can update their neighbors up to two blocks away, taxicab distance. Even though the dispensers, droppers, and pistons have a two block tall activation hit box, the actual block needs to be updated in order to activate, not the block above. Sometimes the source of the redstone signal is too far away to update the actual block. See main article for additional details.
When conductive blocks, often referred to as opaque blocks (stone, dirt, etc.), receive a redstone signal, they can activate mechanism components or power transmission components.
A block can be powered by:
A powered block can activate adjacent redstone mechanism components, and power redstone repeaters and comparators facing away from the block. A powered block may or may not be able to power adjacent redstone dust, depending if it has been strongly or weakly powered.
Blocks that cannot be powered are usually referred to as transparent blocks, glass being a common example.
A block is strongly powered when it can power adjacent redstone dust (including redstone dust on and beneath the block), in addition to activating adjacent mechanism component, and powering redstone repeaters and redstone comparators facing away from the block. A block becomes strongly powered by being powered by a redstone power component, a powered redstone repeater, or a powered redstone comparator.
A block that is weakly powered cannot power adjacent redstone dust, but can still activate adjacent redstone mechanisms, and power redstone repeaters and redstone comparators facing away from the block. A block becomes weakly powered when it is powered only by redstone dust.
Some redstone mechanism components, such as redstone lamps, droppers, and dispensers are conductive blocks and can be powered. When one of these blocks is powered, it is simultaneously activated (excluding copper bulbs, which can be powered and inactive). These blocks do not need to be powered in order to be activated. If one of these blocks is activated, it does not mean that it is powered.
Conductivity is a block property that determines which blocks can be powered and which cannot. Specifically, conductive blocks can be powered and non-conductive blocks cannot be powered. Conductive blocks are often called "opaque" blocks, because many common blocks that can be powered are opaque; for example, stone, dirt, wood. Non-conductive blocks are often called "transparent" blocks, because the most common example is glass. However, whether or not you can see through the block does not determine whether a block can be powered. Most conductive blocks share a similar set of properties, and most non-conductive blocks share their own set.
Most conductive blocks are made of materials that have the solid-blocking property, and are full blocks, with exceptions noted below.
As noted above, most conductive block are full solid blocks with the exception of soul sand and mud (7/8 of a block tall).
Mangrove roots, Monster spawners[Bedrock Edition only], Trial spawners[Bedrock Edition only], Big dripleaf[Bedrock Edition only] and closed shulker boxes[Bedrock Edition only] are the only conductive block that can be waterlogged.
Blocks of redstone, observers, and pistons are full solid blocks made of materials with the solid-blocking property, but are non-conductive.
Many non-conductive blocks exhibit their own unique behavior regarding what blocks can be placed on them, and what blocks they can be placed on. See Opacity/Placement.
For example, leaves are a full solid non-conductive block, but certain redstone-related blocks cannot be placed on them:
Block updates are how most redstone components "tell" each other that they need to change states.
When a change occurs somewhere in a redstone circuit, it can produce other changes in surrounding blocks in what is called a block update. Each of these changes can then produce other changes in their surrounding blocks. The update propagates following the redstone circuit rules within loaded chunks (block updates do not propagate into unloaded chunks), usually quickly. Note: In Bedrock Edition, block updates and redstone are not connected.
A block update simply notifies other Redstone components and blocks that a change has occurred nearby and allows them to change their own state in response, but not all updates necessarily require changes. For example, if a redstone torch activates and updates the dust below it, the dust may already be powered from something else, in which case the dust doesn't change state and the update propagation stops there.
Block updates can also be generated by any immediate neighbor block being placed, moved, or destroyed.
Solid blocks don't "know" if they're powered or not. Block updates simply update enough blocks around a redstone component to update other redstone components around the solid block (for example, a pressure plate updates its neighbors and the neighbors of the block it's attached to, including the space under that block, which might be redstone dust).
In addition to block updates, comparators can be updated by containers (including detector rails with container minecarts on them) and certain other blocks, up to two blocks away horizontally when their state changes (for example, when their inventory changes). This is known as a comparator update.
The following redstone components produce block updates up to two blocks away by taxicab distance, including up and down:
The following redstone components produce block updates in their immediate neighbors, including above and below, and in the immediate neighbors of the block they're attached to:
The following redstone components update only their immediate neighbors when they change their state, including above and below:
The following redstone components do not produce block updates when they change their state (although any block produces a block update in its immediate neighbors if moved or destroyed):
| Gameplay | |
|---|---|
| General mechanics |
|
| Technical mechanics | |
| Survival |
|
| Combat | |
| Environment | |
| Movement | |
| User interface | |
| Visuals | |
| Removed | |
| Unintended | |
