Comparator side input does not recognize all types of redstone power sources

I really dont understand the way this is supposed to be fixed. Besides, the picture shown is intended behaviour, because if the redstone block powered the comparator from the side, the redstone block still carries a signal strength of 15, or its simply considered "powered". Since the first piece of redstone it powers also carries the same signal strength, both inputs carry equal power, and thus the signal should pass through, even if it does power it from the side. But thats not what I wanted to say.

Mojang added redstone blocks in 1.5, arguably one of the best additions to redstone ever. I dont think that jeb realised what he changed while fixing this bug, or he doesnt realise the impact on every redstone circuit it has. Redstone blocks now appear to power any block next to them strongly, like a repeater, though without updating things next to it. I really hope that this is not intended behaviour. It's broken at least 50% of every single redstone creation built since 1.5.

I've been redstoning for a very long time and when you do, you like to make use of every single thing that works differently from others, so that you can always find a solution to problems in many situations, this is one of them. Comparators only being powered in the way they used to be, that is, not by blocks but only by redstone dust, comparators or repeaters, was really useful. Mainly when you try to fit circuits in small spaces and need to lead power somewhere. I dont understand why a 'bug' such as this one is fixed while clear bugs such as MC-54711 are not being fixed. The behaviour in that report just flat out makes no sense, even if its explainable using the code.

You could argue that small things that may not be expected behaviour should be removed from the game because its confusing to people that haven't often used redstone. However, 99% of players follows redstone tutorials on youtube, from people that can make incredibly awesome designs. They sometimes put weeks into designing even little creations, and many people have done that over the past few years, yet this fix makes all that work useless. I'm one of those people and this here broke just about everything I made using instant redstone mechanics. Just about every design on youtube is now broken and many youtubers (including me) will be getting requests to fix these designs, where in some cases thats not even a possible thing anymore. You could almost take down all those videos because they are useless now anyway, and you dont want people following the tutorials anymore because they will be quite disappointed.

Another fix in 1.9 I can name is the way redstone on top of slabs or glowstone now redirects redstone on blocks (diagonally) below, where the redstone source would come from. Though this fix does make sense to some extent, the 'bug' has been in the game since before 1.5 and was used in absolutely countless redstone builds, where in many it was even essential for it to work properly. If you didnt want it to redirect, but you did need the signal, just use a slab, and there is another solution to one of your problems. I loved the way redstone worked back in 1.8, where you have all these little funny things you could know to work around problems you come across. Yet another one is gone and redstone is getting less and less interesting to play with.

So, I just really hope to see this 'fix' removed, and I hope that mojang is able to move their focus to bugs that really matter. I did not intend for this to be taken offensively, if it was. This is just straight out my opinion on why this fix is so bad and I can hardly believe that the bug I mentioned is still in the game.

See also MC-92562

It would destroy the Redstone circuits, when other signals also blocks Redstone could give to the comparator. As an example, check out the page (with download-world) http://minecraft-de.gamepedia.com/Redstone-Schaltkreise#Welt_zum_Download.2F_.C3.B6ffentlicher_Wiki-Server

Yes, that's been how it works since 1.5, when comparators were introduced. So why should it be changed because this is suddenly considered/accepted as a bug, and break all previous designs so we should just start over again from the 5x5 to the 10x10.

This is the bug report of redstone blocks powering blocks next to them strongly MC-92562.
Fix that = Unfix this.

Even though I don't play mc anymore, I agree with DicoTheRedstoner; this 'bugfix' breaks more than it fixes and should therefore not be implemented in 1.9.

Completely agree with Dico. This is one of times, where a tiny "bug" gets fixed, without any concern what it breaks. Hardly anybody was missing the feature to disable a comparator with a redstone block from the side, some contraptions even work with the behaviour, that this wasn't possible.

Redstone as it is, is great. Toying around with it, in most cases does more harm than good.

You really just worded what I tried to accomplish in a few lines, thank you.

This comparator issue didn't even get fixed. It still ignores powered blocks on the side.

Quoting Jeb:

> "Fixed" as in "fixed for redstone blocks". Other signal sources have not been changed

This "fix" breaks more than it fixes.

A redstone block shouldn't power things behind the blocks it touches. This makes it extremely hard to use them for their original intended purpose (sticky pistons) without breaking the circuit they're in.

If I could downvote this bug report, I would. Why on earth was this even an issue. You have directional redstone: redstone dust, repeaters and comparotors. And there in non directional redstone. Redstone blocks, levers, torches and buttons. Are you saying levers next to comparators should also interact? Ofcourse not.

Redstone components that power blocks next to them also powered comparators, and one more case because the side of the comparator redirected the redstone towards it, oddly, but its nice that way. For example, a redstone torch doesnt power blocks next to it, and thus it doesnt power comparators next to it either. It does power pistons, but solid blocks dont receive a powered state. The same goes for redstone blocks and other powered blocks.

Like Dico said it... this Bug DIDN'T got fixed!

What is this nonsense, and why did this get 'fixed'? The comparator never worked this way. If you put buttons/levers/torches anything next to it, it dosn't turn off. Only redstone dust could be used for the compare input. Why should it be different with redstone blocks? I think actually "fixing" this bug is a far worse bug, this should get reverted!

From their beginning comparators have required strong side-powering to function. They pull signal from behind like repeaters, and require strong powering from the sides to change operation, also like repeaters. So this was never a bug to begin with, just someone who didn't understand proper redstone functionality. And that basic functionality is not changed by this fix.

From their beginning RedStone Blocks behaved exactly like any other 'strongly powered' block, except they were simply inherently strongly powered, rather than requiring power pushed into them. They have never behaved like 'omnidirectional repeaters' which is how they behave now. This change severely breaks any redstone contraption that uses redstone blocks (most of them) and throws slimestone (including Missile Wars and perhaps most other Realms prefab worlds) out the window for no functional gain and serious functional loss.

Cube Hamster explains also:
https://www.youtube.com/watch?v=cXm6JlCn8EY

It also creates a lot more BUD situations, which are always difficult to predict, while breaking a number of traditional piston BUD designs which are well understood.
For example:
If you put down a redstone block, put down lamps in a 5-wide diamond all around it, and then break the redstone block, the lamps 2 blocks away from the redstone block stay lit.
Screen shots will be attached.

"Fixed" for a future version per Searge:

I discussed MC-5951 with @jeb_ and we decided to change the behavior of the redstone block back to what it was and fix the bug differently.

https://twitter.com/seargedp/status/666541482401251328