Target blocks - redstone input/parity not working

Yeah I was pissed when I loaded up the update and it didn’t work

I was upset as well, as I just got my phone fixed 2 days after the update dropped. I will be adding my vote to this issue.

I hope it gets fixed soon. This feature is one of the main reasons I liked the new update. 

I've run into this issue too and was very disappointed because I had planned to use it to save on pistons in a machine or two. I really hope it gets fixed because it's a really interesting mechanic.

77Tigers, If I wanted a block that redirects red stone without being powered, I would use a lectern.

can confirm for 1.16.1. Target blocks don't conduct redstone power.

Parity issues can be raised as bugs.

Interestingly, the ability of the target block to conduct redstone power was introduced to Java on the back of a bug report, even though there was no indication that the developers intended this. The "bug" was voted for 6 times and introduced as a new feature 2  months later: MC-173198. This bug currently has 66 votes...

Affects 1.16.20.54 Beta

Will this be fixed for 1.16.2?

Please see https://youtu.be/I_5LQJHrJeU for why this change is so important. I have a giant potion brewer machine that I could make about 20% smaller if target blocks worked like they do on Java. 

I also have a lot of machines that are waiting to be slimmed down with this new block. I really hope it's fixed soon. 

still affects 1.16.100.51

Confirmed on 1.16.20 (iOS). Target blocks do redirect redstone dust, but they behave like glass in any other aspects (aside from reacting to thrown entities of course):

• They can't be strongly powered, i.e. a powered repeater pointing to a target block can not power redstone dust adjacent to the target block.

• They can't be weakly powered, i.e. a powered redstone dust pointing to a target block can not activate a repeater which is supposed to read the power of the target block.

• They can't have an activation power, i.e. you can not turn on a redstone lamp placed next to a target block by giving the target block a redstone signal.

In Java, on the other hand, target blocks behave as solid opaque blocks like cobblestones.

dammit out of everything that could go wrong of course its this. i tested the entire rest of my system to rework it for bedrock, and after building it it wont actually power the pistons. im stupid for only testing the redstone and not the whole device, but the target block being transparent is more stupid

Still being a nuisance in win 10 version 1.16.20

In the picture with a lever connected to Redstone connected to a target block connected to piston that says bedrock, can you tell me the name of the resource pack that is on?

This isn’t a glitch. Bedrock and Java red stone are just way different.

This is a bug, because parity issues that were introduced in the buzzy bees update or later are valid on the bug tracker, this parity issue was introduced in the nether update. See https://www.reddit.com/r/Mojira/comments/g9rjfh/from_now_on_well_accept_bug_reports_about_certain/.

Dear mojang,
There are few other things that should be in a target block

1. A comparator should need to get signal strength of the Redstone dust beside of the target block and check nbt blocks and out put a Redstone signal...

2. Target block should allow Redstone dust through it even tho it will be a solid block(this could be a feature if you devs will)

And thanks for reading this...

It's called Faithful and it's from the Minecraft Bedrock Marketplace 🙂

I don't understand how this is still a bug. I spent hours and hours last night debugging a large contraption I had previously made in a java world, not thinking in a million years that the target block's basic redstone power-up purpose would not work. HOW does this not work? Based on the wiki it looks like the solidness is a single property of this block that needs to change. PLEASE change this so that it works. It can't be that hard. I doubt I'm playing again until this works because this was such a poor experience for me.

Affects 1.16.100.57

Affects 1.16.100.58 Beta.

Does anyone know how long the average bug takes to fix? It's been 4 months and we haven't heard anything. I personally need this bug to be fixed to finish my redstone machine. 

You just have to be patient with these things. The devs will get around it eventually. Try working around the bug for now, I know that it might not be as compact or efficient as you want it, but it might lead to discovering new things 🙂

affects 1.17.0.52

Affects 1.16.50 on ios

Unfortunatly since bedrock has a p/c tick system, there are no producers that are solid. I think this is to do with somewhere in the code. I highly doubt targets will be solid in bedrock in the future because if the devs could do it, they would code it in.

affects 1.17.0

Affects 1.16.200.56 Beta

Effects 1.16.201 also

For now you could use a piston with a unmovable block in front of it to get similar (but not the same) behaviour without the noise of the piston

Frankly, it's a shame he hasn't fixed this problem yet... I wonder if they will ever do so. On Java Edition this problem was fixed in 20w18a by the way.  

Targets not redirecting redstone and being a conductible block isn't the end of the world, soft inversion is almost just as good.

There are several workarounds to not having your redstone dust not redirect onto a block, and honestly, most contraptions don't need it. A redstone contraption will be able to survive without this mechanic just fine; it's not as game-breaking as something like chunk borders breaking redstone contraptions completely. If you want to port over a java redstone contraption, it is best to re-create it in bedrock but with entirely new wiring. I'm not saying that this is fair, but this is how it is and will always be.

Plus I would argue that target blocks are one of the most useful block in the game, in a redstone perspective as a compactor for piston doors etc.

This is a comment section for providing information. NOT whether you think this bug needs fixed or not. People receive email notifications on comments on bugs they follow. Stop spamming us.

Fixing the bug would also stop the spamming but they're not doing that. It's been a year now. I don't mind the spamming as it raises more awareness to the issue. The fact that people are still commenting means people care about this issue. (me included)