Edited by @unknown:
In worlds of the Old type, redstone ticking only occurs within the central 96 x 96 blocks. The active area does not depend on the player position nor the Simulation Distance setting. Block updates, on the other hand, work normally.
Steps to reproduce:
1. Create a world with the Old type.
2. Place a redstone torch with a redstone dust beside it, within 32 blocks of any edge.
Expected results: The torch powers the redstone dust.
Actual results: The redstone dust is unpowered.
Original description:
Started an old world type with experimental gameplay enabled when it was first released, now with the prior and latest update redstone wont update. So all buildings and devices that used to function no longer update properly. Taking it out and rebuilding it doesn't work either. I have tried to copy and export it, but the new files wont update either. Switching it to infinite world type fixed the issue, but this doesn't help me still use my old world type.
screenshot and world attached
Related issues
is duplicated by
BDS-899
Redstone not working
MCPE-35300
Redstone not being powered within two chucks from world edge
MCPE-35420
Redstone Devices Error
MCPE-35995
Red stone does not work on old world type
MCPE-36864
Redstone won't work at the edge of the landscape in old worlds.
MCPE-37807
redstone doesnt work at all
MCPE-40655
Redstone system can't work normally on the old world type.
MCPE-40883
Redstone working in certain parts of world but in other parts not working at all
MCPE-40923
Redstone is broken on old worlds
MCPE-41501
Last blocks of edge in Old Worlds
MCPE-42043
powered rails do not work anymore
MCPE-43817
Redstone will not receive/transmit power.
MCPE-44599
Redstone not working in old worlds
MCPE-46884
Redstone Doesn't Work
Attachments
Comments
migrated
migrated
I wonder if this fix, that is only active when you enable experimental gameplay would help with it?
The power output of Redstone Comparators is no longer lost after a world is converted from Xbox One Edition
Auldrick
I was able to confirm this using your attached world imported into Windows 10 1.4.2.0. However, I could not reproduce the problem using a new Old-type world created in 1.4.2.0, so it is probably an upgrade issue, as you said.
Replacing components has no effect. It acts as if no redstone ticks are being processed in the world.
Auldrick
Edited:
@unknown discovered that redstone ticks are being processed in the center of the world. The problem is that the redstone ticking area is permanently set to the 96 x 96 bock area centered on the center point of the world. It has nothing to do with Experimental Gameplay, and has probably been working this way since 1.4.0. I have updated the summary and description of the ticket to reflect the actual bug.
The redstone ticking area should be centered on the player, and its size should be determined by the Simulation Distance setting, just like the block update area is.
As a possible workaround, you might be able to move your redstone inward from the edge. Redstone more than 32 blocks from the edge should work properly and continuously.
migrated
If you are 32 blocks away from the border redstone works fine
migrated
I also have the same problem in version 1.9 and can't use redstone when near the edge.
migrated
This is a really annoying bug that needs to be fixed. Can confirm in 1.10.0.4.
migrated
Still a bug as of v1.12.0.4
migrated
A really easy fix to this would to allow you to set the simulated tick range to 14. That happens to be two more chunks out then the current max, or 32 blocks. ( Right now it has to be a value between [2, 12] )
I am experiencing this bug in v1.11 & hope it gets fixed. Also, if you have the redstone come back into the chunk it acts as if it gets powered btw.
Thank you.
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please make sure the ticket description contains the following information:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Auldrick
I am no longer able to reproduce this issue in 1.17.30. I tried the attached sample world and made a fresh "old"-type world, and the redstone torch lit adjacent redstone dust near the edge in both of them.
Resolving as "Can't Reproduce".