X

NOTICE

Are you sure you want to report this?

What is parity? This category is designed just for features that exist but work one way on one platform, and another way on a different platform. Bugs are not parity! Please read the intro post before you post!

304

(Java Parity) Return Quasi-Connectivity! | BUD | Etho Switch

under review

44 Comments

Post a new comment:

Please sign in to leave a comment.

  • 0
    Perstein2874 commented
    Comment actions Permalink

    Maybe put this feature into the game behind the experimental toggle

  • 0
    LegitUserPels commented
    Comment actions Permalink

    How about making it an optional feature. You'll be able to chose what type of mechanic you want. It will be like enabling and disabling command block functions.

  • 0
    Comment actions Permalink

    Simple solution: accept that it's a bug and move on.

    If you love it so much, keep playing Java Edition. 

    If you want to play on Bedrock, actually learn to play Bedrock.

    Stop bugging the developers to add something they  never meant to add.

  • 0
    sirdaniel0 commented
    Comment actions Permalink

    Please dont add! This will make redstone so much more complicated! Us bedrock only users will have to re-learn redstone! Come on Mojang! Please don’t add!

  • 0
    Hario337 commented
    Comment actions Permalink

    I think they should add a version of redstone that works the way it does on java now, but requiring more resources to make.

    it would be nice to have both at the same time for both platforms.

  • 0
    Rinni Parker commented
    Comment actions Permalink

    You know what interests me the most. Before we had block update detectors we used to do this thing with Redstone Ore,, You cause an update near it and it does and animation. Wouldn't it be amazing if - say - putting a redstone signal into a redstone-ore block and All redstone within two blocks resonates with a 1RF signal until the redstone signal was removed.

    In that way the other half of quazi connectivity could be implemented in a way that doesn't have to apply to every single block in the game. Of course that's just me riffing ideas.

    You should hear my ideas about pistons that spit out blocks and one-tick pulses.

  • 0
    Comment actions Permalink

    Please, no...
    Bedrock redstone actually makes more sense to starters
    and plus, Bedrock redstoners are gonna get REALLY annoyed if this actually happens.
    The only reason why Java redstone is still the way it is is because Java redstoners would get angry if Mojang changed it.

  • 0
    Light1Knight1 commented
    Comment actions Permalink

    To be honest I don't really use the QC feature much. I only use it for pulse shorteners and Jeb doors. observers can be used as a pulse shortener but they require there own work around because they give out two pulses, instead of just one. Mumbo Jumbo pointed out that red stone on the bedrock edition is unpredictable, and you can get varied results with a build. this isn't good at all if your'e trying to build fast compact contraptions. also sticky pistons can't "spit out there block" with a one tick pulse, making toggleable switches from a red stone pulse much more expensive, complicated, and big. so even though you could theatrically build more "compact" designs with out QC; with all of these problems on the bedrock edition of minecraft, you can say good buy to all of the fast compact space saving red stone. 

     

  • 0
    Comment actions Permalink

    I don't envy Mojang trying to figure out how to square this circle. QC is confusing and annoying but also incredibly useful and powerful. There are some things that you can't do in Java because QC exists, and some things you can't do in Bedrock because it doesn't.

    Adding QC to Bedrock would cause a lot of confusion and frustration, and break a lot of existing builds.

    Removing QC from Java would cause a lot of confusion and frustration, and break a lot of existing builds.

    Keeping things the way they are ALSO causes a lot of confusion and frustration, and breaks people's builds if they're building from tutorials for the wrong edition.

    I don't know how to reconcile the conflicting requirements into a best-of-both-worlds solution, but between Mojang and the technical Minecraft community there are a lot of really smart people, and I really hope they can find one!

  • 0
    Comment actions Permalink

    honestly id rather java get rid of this feature since its technically a bug. And these bugs are the things that keep me from learning how to use redstone. That being said bedrocks redstone is random which is another problem

  • 0
    SS12Fluffy commented
    Comment actions Permalink

    Quasi-Connectivity is an actual feature and "works as intended" as stated by Mojang themselves in the patch notes for Java.  Yes, it would break some redstone machines on Bedrock, and there are work arounds for some situations.  However, if they want the two versions to be more like each other, they should incorporate this feature on Bedrock sooner than later.  Otherwise the gap between the two versions, in terms of redstone builds, will continue to grow due to people sticking more with the version they prefer.  As for the people that want it to just be removed from Java, Mojang tried that before and had massive backlash for it, so I don't see them removing it at all.

  • 0
    Comment actions Permalink

    quasi.connetivity is just a bug that wanst removed frome the game because players loved it, but when the redstone was added to bedrock in alpha 0.13 a developer said that quasi-connectivity wont exist on MCPE because is a bug and to be honest if is added will destroy some redstone contraptions we have now

  • 0
    SS12Fluffy commented
    Comment actions Permalink

    Yes, it WAS a bug.  However, it turned into a feature due to Mojang noticing that it was causing more good than harm.  It was removed in a snapshot, which is what worried a large amount of the community (along with another issue that is present on Bedrock and will go to the correct thread to address), although was an accident in the coding that caused it to break was fixed to how it was prior to the snapshot.  Added on, Mojang stated themselves they will NOT remove QC (quasi-connectivity) from Java.  Also, don't know where (and yes I did look for a good ten minutes to try and find anything relating to it) this dev said that there would be no QC for MCPE almost five years ago, but you have to consider that was five years ago and could have been either a former dev or the company that ports it over.  If Mojang does want to eventually have Java and Bedrock players experience the same game, they would still have to result to adding QC to Bedrock.  After all, Java had the feature in the game prior to Bedrock/MCPE Alpha 0.5.0 being released.

  • 0
    LizibethVeir commented
    Comment actions Permalink

    small thing is the fact that some of the bedrock quirks i actually would have in java too, oddly enough.