Arqade is a question and answer site for passionate videogamers on all platforms. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I set up a redstone circuit for rotating blocks (with pistons) or flashing redstone lights, everything's fine, but when I exit that zone, the current is not saved, and when I return later, the blocks have stopped moving or the lights have stopped flashing.

I don't want to reassemble part of the circuit each time I come by -- How can I keep the redstone circuit running when I'm far away?.

share|improve this question
up vote 13 down vote accepted

Redstone state is not saved when a chunk unloads, however entity state is. This means minecarts will continue to move when a chunk is reloaded. This in turn means if you replace your redstone clock generators with minecart based clock generators, they'll resume ticking when a chunk is reloaded. Here's the most basic Minecart ticker:

Minecart ticker

You can adjust the lengths of track to get the length of tick you require, and you can combine with other tickers outputs ANDed together to fine tune the length of the tick.

share|improve this answer
Alternatively, if you don't want to mess around with minecart timings, you can use one of these to "jump start" a pure-redstone circuit. – Ben Blank Aug 22 '11 at 23:28
@Ben yup, that too. – fredley Aug 23 '11 at 10:25

This is a known bug: Redstone Repeaters will not update properly across a reload. However, Redstone Torches will, so if you build your system's clocks with torches then they will continue working.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.