Tutorials/Redstone tips

From Minecraft Wiki
Jump to: navigation, search

This tutorial gives general advice for building with redstone. There are a variety of pages discussing how redstone works, mostly collected in the page Tutorials/Redstone.

Planning[edit]

The first step in building a redstone circuit is to decide what it will do and how, in general, it will operate.

  • How and where will it be controlled?
    • Will the circuit be controlled by the player, by mob movement, or something else?
  • What mechanism components will it control?
  • What is an efficient first design?
    • Although refinement often occurs in later stages of the build, starting on a strong foot to tackle the idea will be beneficial later on. Allowing an inefficient/flawed design to manifest can hinder development.
  • How will the signal be transmitted from the controls to the mechanisms?
    • Will signals need to be combined from multiple sources?

Size[edit]

When making redstone, its important to make it a reasonable size.

You shouldn't use a huge amount of space for a single contraption. If many complex redstone circuits are going on all at once, your game will lag. However, you also shouldn't try to create a fully functional redstone circuit in a tiny area. Complex redstone circuits often need plenty of space to function. For example, you cannot create a redstone computer which can perform number operations and display multiple items on a screen at once in only 1 chunk.

For the best redstone results, make your contraption as small as you can with it still functioning, but if you find you're having any troubles with that size, make it bigger. Also, make sure to never underestimate how much time, space or materials you will need. It's much better to overestimate and bring more than you need so that you have extras for the next time.

Creative Mode[edit]

A complex redstone project for a Survival world can be prototyped and tested in Creative mode first, before investing resources and effort in the "main" world. It's handy to keep a creative-mode world handy for such laboratory work, usually a superflat with cheats on. You can also manipulate the game rules for your testing world to your liking, such as to make it permanent day or avoid mob spawning. Creative mode is great for building, because you have an infinite number of blocks, you can break blocks right away, and you can fly around to look all around your structures. You can also press F3 + N to invoke spectator mode, then fly through look inside your circuit.

Once you have finished your redstone contraption and gotten it working, look it over to make sure you understand how it's working now. You may be able to make some improvements here. But eventually, you go back to your survival-mode world, gather the materials, and just copy your design from creative mode. Optionally, you can count how many of each material you used when building in creative mode, so that you will know exactly how much of a certain material to gather when in survival.

Gathering Resources[edit]

When making very large redstone contraptions, you may need farms for renewable resources. Here are some materials you may need to farm:

  • Redstone: There are only a couple of renewable sources of redstone: killing witches (and a witch farm can be difficult) or trading with Clerics. However, it is fairly plentiful in the underground, especially once you have a Fortune III pickaxe to multiply its drops.
  • String: A spider farm can help if your contraption includes a lot of tripwires and/or dispensers), or Piglin bartering can help.
  • Iron ingots (Make an iron golem farm if you need a lot of hoppers or minecarts)
  • Slimeballs: (For sticky pistons and/or slime blocks)
  • Stone and Cobblestone: Smooth stone for repeaters and comparators, cobble for pistons, dispensers/droppers, etc.
  • Nether Quartz: Plentiful in the Nether, impossible to get elsewhere. With it, you get to use comparators, observers, and daylight detectors.

Construction[edit]

It can be helpful to choose a specific set of blocks the player uses to construct circuits. Then, when the player runs into these blocks during the excavation of new rooms in the base, the player knows they are about to damage a previously-built circuit. Common choices include stone bricks, snow block, wool and concrete. (Using different colors of wool and concrete is also a great way to keep track of different circuits)

Be cautious when building circuits near water or lava. Many redstone components will "pop off" (turn into items) when washed over by liquids, and lava will destroy any items it contacts.

Be careful when building circuits to activate TNT (traps, cannons, etc.). Circuits in mid-construction can sometimes briefly power up unexpectedly, which might activate TNT. For example, placing a redstone torch on a powered block, it won't "figure out" that it should be turned off until the next tick, and can briefly power another part of the circuit until then. Placing TNT after the rest of the circuit is complete will help to avoid such problems and the destruction of the device itself. This also applies to any other features of the circuit that may be accidentally activated with such actions (e.g., activating a dispenser before the circuit is ready).

Color coding[edit]

This is a simple yet very effective tip, especially if you create redstone contraptions that have many different parts to them, such as comparator clocks mixed with other redstone items. It is best to use different colored wool, concrete, or terracotta for different parts of the circuit. If you place all of the redstone on top of the same block, for example, out of dirt, soon you may completely forget how your redstone works. Furthermore, this is important if you want to show off the redstone contraptions on YouTube, so people can copy your design in their Minecraft world or you want to be able to go back to your project and understand what parts of the circuit perform what function.

If you don't want to use wool, concrete, or terracotta, you can find other blocks that are different colors from each other. For example, you can use stone variants and wood-related blocks. However, try not to use blocks of similar color, such as a block of coal and black concrete on 2 different parts of a circuit. This may be more time-consuming, but it'll be worth it in the end.

Troubleshooting[edit]

When the circuit isn't working the way it should, take a look at it and try to find the problem. Work through the circuit and test various inputs to find where a signal is "dropped" or gained inadvertently.

  • What part of the wiring actually is not behaving as expected?. Unexpected output behavior is usually only a symptom, where the actual problem resides somewhere in the wiring.
  • Trying to draw power from a weakly-powered block? Maybe a redstone repeater is needed to either strongly-power the block or to pull power out of it.
  • Trying to transmit power through a non-opaque block? Replace it with an opaque block, or go around it.
  • Was a short-circuit created and a redstone torch that should be powered is now burned out? Fix the short-circuit and update the torch to get things going again.
  • Are parts of the circuit activating when they shouldn't be? Maybe accidentally "crossed wires" are allowing a signal from one part of the circuit to activate another part of the circuit, or a repeater's output is being cycled back into its input.
  • Did the circuit go off track from its intended behavior?
  • Are pistons, dispensers, or droppers being indirectly powered when they shouldn't be?
  • Is the circuit based on a tutorial from an older version of Minecraft which no longer works in the current version?
  • Are signals out of sync due to timing issues?

Refining[edit]

Once the circuit is working, consider if it can be improved (without breaking it).

  • Can the circuit be faster?
    • Reducing the number of components or distance a signal has to travel through can speed up the circuit.
  • Can the circuit be smaller?
    • Can fewer blocks be used?
    • Can the redstone dust lines be shortened?
    • Can compact logic gates be used in the circuit?
    • Are unnecessary components used?
  • Can the circuit be more robust?
    • Will the circuit still work when activated by a very short pulse?
    • Will the circuit still work when activated and deactivated rapidly in succession?
    • If either of the above are a problem, can this be fixed by filtering the input?
  • Did an update create the opportunity for a better circuit? (e.g., comparators, locking repeaters, observer, etc.)
  • Can the circuit be quieter?
    • Fewer sound-producing blocks (e.g. pistons, dispensers and droppers, doors, trapdoors, fence gates, and note blocks) will make your device more stealthy around other players.
  • Can any lag be reduced? Machines with many redstone components frequently changing state can cause light, sound, particle, or update lag.
    • Redstone dust creates hundreds of block updates whenever it changes states, and the more the signal strength changes, the more block updates it will produce. Reducing the length of redstone lines will significantly decrease lag. An alternative to redstone dust lines is to use lines of rails which update observers, as rails create much less block updates than dust.
    • Hoppers and hopper minecarts especially may be trying to do several things every tick (accept items pushed into them, push items into other containers, check for item entities above them). Powering unneeded hoppers to disable them or placing containers (such as composters or droppers) above them to disable their item entity checks can help to reduce lag.
    • Redstone torches and redstone lamps change their light level when they change state. Light changes can cause block light updates in hundreds of block tiles around each component. Concealing the component in opaque blocks or placing permanent light sources (torches, glowstone, etc.) nearby can reduce lag from block light updates.
    • Several redstone components produce particles (redstone torches, redstone dust, but especially fireworks fired from dispensers). Too many particles may overload Minecraft's particle rendering and then some particles may fail to render until old particles have disappeared.
    • Every time a block is moved by a piston it can produce block updates in its neighbors, so moving too many blocks at once can produce lag.
    • Several redstone components produce sound when activated or deactivated (pistons, dispensers and droppers, doors, trapdoors, fence gates, and note blocks). Too many sounds at once can overload Minecraft's sound engine and produce lag.


See also[edit]

Video[edit]