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! Items in snapshots and betas are subject to change so please be sure to only post about things that are currently released in Minecraft. Please read the intro post before you post!

665

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

under review

73 Comments

Post a new comment:

Please sign in to leave a comment.

Sorted by oldest
  • 3
    Registered User commented
    Comment actions Permalink

    What would make more sense (and please everyone) is a toggleable gamerule on the world settings to turn it on or off. I'm not a fan of QS but it is something people want so I can see why it's important. Also because its omission results in Bedrock redstone being mocked unfairly

  • 2
    Registered User commented
    Comment actions Permalink

    Please don’t add this. It would totally ruin all the enjoyment of redstone in BE, and would make me quit Minecraft 

  • 2
    Registered User commented
    Comment actions Permalink

    I see a lot of yes and a lot of no in the comment section. Everyone seems really split on this idea due to the fact that it can either make or break their pre-existing redstone contraptions. I for one have had experiences in which I had redstone that needed features and bugs such as these, and now can't use the machine because I converted to the world to bedrock. It's important that we make sure the community can agree on this topic, so why not just have both? I don't know a lot about how hard it would be to implement, but I think these features should be a world option (maybe even a game rule?) in which you can toggle back and forth before getting back on your world. There could be an option such as, "Java Redstone" and another that says, "Bedrock Redstone", with explanations of course, for example: "Java Redstone is the older and more classic way in which you can..." and "Bedrock Redstone is the new and improved smoother redstone, in which you can..." With this, I feel everyone would be able to make redstone contraptions the way in which they please.

  • 1
    Registered User commented
    Comment actions Permalink

    No. No most of my builds won't work anymore. 

  • 2
    Registered User commented
    Comment actions Permalink

    I super disagree, Most of the features requiring quasi connectivity are caused by shortcomings in the Java redstone systems, like not being able to bring redstone down transparent blocks, or how pistons break redstone dust on opening, or comparators being unable to read containers through pistons, or how redstone dust doesn't redirect towards nearby pistons, to name a few.

    Besides this, quasi connectivity does not make sense because there's no "connection." This would just make it more confusing for new players. IF quasi connectivity is to be added, there are three specific requirements that need to happen in my opinion:

    1. Separate redstone hitboxes are displayed to the player when placing. Ideally normal pistons won't gain this feature.
    2. Pistons with quasi connectiviy should be a separate block from normal pistons, and should be visually distinct and have a separate crafting recipe, Like replacing cobblestone with quartz in the crafting table.
    3. The awful block update system isn't ported. If something isn't powered, it shouldn't be powered. If it is powered, I shouldn't need another block to make it work.
  • 2
    Registered User commented
    Comment actions Permalink

    Maybe there could be a setting called "advanced redstone" in settings which would default to on, but if it was off the redstone would go back to old redstone so that your builds don't completely break.  

  • 3
    Registered User commented
    Comment actions Permalink

    not only it will spread ideas we (in bedrock edition) could use all the auto farms tutorials that on youtube that we currnetly can't use because the diffrent redstone mechanics

  • 2
    Registered User commented
    Comment actions Permalink

    Would it work if instead of quasi-connectivity existing/not existing, the entire behaviour was moved to a separate redstone component?

  • 1
    Registered User commented
    Comment actions Permalink

    Yes we need quasi connectivity in Bedrock because as a result it will make redstone more predictable and easier to understand after you get a grasp on quasi connectivity.

  • 2
    Registered User commented
    Comment actions Permalink

    Maybe this could be a setting in world settings, so that you could build stuff with the new features but be able to turn it off to not break existing creations.  

  • 1
    Registered User commented
    Comment actions Permalink

    There could probably be a ui to toggle quasi connectivity on a piston

  • 1
    Registered User commented
    Comment actions Permalink

    Or remove this things in Java Edition

  • 0
    Registered User commented
    Comment actions Permalink

    This idea is not possible because minecraft java circuits are too complex and those have been around for a long time, just like in bedrock, those circuits have been around for a long time, and changing everything to be the same in bedrock and java is impossible anymore that there is already the way that redstone works in these editions, and maybe some worlds that use large and complex redstone circuits, these can stop working, not only that, but the whole community has learned the operation of the redstone in bedrock and java and they would have to relearn how redstone works, which could lead to community discontent.