Detector rails do not power adjacent powered rails upward on slope

Affects 1.5.2pre as well as 1.5.1.

Is this still a concern in the current Minecraft version 1.6.4 / Launcher version 1.2.5 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

13w39a - confirmed

This bug is over a year old and still not fixed?

?! Anyway, affects level powered rails attached to sloped detector rail when powered rail is above detector rail. PUHLEEZE fix this? seriously complicates my auto sorter :/ 1.7.4

Still valid for 14w20b

I can confirm this in 14w20b, 14w18b and 1.7.9. Is this a case of a bug re-emerging, or has it been consistently broken for all this time?

I have to admit it's fairly esoteric, as a redstone torch is much resource cheaper than a detector rail, but there are times I have wanted to use this due to space issues. It also means that up-slope activator rail mob unloaders don't work, and I have a use for that too (a one way mob unloader, for example).

Still valid for 14w21b

@Christopher Martin
It has been like this all the way since 1.4

Still valid for 14w27b

14w33a - not fixed

Confirmed in 1.8.

Confirmed in 1.8.3. All I want to know is if there is a plan to fix this: yes or no and what potential time frame? Yes, there are workarounds, but seems like a pretty straight forward fix for the next version.

As far as I can tell from testing, detector rails only power themselves, and the block below them – they will activate redstone-sensitive blocks next to them, but don't actually "power" the blocks around them. Dust placed next to them will be powered, but you can't draw a signal out of a block placed next to a detector rail using a repeater. So when the detector rail is above the powered rail, it powers the block next to the powered rail, which in turn activates the powered rail.

The problem is that the concept of redstone signals isn't actually represented in the code anything like we perceive it to work, which makes the mechanics kind of inconsistent and causes a number of the outstanding redstone bugs. Signals are propagated mostly through block updates and checking the blocks around them, rather than blocks actually carrying power information. Powered rails don't actually follow the normal redstone rules for power propagation, and the way they carry power has some bugs of its own. A few of the developers have mentioned that they'd like to give it a major overhaul to fix some of these bugs, and I believe this was considered a possible target for the next major release at one time. I don't know if that's still the case; I haven't heard any mention of it recently, and 1.9 has already been labeled "The Combat Update". They've always got a variety of things in the works, and focus on different aspects as time, interest, and inspiration allow.

Considering all that, what would be a "pretty straight forward fix"? They can:

1. Put in a hacky special-case check that defies the redstone rules. This is how Minecraft was originally cobbled together, which is why it has so many bugs that are difficult to fix. The current dev team was practically hired for the express purpose of cleaning up the code, rewriting it to remove all the hacky special-case code, while preserving intended behavior.

2. Change the redstone behavior of the detector rail to power blocks next to it. This would probably be the simplest clean change, but would also probably break some existing compact builds that depend on the current behavior.

3. Rewrite the whole redstone system, as previously mentioned. Would take a lot of time and effort. Still wouldn't make everyone happy, because so many users are absolutely dependent on buggy, nonsensical behavior.

So is there a plan to fix this? Sort of. Not this issue specifically, and probably not soon. It would depend on how much negative impact any change would have, and whether it would outweigh fixing this particular case. I haven't made much use of detector rails, and am not familiar with the types of contraptions people have built with them, so I don't know what the impact would be. That would be a good discussion for players and the developers to have in order to find the right solution to the problem.

That is not a BUG.It should work like that.Don`t fix it!

Why?

The fix of this issue has caused MC-92697

still an issue in 15w49a

Reopened.

Affects Xbox One, TU34 😞

This part of the tracker is for the pc edition only

confirmed in 18w05a, the exact same behavior occurs.

I don't think that is a bug.
Dont you think that is how redstone works？

fixing this will lead to adding a special case，which is not we want.
redstone should keep simple.

（sorry for my pool English）

"Don't you think that is how redstone works ?"

No. It does not work that way.

Look at it this way:

There is an rail which should give redstone power to the upper rails.

The detector rail should give redstone power to the upper rails, just like it does to surrounding rails on a flat surface.

Sounds the same, huh? 

For anyone that does not understand the bug (for whatever reason) please look at my attachment.

@unknown
I m sorry for my replying too late.

I m afraid that I cannot agree with you.

Rails should only share power with rails of the same type.

In your example, detector rails != golden rails .

So it should not.

Just as golden rails never share power with activator rail.

... that would defy the entire point of detector rails though.

You can use a workaround of using the detector rails to power some redstone and then use that to power the rails which is effectively what should be happening in the first place with the detector rail next to the powered rail. Dimitar is correct, it should act like a flat surface. After all, redstone works on a slope so why shouldn't a rail?

Can confirm in 20w48a.

This is broken again in 21w05b

Can confirm in 1.19.