| Type: | Bug | ||
| Reporter: | Hess | ||
| Resolution: | Unresolved | Votes: | 82 |
| Labels: | piston, redstone, redstone-redirection, redstone_wire | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Platform: | Multiple | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ADO: | 55366 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
When redstone dust is connected to any redstone component that redirects dust but does not produce power(will call this a 'consumer' [*] component to match the technical community's term), unintended blocks will also be powered by it. See attachments Note: This appears to work as if the dust wasn't redirected in the first place while also powering the consumer* component Steps to reproduce:
Expected results: Powering matches with the visual representation(as it does in Java edition), and so only the blocks that seem like they'll be powered, get powered. Observed results: The dust powers not only the block it redirects into, but also blocks it shouldn't from visual logic (testing shows that it powers as if it was not redirected in that case) |
| Comments |
| Comment by Minecraft386882 [ 10/Nov/24 ] |
|
Confirmed in 1.21.44 |
| Comment by Tyler [ 12/Aug/24 ] |
|
Reply from GoldenHelmet:The bottom row is indeed a different issue. I believe the repeater, comparator, and dust correctly redirect the redstone power, and the dust on top of the lamp triggers an incorrect visual in the dust next to the lamp. Many tileable shulker box loaders use exactly this power-redirection by adjacent dust to make the block represented by the lamp in your screenshot sensitive to the change from signal strength 1 to signal strength 2. |
| Comment by Tirefeind [ 12/Aug/24 ] |
|
I do not think 185075 is a duplicate of this. 185075 talks about how dispensers, crafters, and droppers do not redirect redstone dust, while pistons and sticky pistons do. This is talking about how redirected redstone does not fully redirect the redstone pulse and can power a block it shouldn't. |
| Comment by VoicefulBread66 [ 14/Nov/23 ] |
|
Affects 1.20.41 |
| Comment by TanyaLit [ 10/Nov/22 ] |
|
Bug is still present in 1.19,41 |
| Comment by Dac419 [ 26/Aug/22 ] |
|
As of Preview 1.19.30.23 bug still effects target blocks, both piston types and bells as well. |
| Comment by Kith Bryant Benico [ 03/Aug/22 ] |
|
Affects 1.18.0. |
| Comment by Douglas F Correa [ 17/Mar/21 ] |
|
Affects 1.16.210. |
| Comment by GinePik [ 01/Oct/20 ] |
|
Affects 1.16.100.58 Beta. |
| Comment by GinePik [ 17/Sep/20 ] |
|
Affects 1.16.100.56 Beta. |
| Comment by GinePik [ 16/Sep/20 ] |
|
Affects 1.16.40 Hotfix. Affects 1.16.100.55 Beta. |
| Comment by DrAv0011 [ 25/Apr/20 ] |
|
All 1.16 betas until 1.16.0.58 also have this visual glitch. |
| Comment by Tal Melamed [ 15/Apr/20 ] |
|
Added two attachments. The problem here is just visual, but the behaviour is right. |
| Comment by [Mod] GoldenHelmet [ 08/Apr/20 ] |
|
@Etanarvazac Taseet The redstone dust being redirected into the piston in your picture is working as intended. This is indicated by the Mojang developer tweet Tal cited above. As Zeb mentions above, this is an intended parity break from Java Edition. What this bug report is about is the fact that the dust still powers the block it would have powered if it wasn't redirected by the piston. That is not an issue in your circuit, since the lower piston lifts that block away when it is activated by the solid block below the redstone dust. |
| Comment by NewcomerMC [ 12/Mar/20 ] |
|
There is nothing wrong with it, WAI. |
| Comment by Etanarvazac Revorix [ 10/Feb/20 ] |
|
Little more than confirmed... My 3x3 piston door no longer works due to this. Direction of redstone is going to the wrong piston.... The redstone should be going straight. Not to the left. That piston shouldn't be active yet.. |
| Comment by Tal Melamed [ 08/Feb/20 ] |
|
I understand. And thank you very much. That's the way I'm reporting things here. It's not my fault there are so many technical bugs recently haha. Hope at least that reporting them may boost the process a little bit. |
| Comment by [MCPE Mod] Auldrick [ 08/Feb/20 ] |
|
TalMelamed: Just to make sure there's no misunderstanding, as this ticket has already been forwarded to the developers, we will not be closing it as you've suggested unless and until they tell us to. Won't Fix is always a developer determination, and Works As Intended is a developer determination in the great majority of cases. BTW, thank you for the explanation of your testing methods, above. Now that we know, we should have no reason to doubt your updates on the basis of how rapidly you report them. |
| Comment by Tal Melamed [ 08/Feb/20 ] |
|
After thinking, this report should be marked as 'works as intended' or 'won't fix'. Since pistons were introduced to Bedrock Edition, the developers wanted a unique feature which redstone dust will always be connectable to pistons, just like repeaters for example: https://twitter.com/darngeek/status/744817216785244161 In adittion, I want to say things about the first image in the attachments: the redstone tortch is turned off because it's like the redstone dust is a dot, or in a cross texture, however it doesn't look like that because the dust connects to pistons . That's why, if you'll place a repeater next to the block (the block that is above the torch), the repeater will turn on. And the second image - that's kink of like a feature. It's a very useful technique and it used in a lot of creations to make them more compact. That's also why I can relate the case I brought to this one and give a suitable quote from @silentwisperer: "it does not break anything in the game and just allows users to make better contraptions in the game". |
| Comment by Tal Melamed [ 01/Feb/20 ] |
|
Hi Auldrick First of all I always test the bugs I report in-game before reporting them, and check changelogs in an orderly manner for every new update. Actually I have a list with all the relevant bugs and that is how I report them in that little short time between them. I never report things randomly. In addition, you can check the lists that I made: Technical Bugs: https://docs.google.com/document/d/1nziKYzCr4pBdCRj2gIMlfr9MVdWHd6HyafdiBHx9F0c/edit Significant Bugs: https://docs.google.com/document/d/1cOoXay1lKhyOhELdyfUGeOm9_U_PdwDEPlSH72XUzcY/edit |
| Comment by [MCPE Mod] Auldrick [ 31/Jan/20 ] |
|
TalMelamed: We've noticed that whenever there's a new release, you very quickly comment on lots of tickets asking us to update the Affects Version/s. We certainly appreciate the help, and thank you for it! There's just one thing we need to check with you. Your comments seem to come in batches, one right after the other with very little time in between. Are you actually testing your bugs in the new release? It's possible that you are: You might do automated testing, for example, or maybe you do the testing separately from the commenting. But it's also possible that you're assuming the bug is still present because you haven't seen a fix for it. Unfortunately, that logic isn't reliable, because occasionally a bug gets fixed as a side effect of fixing a completely different bug, and neither we nor the developers realize it. It's really important to us that the Affected Version/s field be accurate. Otherwise, we could waste a lot of time trying to reproduce a bug in a release that it doesn't exist in. And then we'd have to set it aside to try again later, and no progress would be made on the ticket. So could you please confirm for us that you're actually verifying that the bug exists in a new release when you tell us it's affected? |
| Comment by MantacidTech [ 20/Dec/19 ] |
|
I wonder if this could be used to create Bug-Powered pistons. |
| Comment by Blobs2 [ 20/Nov/19 ] |
|
I looked at the list of block states in the Bedrock Codebase. Apparently, there is a block state for the redstone power level, but not for which directions the redstone connects. Java Edition does have block states for the north, south, east, and west connections |
| Comment by DrAv0011 [ 02/Nov/19 ] |
|
As [Helper] Jeffrey said, would be better to only change the way that the redstone dust looks like as it is a very used feature (when you knwo how it works) useful for compaction and other things. It is a bug, so it must be resolved, but the best way for the redstone community would be to change the texture instead of changing the behaviour |
| Comment by silentwisperer [ 29/Oct/19 ] |
|
Affects 1.13 on windows 10 and xbox one |
| Comment by Tal Melamed [ 20/Aug/19 ] |
|
MindBlown You are right. This is useful, however the way the dust appears here is the problem. So please update the report and change the title name. It happens in 1.13.0.6 also. |
| Comment by Jeffrey [ 21/Jun/18 ] |
|
Sorry, just realized my comment was misleading. I meant they should just change the way the dust appears. ( connects to the piston but still points towards the block) I understand that there should be as least bugs as possible. But like you said this bug makes more compact contraptions which are very useful for small areas for building. |
| Comment by Specialistol [ 21/Jun/18 ] |
|
No, this shouldn't turn into another Java version that is riddled with "feature" bugs. Yes the design above becomes bulkier one block, but it is still possible. I doubt any contraption "needs" this behavior, they may be slightly smaller with it, but they can be fixed when this bug is fixed. There are other ways to simplify contraptions like this without creating bugs on purpose. Funny enough, I had a suggestion for handling some of the quasi-connectivity disparity, a solid block that acts like redstone dust, which would keep the design in the screenshot compact even after the bug is fixed. You can find that suggestion here if you are interested. |
| Comment by Jeffrey [ 20/Jun/18 ] |
|
Please dont change this behavior. Just make the redstone dust connect with pistons but still power the block that the dust was facing without the piston. Some contraptions like elevators need this behavior. |
| Comment by Filip Saint [ 31/Aug/17 ] |
|
I have an elevator design that is very compact because of this bug. If it is going to be changed, this situation should be fixed, but, if the redstone dust is on its own (with connections to its four sides) it should still power al sides. The shape of the single redstone wouldn't change when a piston is next to it, since it already pointed in that direction. In my screen shot, the same thing happens but this time its a good effect and in my eyes it would more logical to change it to a regular 4 direction shape, like it would do if there where no pistons next to it. In this case redirecting would then have no effect, since the dust already pointed in al directions. For redstone dust lines longer than one, like in the first image, this would indeed be impractical. I don't mind rebuilding my elevator, but it would just be a partial solution for this bug. It is at least not as weird as observer dust redirection |
| Comment by Zeb [ 30/Apr/17 ] |
|
5tr4, this is not WAI, because pistons in Java Edition don't redirect redstone dust. Bedrock Codebase pistons do, as you can see in the picture. Therefore, this is a bug, since the lamps in the screenshot shouldn't be powered if the redstone dust is being redirected by the piston. (The piston-dust redirection is an intentional parity break, by the way.) |
| Comment by Anomonous Anomonous [ 30/Apr/17 ] |
|
This is how it works on Java. works as intended |
| Comment by Zeb [ 10/Oct/16 ] |
|
Affects 0.15.90.8 (0.16.0 beta build 5). |
| Comment by Zeb [ 06/Oct/16 ] |
|
shukafu Technically, if the piston is redirecting the dust (like a repeater would), then it should no longer be powering the lamps, as lamps don't redirect redstone dust. (And neither do dispensers or droppers... pistons used to also not redirect dust, until 0.15.3 when the devs thought it would be a good idea to change that.) |
| Comment by wakafu mafuyuu [ 06/Oct/16 ] |
|
i think its just visual. redstone dust attach to piston and not redirected (meaning its still pointed to lamp) |
| Comment by Zeb [ 06/Oct/16 ] |
|
Affects 0.15.10. (Tested on Windows 10.) |
| Comment by Zeb [ 16/Sep/16 ] |
|
Affects 0.16.0 beta build 4 AKA 0.15.90.7. |
| Comment by PHO [ 05/Sep/16 ] |
|
No there is no legit reason for the lamps to activate as the redstone dust is not pointing at them, and the lamps aren't adjacent to any powered solid opaque blocks either. But in the screenshot the wire is internally treated as if it is pointing to both the piston and the lamp, which is certainly a bug. The reason why the upper lamp is also lit is probably that the lower one is weakly-powered incorrectly. |