Correct! And you were the first :)

This was my guess as a bedrock player, which goes to show your explanation was perfect haha! X

Could you explain why 7 is being powered?

@@vannername8413the top most wool block gets powered by the redstone line, which powers the piston by qc then at nearly the same time the note block gets powered which updates the piston…

Congratulations

Acceptance

Very interesting!

maybe this is where the bug originated from? it makes sense that doors work that way, and maybe notch just used the same code for pistons.

@@zaptrap4802 Yes! This is indeed the most likely origin.

​@@zaptrap4802 it says that in the video lol

@@lilyofluck371 yeah i know i need to stop typing comments before actually watching the video

its not a "bug" its officially a bug, and Mojang DO NOT endorse it. It is VERY cheaty, not to mention it is a BISH to pair with Bedrock. (BTW, TNT-Dupers are a bug as well... the reason these "features" stay, is because children whine and complain that the BUG theyve been using WAS going to be REMOVED. BUT because these children SCREAMED AND WHINED over it, Mojang left it in. Check the ACTUAL history of this stuff, don't just blindly follow these idiots)

Wow, that's some very high praise 😳 Thank you, and that's exactly my goal - to provide quality redstone education and entertainment for beginners. I appreciate the support!

actually the phenomena was still called Quasi-connectivity (literally meaning false/pretend connectivity). QC is like the trampoline, "bud powering" is like the jumping. one's a "thing", the other is what you do *with* it. two sides of the same coin.

bedrock redstone has some neat piston mechanics like pistons redirecting redstone and pistons powering off redstone torches whenever the piston itself is powered by any means, but yes bedrock redstone has too much randomness and precise timing is basically not a thing. Certain redstone mechanics can even cause all other redstone to "lag" and effect the speeds, for example, take a torch clock (two torches on either side of a solid block, one redstone dust on the top of the block, and one solid block over each of the redstone torches) and then somehwere nearby but disconnected, make one of those observer clock lines (a line of observers facing into the one before it, and then at the side of the line with the exposed face, face one observer the opposite direction of all of them so that the output is facing away from the line but the face is facing the line) and see how the torch clock slows down significantly. It could theoretically be used for wireless redstone though, but idk exactly how

Bedrock redstone is perfectly fine. It's closer to what Mojang/Minecraft (what's in a name?) intend for redstone. Does it have flaws? Absolutely. But things like sticky pistons leaving behind blocks? Quasiconnectivity? Hell, even torches/buttons etc. breaking on pistons when fired... DOES NOT MAKE SENSE. Sure, once you understand WHY it happens.. the logic of "why" it happens makes sense, from a game perspective. But the reality of it is still rediculous, illogical and problem causing -- Go watch Tango debug Decked Out 2 and see how many times QC enraged him. Bedrock has its problems too, sure. But I have been building redstone on bedrock for about 5 years now... I went from noob to designing and building my own binary counter and decoder, with full functionality. Can run on a clock, manual input (individually turning on lights 1-8) or manual input (adding 1 e.g. 10101010 to 10101011, or 10101011 to 10101100, or w/e) "activate all" and reset lines... all accessible from a centralized control point. Bedrock is logical. If something doesn't work, there's a reason you can identify as to why it doesn't work. And it's almost never a bug. It is "intended" behaviour, unlike QC which is "accepted" behaviour. Soft inversion, for example, or just the ability to place things like buttons, torches etc. on pistons. Well, if you look at a piston when extended - especially on bedrock - the section where the torch, button, redstone w/e goes never actually moves. It doesn't make sense for it to break. But java can't do that. Or a whole bunch of other things. For the average, and majority of players... bedrock redstone is genuinely better. It's only for the people looking to push it to it's absolute limits - like that 16kb RAM minecraft computer guy - who "need" java redstone.

@@SupachargedGaming no you're wrong, java redstone has those quirks, but those quirks are always consistent. Bedrock redstone has randomness, it's hard to work with randomness. Doing the exact same thing twice can led to different results. In java that doesn't happen nearly as often, which is why I'd say java redstone is better in general even if it makes less sense at first

That's why I test my machines four times in bedrock to make sure they work

@@Trombonemusic765 good thing mojang made sure bedrock didn't have any icky mechanics like piston block spitting or bud powering and instead just made it randomized and unreliable

Yep, exactly right 👍

Interesting ideas

definitely better to add the "new" pistons, so aesthetic builds using pistons don't look worse

No, no, god no. Leave that garbage on Java please. Bedrock redstoner here, I DO NOT WANT TO DEAL WITH QC NONSENSE. THANK YOU VERY MUCH, GOOD DAY.

Glad I could help out :)

Thank you 🙏

Thanks!

Yay! Glad I could help

Glad you liked it!

Of course! Glad people are finding it useful :)

Glad it helped!

Maybe, if I can come up with a good way to implement it. Thanks for the suggestion!

Glad I could help :)

I suppose it could. Great idea!

Yes, I've used it to make very compact RAM

@@vibaj16 awesome

Do you mean the jeb door? (AKA the 2x2 flush piston door)

It's definitely a polarizing feature for some. But the huge majority of the redstone community clings to QC, and it is so deeply integrated into modern redstone that an unimaginable number of machines will be broken in one swoop if it was removed. Mojang has threatened several times in the past to remove it, but the pushback was so strong that they haven't considered it in years.

I'd say it opens up a lot more possibilities than it destroys. If you know what you're doing, it almost never ruins a project. Mojang should just add a variant of pistons (maybe using copper instead of iron) that doesn't have qc, so we get the best of both worlds

Are you serious, it allows you go achieve additional delays with sticky pistons.

The VERY fact it is Java only and will NEVER recieve parity in Bedrock, means this IS a bug, NOT a "feature". Be careful implementing this bug, as Mojang have been working at trying to phase it out, or Java itself, since it is a PAIN to work on TWO seperate versions of the SAME game, and Bedrock has THE most playerbase. So their PRIMARY focus, is making sure things work on Bedrock FIRST, before adding it to Java. If it dont work in Bedrock, it dont get added to Java. Kids like the videoOP havent ACTUALLY done the research to LEARN of these facts. Instead, willfully ignores them, likely because this is ALL he uses in his infantile (brokenAF(bugged)) contraptions

@@swizzamane8775 they will never remove it from Java though, they have a fix for it but the community would get so upset that they won’t implement it. Also bedrock redstone is more bugged and broken (in a bad way) than java rs. (It is non deterministic) the only good redstone features of bedrock is movable tile entities and comparators reading container signal strength through pistons

@@swizzamane8775 also the smarter move one mojang send would be to phase out bedrock edition and not java if they cared about how long time it takes to implement features

levers, buttons, redstone dust, redstone torches, and some other components update 2 blocks away, not just 1. Repeaters, comparators, observers, and some others update 1 block away, but also update 1 block away from the block they're pointing at

Actually, item ID based wireless redstone is the quantum entanglement of Minecraft.

@@Minty_Meeo and IID based transmutation is the quantum tunnelling of minecraft

Yes, your edit is 100% correct

yes

Yes! (1 included)

more like a D latch

Pistons don't transfer power like that. This is only a feature of solid blocks.

@@jazziiRed oh ok im sorry that makes sense

Notch dont head Mojang anymore. The current Devs expressed QC and TNT-Dupers ARE bugs. But you children whined and complained and THREATENED to LEAVE if was FIXED, they were FORCED to leave them in. Learn the ACTUAL history before you spout nonesense

@@swizzamane8775 Please learn English before you post another hate comment, please. Also what does "Not don't head Mojang anymore"? Did you mean that Markus Persson doesn't own Mojang anymore? "threatened to leave" lmao what? Mojang prolly wouldn't care since the only time they make money off minecraft is when you buy the game. Also calling everyone/random people "children/a child" is one of the most pathetic things ever. Also why are you talking about tnt dupers? This video is about quasi connectivity. 🤦‍♀️

@@swizzamane8775 *doesn't, nonsense!

@@_GhostMiner "threatened to leave" lmao what? yes. learn the history you moron. OVER HALF of you THREATENED to leave the game

@@_GhostMiner "Mojang prolly wouldn't care since the only time they make money off minecraft is when you buy the game." Who is Mojang ?? HMMMM!???!?!?

Not 2, but the rest are correct :)

Correct!

Correct!

Honestly I have no idea how the term itself came about. But this was very often called "BUD powering" back in the day.

@jazziiRed interesting I wonder why it changed? (Maybe it was the coolness haha)

​@@fomocomotion224 BUD described one possible use for the bug, while QC describes what it is a little bit better... A power source that is not directly but sorta connected to a mechanism.

I seem to recall Sethbling having coined the term, or at least popularizing it, but idk