Alright This is a repeat of what now appears to be a deleted report. It is very important that this issue is resolved as its the fundamental foundation of red-stone flying and transport machines in all of Minecraft. With that being said, this video will show the issues https://www.youtube.com/watch?v=MJma4GBQdEA&ab_channel=Zombwars77. when watching at 1:30 in the video you will see the repeater timing issues in relation to the Bedrock game client. This is fixable and I am not an idiot and have programed plenty of things and know that time can most certainly be modified in any programing language. If this was not the case no person could make a robot be programed to follow a black line against white paper using a photo resister since timing is of upmost importance in programing of such a device. Once you have seen whats wrong in the Bedrock game client for Minecraft, you may head to 2:40 in the video to see what is correct in the Java edition. These errors have been explained with plenty of ignorance to be caused by changing programing languages, however in mathematics there are many ways to come to the same solution, therefore the timing difference is not a result of such a thing as a change programing language as it is likely a result of rushing the work to program the red-stone for the bedrock edition. When it comes down to the issues related to the observer blocks in the summary, its likely a result of it probing too quickly or too slowly where it may or may not need reprogramming in order so that it might work properly (you can see whats wrong in the video as well with the observers). The observer is likely a result however of the difference in programming language but still may be a correctable magnitude of error.
Linked issues
Comments 7
You clearly did not read. Sorry to say such a thing but its true.
1. Open Minecraft (Bedrock game client)
2. Open Minecraft Java
3. place two pistons and a repeater to divide their red stone connections ( the steps are very simple and were shown in the video and highlighted in the description)) [do this in Java and bedrock game clients]
4. place lever and flip switch for level one repeater (both clients)
Observed result: zero time difference for the connection to the second piston in Bedrock game client while there is a time difference in the Java edition.
Expected result: Both time gaps would be identical in operation. (please note the only problem in the bedrock edition is that the time difference between the connections is incorrect)
5. Change repeater level to 2 for both editions
Observed result: Bedrock edition appears to be faster in comparison to the java edition which is running on level two
Expected result: Repeater in Bedrock edition would run on level 2
6. Change repeater level to 3 for both editions
Observed result: Bedrock edition appears to be running slower by small amount of time gap while java is running repeater level 3.
Expected result: Bedrock edition should should run on repeater level 3.
Observer Block
This issue does not have any one way to reaching the issue. As this problem is an issue in the probes which causes flying machines to work in the Java edition utilizing observer blocks but not to work in the Bedrock edition. My video of course also show this which was clearly ignored as all the facts including what I am saying in this comment have already been stated. PLEASE READ. THIS IS NOW TWICE I HAVE REPORTED THIS.
All issues are repeatable 100% of the time
Red stone is not working as intended as you can check out any other previous edition and see that red stone did work properly. It is not the result of changing the language Minecraft is programed in as many have claimed, but instead a result of rushing red stone when this was Minecraft pocket edition. I am a mechanical Engineering student so do not expect me to constantly reply. This reopening is mainly to help others who do not know any better as most of the audience for Minecraft have no idea this is fixable.
Hi @unknown. Please keep reports limited to reporting one issue per ticket. I've resolved your report as duplicates of MCPE-15793 and MCPE-16371. (I suggest looking into PID when talking about line riders and analog sensors). Have a look at our bug tracker guidelines linked below.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
@[Mod] KillerbeeNL Thank you, I get what your saying with PID however it does not exhibit any challenge and is more of a correctional device than the heart of the machine. Thanks for recognizing the duplicate, I think the result of looking at that ticket though shows even more problems which means I do not really think the second problem needs any reporting since the methodology of how redstone was programed was likely wrong to begin with in this edition of the game. Likely a complete redo is needed in order to fix the fact that redstone dust ticks are not connected as shown in the other report which is a huge issue as the redstone dust determines timing for all contraptions.
It is generally known that redstone between Java and Bedrock does not behave identically. Many devices in JE rely on "quasi connectivity", which is never expected to be added to Bedrock. There are also various timing differences, ticking order differences, etc. Most of these are not considered to be "valid" bugs, because parity differences between Java and Bedrock are not tracked unless the behavior difference was introduced in the "Buzzy Bees" update or later.
There are many online tutorials for devices, such as flying machines, for Bedrock, so I would recommend trying one of those out. You might also visit one of the technical bedrock communities, such as "TechRock" on Discord.
[This appears to be ongoing in version 1.19.7 where the first level of the repeater still opens the piston at the same time as when no repeater is present... Not supposed to happen! (also I'm an idiot and forgot this is duplicate and also reported in 15793] I happened to just be going through the reporting's, and it looks like there is issues currently with comparators on MCPE-15793. It would be a good Idea to up the level of importance in fixing that and this error in Redstone programming at least in my opinion. The fact it is not working so far from when this was the Pocket Edition is absolutely extremely controversial. Viewing the issues in timing presently, it appears to cause pistons in some Redstone machines to create a variable if not random output doing something different every time. I often find myself if playing the Bedrock edition placing the repeater levels at level 3 to slow the flow down enough that the output of a Minecraft designed circuit (in bedrock, works fine in Java) is not randomized by the timing the other end of red stone reaches its desirable destination. If you can understand me, the issue is a race with time, where the timing outputs of the repeaters in Bedrock are so fast that they can reach their destinations in a way that the output could result in a random number instead of the desired outcome (key: the numbers are in Booleans). In other words, Since PE the Red Stone has been so buggy that you can use it as a random number generator. I went through some of the comments here, and it appears there are some bad practices in reports of dated issues like this one. The fact is that the desired outcome of the Redstone current is not what is happening in fact. Hence you have a bug, sad to say, that has existed for many years and is yet to be resolved.
A bug report should have enough information by itself to understand how to reproduce the issue. Videos can be helpful in understanding, but the steps need to be in the report.
Please clarify the Description section above, using this format:
Steps to Reproduce:
1. (list every step exactly, so someone else can reproduce the issue, and try following your list to make sure you can still reproduce the issue yourself)
2.
3.
Observed Results:
(briefly describe what actually happens, including exact message(s) shown)
Expected Results:
(briefly describe what should happen)
(add screenshots or video to help explain the issue)
This report has been temporarily closed as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
You may find this Report Creation Form helpful for any future reports you create.
Please also limit the report to the specific information needed to reproduce the bug.