Powered rails do not update when additional power sources are added or removed
The bug
Powered rails do not update when additional power sources are added or removed.
How to reproduce
- Build the setup as shown in the attachment below (setup.png
) - Place a redstone block on top of the diamond block
- Take note of how many powered rails are activated
- Place a redstone block on top of the emerald block
- Once again, take note of how many powered rails are activated
- Take note as to whether or not powered rails update when additional power sources are added or removed
→
Powered rails do not update when additional power sources are added or removed
Expected behavior
Powered rails would update when additional power sources are added or removed.
Code analysis
Code analysis by Ismael Rosillo can be found in this comment.
Linked Issues
is duplicated by15
- Unresolved
[Mod] AvomaRicardo Stryki
- 135
- 52
- Confirmed
Low
- Platform
- Block states Minecart Redstone
- power powered_rail rails redstone update update-failure
1.4.1 - 1.21.4
1.4.1 1.4.2 12w49a 1.4.6 1.4.7 13w02b 13w09c 13w10a 1.5 13w11a 1.5.1 13w18b 13w18c 1.6.1 1.7.4 14w03b 14w05b 14w06b 14w07a 14w08a 14w11b 1.7.9 14w18b 14w19a 1.7.10 14w27b 14w32d 14w33c 14w34a 14w34b 14w34c 14w34d 1.8-pre1 1.8 1.8.1-pre3 1.8.6 1.8.8 15w31c 15w36d 15w44b 1.8.9 15w51b 16w03a 1.9-pre1 1.9-pre3 1.9.1 1.9.2 16w14a 1.10 1.10.1 1.10.2 16w32a 16w32b 16w33a 16w35a 16w41a 1.11.2 17w06a 17w18b 1.12-pre1 1.12-pre2 1.12-pre6 1.12.1-pre1 1.12.1 1.12.2 17w43a 17w43b 18w03b 1.13-pre1 1.13-pre3 1.13-pre4 1.13-pre5 1.13-pre6 1.13-pre7 1.13-pre8 1.13-pre9 1.13-pre10 1.13 18w30a 18w30b 18w31a 18w32a 18w33a 1.13.1 1.13.2-pre1 1.13.2-pre2 1.13.2 18w47b 18w48a 18w48b 18w49a 18w50a 19w02a 19w03a 19w03b 19w03c 19w04a 19w04b 19w05a 19w06a 19w07a 19w08b 19w09a 19w11a 19w11b 19w12a 19w12b 19w13a 19w13b 19w14a 19w14b 1.14-pre1 1.14-pre2 1.14-pre3 1.14-pre5 1.14 1.14.1-pre1 1.14.1-pre2 1.14.1 1.14.2-pre1 1.14.2-pre2 1.14.2-pre3 1.14.2-pre4 1.14.2 1.14.3-pre1 1.14.3-pre2 1.14.3-pre3 1.14.3-pre4 1.14.3 1.14.4-pre1 1.14.4-pre2 1.14.4-pre3 1.14.4-pre4 1.14.4-pre5 1.14.4-pre6 1.14.4-pre7 1.14.4 19w34a 19w35a 19w36a 19w37a 19w38b 19w38a 19w39a 19w40a 19w41a 19w42a 19w44a 19w45a 19w45b 19w46a 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre5 1.15-pre6 1.15-pre7 1.15 1.15.1 1.15.1-pre1 1.15.2-pre1 1.15.2-pre2 1.15.2 20w06a 20w07a 20w08a 20w09a 20w10a 20w11a 20w12a 20w13a 20w13b 20w14a 20w15a 20w16a 20w17a 20w18a 20w19a 20w20a 20w20b 20w21a 20w22a 1.16-pre1 1.16-pre2 1.16-pre3 1.16-pre4 1.16-pre5 1.16-pre6 1.16-pre7 1.16-pre8 1.16-rc1 1.16 1.16.1 20w27a 20w28a 20w29a 20w30a 1.16.2-pre1 1.16.2-pre2 1.16.2-pre3 1.16.2-rc1 1.16.2-rc2 1.16.2 1.16.3-rc1 1.16.3 1.16.4-pre1 1.16.4-pre2 1.16.4-rc1 1.16.4 20w45a 20w46a 20w48a 20w49a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w08b 21w10a 21w11a 21w13a 21w14a 21w15a 21w16a 21w17a 21w18a 21w19a 21w20a 1.17-pre2 1.17-rc2 1.17 1.17.1 21w39a 21w40a 21w41a 21w42a 21w44a 1.18-rc3 1.18 1.18.1 22w05a 1.18.2-rc1 1.18.2 22w14a 22w17a 1.19-pre1 1.19 1.19.1 1.19.2 22w43a 1.19.3 23w03a 23w04a 1.19.4 1.20 1.20.1-rc1 1.20.1 1.20.2-pre2 1.20.4 23w51b 24w11a 1.20.6 24w19b 1.21 24w33a 1.21.1 24w34a 1.21.3 1.21.4
Created Issue:
Power rails don't update his status (see screenshot)
When you place a redstone torch next to a power rail and you place one more torch and break the firts torch the enegy of the rails dont change (see screenshot)
When you place a redstone torch next to a power rail and you place
one moretorch and break the firts torch the enegy of the rails dont change (see screenshot)When you place a redstone torch next to a power rail and you place another torch and break the firts torch the enegy of the rails dont change (see screenshot)
is duplicated by
It's still a problem in 13w18b
To create a super long powered rail line powered by 1 torch:-place a long line of power rails
-place a redstone torch anywhere near one end
---repeat-----
-place a redstone torch down at the last powered rail
-place a redstone torch down at the first unpowered rail
-break the first redstone torch
-break the second redstone torch
---reapeat----and you will have a super long powered rail line powered by only 1 redstone torch.
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
When you place a redstone torch next to a power rail and you place another torch and break the firts torch the enegy of the rails dont change (see screenshot)
This could be fixed by adding a power level rather than only true/false.
Léa Gris Was something wrong with your setup? Definetly cannot reproduce it the same way as 1.12.2 in 18w03b.
Here video to show the difference between the versions: https://youtu.be/RZduzSD8cfQ
Confirmed in 1.8-pre1
When you place a redstone torch next to a power rail and you place another torch and break the firts torch the enegy of the rails dont change (see screenshot
)This could be fixed by adding a power level rather than only true/false.
is duplicated by
Is that related to MC-957 ?
If you're playing the 1.4.3 please update to 1.4.4 and report here if this error persists.
Duplicate of MC-957, please use the search function to see if your bug has already been submitted. Currently over 53% of tickets are being closed as duplicate.
Duplicate of MC-957
This issue is a duplicate of MC-957. It has been linked to the original bugreport.
Please search before reporting any bugs, as it's likely that one exists already.
Ok, prepare for something... Could please a mod mark the versions for every bug I tell you here? That would be nice.
I have a world set up for fast bug testing. That means that going into each bug report and saying "Confirmed for 1.10.1" is way more work than actually testing it. So I want to confirm for 1.10.1 with this comment:
MC-4, MC-9, MC-14, MC-87, MC-112, MC-201, MC-212, MC-234, MC-258, MC-460, MC-577, MC-667, MC-679, MC-696, MC-697, MC-849, MC-868, MC-926, MC-957, MC-997, MC-1040, MC-1127, MC-1133, MC-1168, MC-1207, MC-1218, MC-1297, MC-1390, MC-1429, MC-1530, MC-1531, MC-1538, MC-1541, MC-1555, MC-1578, MC-1673, MC-1685, MC-1691, MC-1981 and MC-2023.
All of these are tested in 1.10.1. For some others I have additional information:
MC-711 not testable with my setup because of a crash that's new in 1.10.1.
MC-779: At least some appear outside, didn't test all. What's sure is that no general solution got introduced.
Confirmed MC-1511 for stone button, lever, torch, redstone dust, normal rail, end rod, tripwire hook, ladder and flower pot. Others are untested.
Confirmed MC-1874 for chest, brewing stand, enchanting table and flower pot. Others are untested. It's apparent that there isn't a general solution here either.
Does MC-957 describe your issue?
Does MC-957 describe your issue (but for powered rails)?
Thank you for your report!
We're actually already tracking this issue in MC-957, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicates MC-957
Duplicate of MC-957.
Thank you for your report!
We're tracking this issue in MC-957, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Please note that we only accept issues in vanilla, unmodified environments. Please keep this in mind in the future ![]()
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-957, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any additional information to the main ticket it would be appreciated.
Please be sure to use the search feature before creating a ticket to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 💬 Mojira Discord
The rails thing is MC-957 and happens because they don't have the power states that redstone has.
Thank you for your report!
We're tracking this issue in MC-957, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-957, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Would MC-957 describe your issue?
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
If you're placing a redstone block next to a powered rail that is already powered by a redstone torch and the range of activated powered rails isn't increasing, that is MC-957. If that doesn't describe your issue, then please record a video of this happening and attach it to this report.
If you are on Windows, you can use Windows+Alt+R to open a built-in app for recording game footage.
If you are on Mac (Mojave or later), you can use Shift+Command+5 to open a built-in app for recording your screen.
In case you don't have a program to record videos, we recommend using the free recording software OBS.
In case the resulting video file is too large to be uploaded to the bug tracker directly, please upload it elsewhere (e.g. as unlisted video on YouTube) and link to it here.
Thank you for your report!
We're tracking this issue in MC-957, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki








<Comment removed by MOD>
I'm spanish don't insult me man
Recreated in 1.4.2, moving the torch doesn't update the rails, normally only 8 rails are powered either side of the torch but with this bug I managed to get 16 rails powered one side of the torch this is because the rails don't update from their powered state once the torch is moved.
As you can see from the screenshot, more rails are powered one side of the torch than should be powered due to this bug.
Confirmed for 12w49a
This is still and issue in 1.4.7 and in Snapshot 13w02b
In 13w02b this effects the Activator Rail and Powered Rail in the same way.
The powered rail update changes slightly depending on the power source type(torch or leaver).
Please look at the screen shot attached named 13w02b Powered Rail Bug
From left to right:
Only when the first unpowered piece of track to the north has a block update will the track get powered.
Still happens in 13w05b
This affects 13w09b. Activator rails are affected as well.
Still in 13w10a. Redstone Blocks behave like the levers do in Nic's comment.
still in 1.6.1 pre
Is this still a concern in the latest Minecraft version 14w03b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
This is still valid indeed.
Still present in 08a
I believe this bug has been present since powered rails were added. I've tested it back to 1.0 but not in beta 1.5 because of no creative mode back then. I'm surprised such an old bug hasn't been fixed lol.
Confirmed in 14w11b.
This is not a bug! You see, when you put redstone current (e.g, lever or redstone torch etc.) down it is carried through the rails. Thus, if you destroyed another redstone current, the other redstone current would be carried on.
A redstone torch can normally only power a rail up to 9 blocks away, which makes a total of 17 rails in a row, if the torch is placed next to them. The bug here is that in some cases, redstone torches placed or removed next to an active powered rail are not updating the rails, meaning that some rails do not go inactive, while others do not become active. This means that a single torch can be made to power extremely long (perhaps infinite) sections of powered rail, if the torches are added and removed in the right places, and the right order.
Placing or removing a torch only seems to update the rails if it is placed next to the last active powered rail in a row that is correctly powered by another torch. If it is the only torch within range, then the rails will be updated correctly.
Still not fixed as of 14w27b
This can be exploited by mapmakers to create enormous self-powered tracks with but a pair of torches.
Still reproduceable in 14w32d!
Confirmed in 1.8-pre 3.
Confirmed in 1.8.6
Confirmed 15w31c
Confirmed for 15w44b
Confirmed for 1.8.9 and 15w51b.
Confirmed for 16w03a.
Confirmed for 1.9-pre1
Confirmed for 1.9-pre3
Confirmed for 1.10.
Should be easy to fix by adding power levels like in redstone.
Confirmed for 1.10.1.
Confirmed for 1.10.2.
Confirmed for 1.12.1
Can confirm for 17w43a/b
Bug still present in 18w03b
You could fix that adding a redstone torch near the non-activated rail. It worked for me.
Can confirm for 1.13-pre3
Confirmed for MC 1.13-pre4 too.
Confirmed in 1.13-pre7.
Confirmed for 1.13-pre8.
Confirmed for 1.13-pre9.
Confirmed for 1.13-pre10.
Confirmed for 1.13.
Confirmed for 18w30a.
Confirmed for 18w30b.
Confirmed for 18w31a.
Confirmed for 18w32a.
Confirmed for 18w33a.
Confirmed for the last snapshots (1.13.1-pre1, pre-2) and 1.13.1.
Confirmed for 1.13.2-pre1.
Confirmed for 1.13.2-pre2.
Confirmed for 18w48a
Confirmed for 18w48b
Confirmed for 18w49a
Confirmed for 18w50a
Confirmed for 19w02a
Confirmed for 19w03a
Confirmed for 19w03b
Confirmed for 19w03c
Comfirmed for 19w04a
Confirmed for 19w04b and 19w05a
Confirmed for 19w06a
Confirmed for 19w07a
Confirmed for 19w09a
Confirmed for 19w11a
Confirmed for 19w11b
Confirmed for 19w12a
Confirmed for 19w12b
Confirmed for 19w13a
Confirmed for 19w13b
Confirmed for 19w14a
Confirmed for 19w14b
Confirmed for 1.14 pre-1
Still in 1.14 Pre-Release 2
Confirmed for 1.14 pre-3
Confirmed for 1.14 pre-4
Confirmed for 1.14 pre-5
Still in 1.14 Release
Confirmed for 1.14 Release
Confirmed for 1.14.1 pre-1
Confirmed for 1.14.1 pre-2
Confirmed for 1.14.1
Can also confirm for 1.14.1 Release
Still in 1.14.2 Pre-Release 1 and 1.14.2 Pre-Release 2
Glad someone reported this, I thought I was going crazy (built a string farm from Pixlriffs but the minecart keeps stopping on a powered rail). Still an issue in 1.14.2 pre-release 4.
Still in snapshot 20w17a
and 20w18a
Affects 1.16 pre2
Confirmed in 1.16-pre5.
Confirmed in 1.16-pre6.
affects 20w27a
confirmed for 20w45a
cofirmed in 1.4.1
Only the latest release and the latest snapshot are useful. And that version is already in the list.
Confimed on 1.16.4
Also affects Activator Rails.
There is an easy workaround, just break the rail, add the source and it works.
I am able to confirm this behavior in 21w39a. Here are some extra details regarding this problem.
The Bug:
Powered rails do not update when additional power sources are added or removed.
Steps to Reproduce:
Observed Behavior:
Powered rails do not update when additional power sources are added or removed.
Expected Behavior:
Powered rails would be updated when additional power sources are added or removed.
Can confirm in Release 1.17.1
An attachment with a disallowed file extension has been removed from this ticket.
Executable files and documents are not allowed as attachments.
Please attach crash reports, log files and screenshots as they are instead of pasting them into a document.
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Can confirm in 23w03a
Can confirm in 23w04a
Can confirm in 23w06a
Hey Avoma! Though this is not a code analysis, it is a possible fix for this bug, I hope this will help Mojang fix it.
Cause
Powered rails try to check and update when a neighbour change happens, that is okay. The problem is that if you set a redstone power source next to an already powered "on" rail, neighbors will not update because there are no block state changes (powered=true is equal to powered=true). A possible way to fix this is by making the powered block state depend on a power number state, so every time a redstone signal changes every rail will update neighbour rails up until they're far enough from source.
Workaround
A few months ago I was messing with PoweredRailBlock.java to make curved powered rails, and I noticed how unsafe are methods findPoweredRailSignal(Level,BlockPos,BlockState,boolean,int) and isSameRailWithPower(Level,BlockPos,boolean,int,RailShape).
Basically what I did was remove the proximity variable (the int param of this method that increases every time it checks a further rail) and make powered rails use a new "power" block state that goes from 0 to 9 (0 equals to unpowered, 9 is fully powered). Then, changed findPoweredRailSignal again to only check directly connected powered rails (and not all 8) and isSameRailWithPower to only check the given's rail "power" state (previously it did check if that rail had a redstone source or else check for a further away neighbour block). Also, the two methods mentioned above will now return power state (int) instead of powered state (boolean).
In other words, the new behaviour will make findPoweredRailSignal and isSameRailWithPower get their direct adjacent's power. End result of these two methods:
Now, we are missing something: method updateState(BlockState,Level,BlockPos,Block). This is the only method that uses findPoweredRailSignal, and is the one that sets the rail's power value when it detects a neighbor change. We will update it in order to set the proper "power" block state, by getting instead the adjacent connected powered rails highest signal, and decrease it by 1 (so power will be lesser the further the rail is full from source rail):
After this workaround, the bug seemed fixed.
Problems:
In 1.20.2 Pre-Release 2
Can confirm, bug still occurs in 1.20.2 Pre-release 2.
This could be fixed in the experimental redstone improvements hopefully
confirmed in 1.21.1