As one smart redditor once said Java edition redstone is like 2 + 2 = 5 Bedrock redstone is like 2 + 2 = 4, sometimes 2 and sometimes 7

I was actually confused about QC until you said they copied the door. Now everything makes sense 😂

what makes this worse is there was nothing stopping them making Redstone act the same on bedrock during development because there's already an identical system they could have worked from in c++ on the original console versions of the game Redstone acts identically to java and is written in c++

Java player on steam deck here. This is the exact reason I had to stop playing Bedrock. It was just not predictable at all, and as Mumbo said, "Redstone is a logic-based system". Random is not logic and logic is not random. If your logic system is random, it is not logic. It is chaos.

As a bedrock main myself, I can fully agree with this statement.

Bedrock is better for beginners, the problem with being better for beginners is that you can do less. Java may be harder to learn but the skill ceiling is enormous

The language isn't the problem, it's the structure you make with it. It's not impossible for parity between languages, they just didn't for some reason.

As someone who started out with bedrock redstone and is transitioning to Java, I can safely say that Java redstone is miles ahead of what bedrock has

Also, this video actually made me understand how QC works. Pistons have the hitbox of a door.

Me: This doesn’t seem so bad. Purplers: Observers don’t detect noteblocks. Me: bro what

i have always thought QC was very strange...but this is the first i have ever heard WHY it works the way it does...and now it makes perfect sense.

You wouldn’t need to rewrite all of the C++ code to use Java-like redstone, legacy console edition has VERY similar behavior to Java edition; I made a Java edition 3x3 piston door and to make it work in legacy console edition required basically just one extra repeater.

It’s also true that a lot of the positives you mentioned with Bedrock redstone can be modded to Java minecraft without sacrificing any of the good things in Java minecraft.

Real Bedrock players will never feel offended by this video, this is the purest form of truth regarding the bedrock and Java differences. You're tha man.

I only have bedrock and I agree completely. The fact pistons aren’t deterministic stops me from making so many contraptions that I lose mot8vation

Also if you don’t mind modding, you can add those nice bedrock features to Java, like movable tile entities and redstone on glass etc.

as an ex-bedrock redstoner, i always thought the biggest advantage it had over java redstone was being more intuitive, because QC was very difficult to understand for redstone beginners. i even thought that redstone inconsistency made sense as it highlights ambiguous redstone wiring. only today, 2 years later after leaving bedrock redstone, did i learn about certain bedrock redstone components only updating/powering on odd or even ticks (the observer + rail clock example). i had a flashback of a time when messing around with observers and repeaters having unusual behaviour. i thought that observers were simply slower, just like pistons. this is true, but not for the simple reason i thought. i hope this video convinces everyone that bedrock redstone is really bad, because i know i would have been convinced more than 2 years ago. thanks for this video!

the thing is, you can add all the benefits of bedrock redstone to java through mods with none of the drawbacks, but not the other way around

As a redstoner who mainly plays on bedrock this is very eye opening thanks

It means alot larger structures are needed due to lacking QC and you need to add more repeaters in a different tick state to force the correct execution of update orders.

As a Bedrock redstoner, I admire the courage to make this video lol. I’m a big fan of yours, and even though the redstone works differently I still learn a lot of stuff about redstone from KZfaqrs like you. Thank you for making these videos!

As a technical-ish Bedrock player, this is very accurate and I'm impressed with the research that went into this, especially with the c- and p-ticks (the different redstone components activating on different gameticks)! Just a few things to note: - Bedrock does have update order, but for pistons it is randomised because they're special - The mod you showcased in the video (Trapdoor) is a server-side plugin; "mods" do exist where the exe file is modified Great video!

Years ago, I switched from bedrock (PE back then) to Java and never looked back. The only thing I miss about Pocket Edition is that you had moveable tile entities. Allows for some fun hidden traps.

playing bedrock is like punishing yourself. if u were given a choice between two cars for free, a ferrari and a toyota, and picking the toyota, is like minecraft fans picking bedrock when the ferrari is the obvious choice

As a Bedrock player, you explained to me more clearly what actually is the difference between the redstone of the two editions and now understand why hey say Java redstone is better.

As a bedrock user I think the majority of people who do redstone there would like java redstone, me included. As you mentioned, it simply has more possibilities for redstone capability

As a bedrock redstoner, I test my machines 4 times to make sure they work properly.

I've been using a binary counter in my current survival world that makes use of QC. I built it by following a tutorial because I simply needed smth that worked - this video saying "Pistons think they're doors" suddenly made everythign about this machine click for me. It works by quasi powering pistons to push redstone blocks under other pistons, that push blocks onto the quasi powered pistons, allowing for a signal to go through that block the next time a pulse comes through, quasi powering the next piston in the line. I could never have intuited how this works, but now that I know that pistons think they're doors, I can actually use this info to maybe make some of my own stuff. I feel so much smarter about redstone for simply understanding a glitch that was changed to be a feature!

This is why I respect bedrock redstone creators bc they still manage to make insane builds while being super limited. Im a intermediate bedrock redstone user and it works for me even tho it's objectively terrible

My main problem with pistons in Bedrock is that they don't always activate when they're supposed to. I'm trying to build a castle gate, but I have to spam the button to make all of them go. Sometimes one press activates all of them, sometimes I have to press the button 50+ times

If only we could combine the two redstones. I know Java redstoners would like movable furnaces/dispensers, and bedrock redstoners would like to have noteblocks activate observers. Just keep your quasi-connectivity magic on your side of the fence 😂

I remember designing a 3x3 flush piston door in bedrock and had the worst time with piston retraction order. The door would frequently break because I was powering multiple pistons at the same time, but wasn’t able to find a way to make the redstone compact enough to find any other solution.

QC Makes like 15x more sense when you find out how it came to be, and what's nice about it is it actually introduces uses to a lot of blocks in redstone purely for giving updates to the piston in different ways.

The door explanation for QC is actually incredibly helpful. Than’ you

1:10 and now they remove the 1 tick redstone lamp and crafter because it’s a “bug” even though that’s what people liked about them

Old Minecraft devs: oh oops pistons think they're doors. Wait that's useful? Fine, enjoy! New Minecraft devs: Oh the copper lamp takes a tick to update? NUKE IT, FUCK THE UTILITY

The mod aspect is not just redstone-related, it's a huge point for Java in the overall competition.

Great video highlighting some of the reasons I eventually moved over to java edition, and I love how you thought about the nuance of the topic, instead of just straight up ranting which a lot of people have already done. I'm so glad I got to help with the proofreading for this! (I'm voidredstone, btw. I changed my name :3)

As a bedrock player, I would NOT be mad if mojang rewrote the code to be like Java

There are two culprits for this Bedrock system being like this. Firstly the Devs, which are not the same as the Java Edition, and secondly the pairing with cell phones. This version's chunk simulation is very strange, it doesn't update like in Java, which is due to the exact distance from the player's position. It updates by exact chunks, always starting from the next one where the player is located, regardless of whether he's on the edge or in the middle. This helps with performance and optimization, but ends up causing these differences and other issues. Like the fact that this forces players to always build redstone in the middle of chunks so they don't break. And this is one of the reasons why I hate zero tick farms, they are noisy, break easily and cause a lot of server lag. And unfortunately for me, they are the ones that the community shares the most on the internet.

Incidentally, the bedrock perks could very easily be added to java; (Except maybe the glass.) But multiple mods have been made to waterproof redstone over the years. And still more mods add in moveable tile entities. And for anyone who says bedrock is superior to java because of performance: at least in java you won't fall through the world if you go out too far. Also, saying pistons act like doors would really clear up QC for beginners.

As a bedrock player, I like the more realistic and intuitive areas of bedrock, but the randomness and slowness makes traps large, over complicated and usually easy to spot.

I feel like a good solution to Pistons is adding a new variant to both that acts as it counter part, thus adding java pistons to bedrock and bedrock pistons to java.

Does anyone know what he's using to cause the observer at 2:39 to have a update animation?

I knew bedrock redstone was bad (as i already hated how sluggish the piston is), but then I learned about the fact the some redstone only activates every other tick. Then I remembered that there's no priority on redstone, the game would just choose a random block to update first. I cannot remember how many times my redstone would fail because of that one difference, it truly was painful.

As a bedrock Redstoner, this video didn't anger me, instead, it made me want Java Redstone more in bedrock. One of the major reasons is the Redstone timing and piston push time.

That's why I always wanted to be in trouble so I could do complicated Redstone now that I'm more advanced.

I think it would be really nice to have parity. The problem has always been that Minecraft should be coded like bedrock (in C++ for the performance and cross-platform capabilities), but should work like Java (with all the janky determinism).

As a bedrock player who tried to make a sugar cane farm without checking a guide, a simple sugar cane farm, I can agree with everything here

I'm glad I'm on Java, although I'm pretty noob in Redstone some of the simple interactions seem bothersome even for "casuals", and QC makes sense after the simple explanation, knowing that it is detected like a door for two blocks makes it obvious and probably will be very helpful with Redstone.

DUDE. I NEVER knew about this "QC" nonsense. Now that I know this, I have to try it out! I've always wondered how the Wizards of Redstone (TM) were able to make such massively complex machines in such a small space and why my redstone always sucks. This discovery to me feels like the discovery of the wheel, or fire, for mankind. Everything is open to me now, I UNDERSTAND. Nobody ever seems to talk about it or mention it. It's why I've never known how redstone fully works for the entire past 15 years playing the game.

thank you for this video i thought i was dumb while trying to do redstone on bedrock and having pistons just do what they wanted especially trying to make a flying machine that didn't break i got it to fly the first time and i guess i just got god rng

Disclaimer: excuse my inconsistent grammar. I'm rushing. I have played both versions for a few years now (and coincidentally programmed in both languages), and I definitely see where this all comes from. For me, it is bedrock's unreliability vs java's bugs gone features. The problem is that the main bedrock redstone hate is from its lack of these bugs gone features. Mostly this is QC of course. There is also block spitting, which to me is completely unintuitive (useful as it may be), and I still don't know whether or not this is and/or was intended. Outside of piston doors, I don't have a lot to say. Movable tile entities are useful everywhere, and both versions have pros and cons in storage tech (I never really delve into that so I can't say anything really). Outside of that, I don't think there are any notable differences. Actually, there is that side (that I personally hate) of computational redstone that uses pistons/observers everywhere where QC causes pain and block spitting brings healing. I will always stick to classic (ie. dust, repeaters, comparators). Piston doors are the main source of the debate. For fast doors, java is all centred around 0-ticks, which I am fairly bad in but they seem fairly repetitive to me. But I admire everyone who faces the challenge of making compact 0-tick doors, which I consider the most challenging piston door field. Bedrock's fast doors really come down to layouts. After that it's just timings, which I tend to struggle to keep motivation for. Aside from layouts, they are really the same as just compact doors, but all about the pain of timings. Bringing me on to compact doors. Controversial opinion time: At a world-record level, in this day and age, I believe it is more challenging and fulfilling to work on compact doors in Bedrock. Soft inversion is the cherry on top, always motivating you to go layout-size on the bottom. (Cherry on bottom?) Lack of QC/spitting, and all the timing inconsistency, make smallest possible a lot larger in bedrock than java. Don't get me wrong, I admire the cyclers, observer-spammers, hopper ROMmers of the java world. And my utmost respect for the obsless sweats knowing the ins and outs of every entity in the game (I think entity usage is something missed from this video, more on that shortly). But simply because progression is nowhere near the level of Java in bedrock, I find it more fun and more constantly interesting wiring small (relatively) doors on bedrock. Everything has not been done already. Quick note about the entities, I rarely use them tbh. But in bedrock it seems to be armour stands and striders in minecarts (there's some tff with 6 striders or smth idek). Then I go to Java and I've angered an enderman in a boat clipped into sand held up by 4 furnace minecarts clipped into hoppers in a dh system with 20 chest/hopper minecarts. And a chicken pod for extra scenery. I think I got my point across. ... Example Take an example, I recently cracked the key to a 4-wide 7x7 vault door in bedrock. A similar example in java is the 1-wide cycle doors of late (most notably the 5x5). What's the difference? That same cycle concept can be scaled up intuitively and without a massive amount of difficulty (that will come smallest possible attempt). But the 4-wide 7x7 vault concept I have works only for that size, no 8x8s happening yet. This constant required innovation is what makes bedrock compaction ultimately more fun for me. TL;DR Intro: I am unbiased, with years of simultaneous experience in both editions. Bedrock has unreliability, Java has QC and block spitting (which I find completely unintuitive). MTEs are amazing. Everything outside pistons and observers is largely unaffected (eg. classic computational which is almost edition-proof). Fast doors: Java => 0-ticks => kinda repetitive => unwire-able layouts aren't repetitive => but they're unwire-able. Compact 0-ticks => most challenging piston door type IMO => mad respect. Bedrock => only really layouts => after that just compact doors with pain timings => pretty boring => motivation STRUGGLES. Small doors: record-level, current knowledge => Bedrock more challenging/fulfilling => even though smallest possible is bigger => controversial I know. Bottom layout size => pretty much needs intricate soft inversion => tricky and fun. Bedrock has less layout progression (and just general) => (see the example). Finally, obsless+entityful sweats are crazy people with triple my iq and knowledge capacity. Thank you for listening to my TED talk.

By the way, they can do the same thing despite all of that. Even if they have multiple threads or a separate programming language, it can still lead to at least a very similar result. There's really nothing stopping them, because fundamentally C++ and Java can do the exact same goal but in different methods, even with multiple threads (which one can still handle things the same way by the rate it should update).

6:12 Man, I get the point of the video and agree 100%, but did you _really_ have to give me such an insane rush of nostalgia? 😂 God, playing Tumble with friends with a big-screen projector on the PS3, all in the warmth of my home on a cold winter's day during the break... Man, how I wish I could go back and forget everything, even if just for a day...

I actually never heard the term "quasi-connectivity" until recently. I just called that phenomenon "BUD power"

Use to play Java but permanently switched to bedrock and I 100% agree with all of this. I feel like the changes were made for lag purposes on mobile devices but bedrock runs on C++ one of the most robust and fastest languages (because it’s compiled) they could get parity if they had a dev cycle focusing specifically on this parity sadly I don’t think the community has made enough fuss about it. I would love to see a parity redstone update where Java gets movable entities etc. and bedrock fixes these issues.

The main/only pro of Bedrock, moveable tile blocks, is possible in Java simply by using Carpet mod.

Well now my younger self can finally rest in peace. Always thought that the red stone machines I tried to make from KZfaq videos, Java videos, broke because I did something wrong and was always my fault. Man. So much agony now gone. Thanks for the video and for giving me clarity.

I learned about redstone stuff and was so excited to make contraptions and builds, but I'm stuckwith bedrock. I cant even make a redstone door without spending a couple hours just to find out that half of the pistons I'm using can't get powered because of the lack of, if I remember right, QC? Because of how bedrock redstone works I can't make what I want to make and that kinda ruins my playthroughs.

I can't imagine life without buds and qc in java redstone.

"we havent implemented bundles yet because of parity with other platforms, and strive to implement parity with other platforms and versions of minecraft" "Ok, what about moveable tile entities for java and QC for bedrock?" "oh wow look at this giraffe we just made, neat isnt it?"

I play on bedrock and I put a bunch of random pistons together with a clock, the result was a random signal at the end of the system. I used this to make a randomly flickering light. This video taught me that was because it doesn’t have an update order, so I unintentionally found a (very loud and complicated) use for this lol

i started redstone in xbox 360, with a simmilar redstone to java, when i went to bedrock edition i was like: *what?*. now i have java and bedrock but i keep using bedrock because it is smoothier, well, both redstones are good

That answered so many questions and weird moments in old redstone builds thank you for this video I'm pretty sure I'm gonna watch this a couple dozens more times in the future if I get a redstone problem again

Good job having properly researched for this video; I don't mind Bedrock redstone being called out, but when it's done it has to be done right :p Sadly it gets even worse since this is only about intended behavior, the game is riddled with countless bugs that ruin redstone even further (for example, powered dust triggers observers on relog, hoppers have trouble picking up items when they aren't all of the same type, hopper pickup range is bad, pistons moving blocks cause horrible memory leaks...) P.S. I haven't played MC in a long time so some of these bugs may already be fixed, but BE devs are so horrendously slow and unresponsive when it comes to these game breaking bugs that I don't expect any of them to be fixed within the next 5 years

One thing they could do to make both sides just a little bit happier and have (somewhat parity) is remove QC in java BUT add something that allows you to place something ontop of a piston which it will then merge are still have 1 block of collision but but it act like it has a height of two so not only can it give more options it makes sense to newer players and makes it so you can visually see the blocks being connected to the top area. something similar could done for the piston where by default it pushed when a block opens but something could be added to it which then makes it wait for a block update instead

I'll give up quasi connectivity for pushable chests any day. I was able to move an entire base storage room a thousand blocks away in only a couple of hours VS having to transport them all with shulkers and a minecart track.

bedrock redstone works great after you buy a 30$ texture pack and a skin

Wow, this went way deeping than I thought it would go. Great video

I, a Java player, once tried to make a t-flip-flop on bedrock. Sticky pistons don't spit out blocks on bedrock. I tried the 2 pistons with a redstone block in the middle and because of random order in bedrock, sometimes it would behave like I want and sometimes it won't. Same thing with 2 droppers. Took me over an hour to do something in bedrock that I can do in less than 5 minutes in java.

As someone who plays bedrock update order would be such a god send! I've tried to make flying machines so many times and wondered wtf is making the machine update the way it does. Drives me batty.

The only positive with bedrock redstone is that the piston arm looks cooler And this barely changes anything

I just had a weird idea on how redstone pairity could possibly be achieved without making anyone mad... at the cost of doubling the amount of redstone items. My idea is to make "reinforced" redstone components, these would act exactly like bedrock components (upsides AND downsides alike) and would replace the normal redstone components in bedrock worlds, with normal redstone items acting the same as in Java edition. Pros: More redstone components. No contraptions would be broken by this in particular. Older redstone tutorials would still be valid. No need to get used to new weirdness if you don't want to. Cons: More redstone components. Different crafting recipes required. New weird interactions (probably). More textures. Less intuitive overall. Edit1: fixed an error I made and cleared things up a bit (hopefully)

That quasi connectivity explanation is brilliant, I have been trying to wrap my head around it for a while now but that makes so much sense.

I genuinely forgot this and more redstone tricks were bugs and tried building some machines in bedrock, and spent two hours trying to diagnose shit before I realized "oh right, that's a bug, they don't have that bug here".

My bedrock experience: - Opens bedrock - Builds a 1-tick piston monostable - Sticky piston doesn't spit out the block - Monostable doesn't event output 1 tick - Uninstalls

Before you bought both versions together, what settled me getting java was the redstone. I'm not even very into redstone.

In my opinion I think there should be a mix in between bedrock and java where you can move blocks like chests and furnaces but you can also have 0 tick pistons but it works on mobile and pcs and any other device that can play minecraft. It would be so much better but its an unobtainable dream 😫

I was wondering why my red stone skills disappeared when I switched to bedrock

Hey purplers! I am trying to start doing redstone and so far i have been having a blast, but today you touched on the importance of mods and i got wondering which ones can help me. Do you plan on doing any sort of video/post on what mods and texturepacks you are using?

honestly, i think that if mojang would do a massive redstone overhaul once, i'd want it so some features like quazi connectivety be a gamerule option, yet have things like the glass moving redstone downwards, or movable tile-entity's, also be a feature. so basically any features the versions have that differ from eachother making the contraption break be gamerule options, yet the features that could break some redstone that are completely avoidable not.

I have created designs in Bedrock that rival the best designs in Java and even exceed them. Once you start messing with things you realize how deep it goes. Intead of an item sorter that groups items then sends them to this long hallway of hoppers at double or quad speed. You move the chests themselves. The sorting is the chests themselves. You move each individual chest from a group of chests underneath using bouncing sand to move the chest in 4 ticks, fill it, then it automatically moves the chest back to the location in 4 ticks. Since items can be moved near instantly through a line of sand on pistons, this also applies to chests full of items. No hoppers, no waiting, no sorting with hoppers. Simply input what chest you want by droping one of the item in the chest and the chest moves to you. Once loaded the chest automatically moves back to its location. Impossible in Java

Im surprised you didn't mention the chunk problem. I'm not sure if it's still an issue, but if your redstone build isn't inside a single chunk, it becomes even more inconsistent.

6:26 I also tried something with redstone. I actually wanted to have lamps that retract into the ceiling. I had to try so much more than I would have to try in Java because it always broke because there is no update order. That was so frustrating that I just don't want to build all my redstone circuits so cool anymore and just built everything more quite boring😢

All redstone things that are better in bedrock can be added to java, but great things from java cant be added to bedrock... I think I see winner here!

if they fixed the activation order, I'd tend to think that wouldn't break anything except for randomizers that intentionally use the randomness. I wish they'd just go back on what they said and have parity for both activation order and tick speed. I don't need QC if I have those two things.

1:10 bro, you used the mettatron ex fight music, and i just so had undertale open in the backgroung WHILE BEING ON THE CHAT SCREEN BEFORE THE FIGHT, so i thought the fight strarted(bruh)

As a smaller Java redstone KZfaqr, You are my hero for making this video.

5:49 that's why flying machines in Bedrock Edition move randomly, there is no update order

I started out yesrs ago on bedrock and only been play6for a few years now on java and I was so confus6ehy I couldn't figure out java redstone but this video really resolved those confusions. Such as the non deterministic concepts. Like try fo figure out that thinking error. Expecting always a different outcome while in reality it's all nice and organised

I'm in the same boat as you, but with bedrock. I'm so used to bedrock that I could never get used to java. I really wish more KZfaqrs would focus on bedrock Redstone

9:11 no bedrock player would be mad every bedrock player would be happy

And the feature that I'm most jealous of is, of course, the fact that some Bedrock blocks can be waterlogged with *flowing* water. Why can't we have that in Java? (and while we're at it, lavalogging would be really cool too)

Hi to all! Does anyone know the name of the game: One room with a table on which there are buttons, secrets, then levers appear. Above the table hangs a screen that shows how the player's actions affect the world. A horror puzzle game. Thank you!❤

oh god redstone users aren't the only ones that strugles of that version, as a beginner command block user i noticed that its extremely more difficult to make the simpliest stuffs in java, if i do it in bedrock is only beaceuse i dont have any pc/laptop devices at home so am stuck with my phone to do everything so it sucks, even tho it got some good things like extra commands that aren't in java but... it just all cuz when looking at the down sides we literally see that command blocks have literally a limited range where its active and the only way to make it active anywhere is by using tickingarea command wich has a limit of 10 uses for some reason (am not sure if java also have that problem but it didnt according to what i remember) and using command blocks in bedrock is so bad that it accualy good in an very important side of doing command_blocks wich is creativity cuz the fact that u should do 10 command blocks in a row instead of doing an 30 characters long command on java makes u think and solve problems wich is a nice way to make u better and once u will go for java u will have quite good bases for it

You can make pistons eject blocks in Bedrock. You just have to put the piston within 2 blocks of the top or bottom world limits.

I have been playing on Bedrock for my whole life, and this video explained pretty much all the problems I have ever encoutered with redstone. If I wasn't already subscribed, I would do it again! Thank you! P.S. , could you please do a video that debunks some redstone tutorials that claim to work on Bedrock but don't?

I play both java and bedrock and i get confused so easily on redstone builds between platforms

Jeez heck I'm a java player and I had _NO_ idea how bad redstoners on bedrock have it I had at least three complete "what the actual fuck" moments watching this