Rail duplication Glitch
https://www.youtube.com/watch?v=AoPRufK8r0k
Possibly caused by http://minecraft.gamepedia.com/1.1#Fixes
This bug crashes a 15w31a server.
15w31b no longer crash but duplication is back.
15w31c https://www.youtube.com/watch?v=jq1LUlUtD1g
Environment
Windows 8.1 Java 1.8.0_20
Created Issue:
Rail duplication Glitch
Environment
Windows 8.1 Java 1.8.0_20
- Unresolved
- Open
- Minecraft - Public
- Unconfirmed
- 1.8.1-pre2
https://www.youtube.com/watch?v=AoPRufK8r0k
Possibly caused by http://minecraft.gamepedia.com/1.1#Fixes
This bug crashes a 15w31a server.
https://www.youtube.com/watch?v=AoPRufK8r0k
Possibly caused by http://minecraft.gamepedia.com/1.1#Fixes
This bug crashes a 15w31a server.
15w31b no longer crash but duplication is back.
https://www.youtube.com/watch?v=AoPRufK8r0k
Possibly caused by http://minecraft.gamepedia.com/1.1#Fixes
This bug crashes a 15w31a server.
15w31b no longer crash but duplication is back.
15w31c https://www.youtube.com/watch?v=jq1LUlUtD1g


confirmed for 1.8.1 pre-3
I've attached a simpler reproduction, better suited for a bug report than in-game exploits. When you push the button, the powered rail will drop into 2 powered rail items. It doesn't matter which side of the hole the normal rail is on or which type of rail it is, as long as it's not facing into the hole.
What seems to be happening is that the powered rail getting pushed which has two effects: (1) the adjacent rails are checked for needing-to-rotate, and (2) the pushed rail updates itself, presumably to update its power level. But when the adjacent rail rotates during step 1 it updates all of its adjacent blocks, including the pushed rail which causes it to drop. And then step 2 doesn't notice that the pushed rail has already been broken and so drops it again.
I was able to reproduce this in 1.8.3 with golden, detector and activator rails.
This has been in here forever.. when will it get fixed? 1.8.3 still doing it... my players are making rails as common as wheat....
Bug appears in version 1.1 so it is "only" 3 years old bug
That's the part I don't get.... And it is so reproducible!
Just reproduced on 1.8.4
Jarmo Merinen... affects versions 1.8.5?? No such version yet..?
I've pushed a fix for this out to CraftBukkit & Spigot. Going to see if there are any redstone side effects (hope not).
where do you get the latest versions? I use https://mcversions.net/ and they never had a 1.8.5 posted until after the 1.8.6 was put up (even though they listed the 5/22/15 release date)
The word is Glitch, not glich. Can someone change that (in the labels)?
Oh, this is the fix:
https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/browse/nms-patches/BlockMinecartTrackAbstract.patch
No complaints at all, so I guess it's alright.
15w31a "Fixed" duplication bug.
What is wrong with my bug report, why does nobody notice it?
Mojang gives higher priority to bug reports that have more votes. Since this one doesn't have too many votes, it isn't one of the priorities right now. I agree that they should take a time to fix some of these "forgotten" bugs like this one, but there's nothing we can do other than wait!
How about just closing or deleting this? I know that what is now happening is that people who submit new tickets on this issue, just get their tickets marked "duplicate"... mean while they are busy fixing shit like "new _X_ potion does not work on guardians", etc...
If you close it, maybe one of the new tickets will get a change to grow and prosper.
I already cast my vote... So apparently, only three people give a snit about people cheating the game for unlimited rails and powered rails.
OK, there's seven "watchers" on this issue.. and only three votes.. I voted... who hasn't??
You automatically watch (but does not vote to) any issue where you comment or make a change. That's why there's a lot of people watching, but not too many voting.
Fixed, with thanks to [Mod] md_5!
I kinda fell dumb now, fixed in 5 hours after send tweet to Dinnerbone. Why I didn't do that like year ago.
That was my point, Bentroen... seven people bother to comment, but only three to vote... Who would not think this needed a vote?? I'm glad it is actually getting fixed now.
It's likely that not too many people voted because they actually used this bug. I mean, I can't say I haven't used it myself, but I'm still glad it's fixed now. The less exploits the better in my opinion.