I have a long redstone wire in one direction (of course with repeaters). For example I have a piston 1000 blocks away and I press a button, so that the piston should do something - it will not do anything, because the chunk, where the piston is, is not loaded, I know this. But when I create the wire (not powered) and then go back an power it, only the wire within the loaded chunks power itself. But if I go along the wire, I will get to a point, where the wire changes from powered to not powered. And this point is exactly the last chunk that was loaded, when I powered the wire. I expected, that the wire updates itself when new chunks are loaded, but it only does, when I change a block beside where the wire changed its power.
I hope, I could explain it understandable. Please ask, if you have fourther questions.
See this video for more details: http://www.youtube.com/watch?v=e_MM97ifASw
Related issues
is duplicated by
Attachments
Comments

If chunks are not loaded nothing will happen. This is intentional.

I think, I din't explain good enough. :/ I know, how Redstone works and that nothing happens in unloaded chunks. But the wire does not update, also not when chunks are loaded then!
I will try to explain again. We have a long, long redstone wire which is not powered. I stand at the end of the wire and power it - the redstone wire is powered in all loaded chunks. Then I walk along the redstone wire (new chunks are loaded), but the redstone wire does not update in the new loaded chunks.

Here are some screenshots, I hope, they explain it in a better way.
You see, if you change a block beside the wire (added a gold block), the wire updates, otherwise not.

Reopened due to new description.
The description may be "Long redstone wire does not update in newly loaded chunks"

I changed it - sorry for the wrong title.

No need to be sorry, that was just a suggestion

In the latest version (13w04a) the behavior is even stranger. I filed an issue as MC-8194 which seems to be related to this issue. (However, it's not an actual duplicate... a mod changed the status too quickly unfortunately. 😞 )

It affects more than only redstone. This need to be fixed! (Redstone, Minecraft, Water/Lava)
https://mojang.atlassian.net/browse/MC-8940

This is still reproducible in 13w07a.

This is still reproducible in 13w09a.

...as well as in 13w09b.

Still occurs in 13w09c.
On a side note: While playing around with long redstone wires a bit more, I noticed that both redstone dust and pistons do actually update outside of currently loaded chunks when the energy level changes. The same is true for rail T-intersections. Repeaters and comparators that are placed further away than the "middle" of one of the loaded chunks furthest away from the player (as demonstrated in the video linked above) do not update automatically at all. Torches further away than this magic chunk middle seem to take a (random) amount of time to update when returning to the chunk (which - I think - is caused by the same random update mechanism that is also responsible for randomly growing trees, sugar cane, wheat etc.).
So while this bug still causes a very inconsistent update behavior, my finding offers some kind of workaround for long redstone wires: Simply replace all repeaters with redstone blocks that are pushed by sticky pistons. However, if you need to use other redstone components than just pistons and wires on the "end" of the cable, you'll still have to cause some block update there somehow to make them work.

It looks like that by fixing MC-711 this bug was fixed as well. The problem does not appear in 13w10b for me anymore. Therefore, this ticket can be marked as resolved.

Marked as resolved. Please report if a regression occurs.

This is a continuing problem. On my private server I have a automatic subway station, but when ever it goes out of a spawn chunk, it stops until the chunk is loaded where it then continues to the next station.