When you are making your redstone suggestions, please note that Java and Bedrock will not have the exact same the same redstone systems - this would require redoing redstone system completely on one platform or the other. The two systems are functionally different and are going to stay that way. Please be sure to tag your suggestions with (Java) or (Bedrock).

72

Let's talk about Redstone! [Java Snapshot 24w33a]

Pinned

104 Comments

Please sign in to leave a comment.

Sorted by oldest
  • 1
    Registered User commented
    Comment actions Permalink

    So the wire is now way less laggy, why not use this opportunity to also buff its maximum range. With all the new items etc 15 (16 if u count 0) different signals is often not enough. Why not upgrade it to 64 so we can better translate the different signals to comparator outputs. You could cover each slot of a double chest with that (top 9 signals just mean completely full) and so many new records. You could also remove the weird overlaying on the scull sensor output. I don’t really see an downside to longer redstone signals, of course it’s gonna break some things but that’s already true so why not enable some new and cool behavior on the way.

    Also 64 is just an example you could also go even higher or maybe make it dynamic based on the source.

  • 2
    Registered User commented
    Comment actions Permalink

    All people here a so dramatic ^^

    Some good changes here, definitely the right direction, but I think the route cause is Block Updates and all the weird bugs we have come to use in general! I get that QC is very useful but even if u don’t consider it a bug it’s still bad Game Design! Just replace all that weird game design with blocks that allow the same or even better behavior like u did with the observer. For QC I could see a block that strongly powers 2 blocks infront of it a solution that also enables cool stuff. And for all the other weird bugs we have come to accept over the years there surely is a solution to that might also enable new behavior like the observer did.

  • 1
    Registered User commented
    Comment actions Permalink

    Randomness was eliminated in 24w34a, but that's not the only problem. The redstone update range should be restored to its original state. Looking at the comments here, it seems that there is a mod that makes redstone lighter while preventing the destruction of the device, so if you really want to make it lighter, I recommend you refer to that.

  • 0
    Registered User commented
    Comment actions Permalink

    From my perspective, as an experienced Bedrock edition redstone player, the Minecart changes are great, I have played with them some in the snapshots and I quite like them. The change to the Redstone Torch texture isn't something I had thought about or wanted before, but I do like the change, but I would prefer if the inside were a bright red, maybe with a little bit of white or orange and the outside were a slightly darker red. I think that would look better than the current version, the white inside looks a bit odd to me. The redstone dust changes don't relate to Bedrock edition as bedrock edition doesn't use block updates for its redstone system in the first place, one of the reasons it has randomness. The only bits of randomness in Bedrock redstone that are problematic for me are in cases where one piston is finishing movement at the same time that another one is starting movement. There is a feedback suggestion that would fix those cases for Bedrock edition that I support and have voted for: Pistons should finish moving blocks before other pistons start [bedrock] The complaints about the randomness in Java edition I find strange as those cases are very rare where that occurs.

  • 0
    Registered User commented
    Comment actions Permalink

    the randomthing is prety good ,but that other redstone dust thing brackes lot of farms and other machines

  • 0
    Registered User commented
    Comment actions Permalink

    I am a casual Redstoner and honestly I think that the current change is the a great step the randomness could be used for some interesting contraption and it makes more sense to the average player I'm not sure about the change to quasi connectivity, although any performance gain is great as minecraft needs it.

    -Java

  • 0
    Registered User commented
    Comment actions Permalink

    I fully support the experimental changes in 24w33a. I do not think you should pay too much attention to complaints about breaking hyper-technical play styles. The technical community has learnt to rely on glitchy behavior and understandably they really care about their discoveries and contraptions. But if you think about it, quasi connectivity and other weird behaviors are double-edged swords: they make some circuits possible and other impossible. The technical community will find other ways to accomplish what they do today and maybe more. Just consider the following: 

    - If you plan any other breaking redstone changes, implement them all now to avoid breaking things again in the near future and angering people.

    - Make sure you implement intended mechanics to replace unintended mechanics that are lost (including stacked TNT minecarts).

    - Randomness if good if intuitive (pistons facing each other) and allows new circuits.

    Redstone needs to have less unintuitive behavior for the sake of most players.

  • 0
    Registered User commented
    Comment actions Permalink

    The 'Only causing block updates on blocks that may receive power from the wire' change does way more harm than good and misses to adress the issue it's trying to solve.

    It is intended to reduce lag, but the only people that will get a performance benefit are those building large redstone contraptions, and those people are the ones that are the most upset about this change. Players not using redstone will not be affected by this change, so it doesn't make much sense following their feedback. The redstone community would much rather have redstone wire update all blocks as it used to be instead of rebuilding many contraptions to gain a tiny performance increase. Also, reconnect stuff that was previously connected and now isn't anymore, new redstone wire / observers / powered rails / target blocks will need to be placed, lowering the gained performance. 

    Furthermore, if you cause a block update manually / by some other means to something that now no longer updates through the redstone wire, it will still update. This seems rather confusing to me and doesn't fit in with the other major change of this redstone adjustment, the update order, which is meant to make things more simple and easy to use and is well accepted by the community.

    Speaking of the update order randomness in redstone is very undesirable and it would make much more sense to always have a consistent output (for example based on direction as it used to be).

    Thank you!

     

     

  • 1
    Registered User commented
    Comment actions Permalink

    Another thing I can note is that making Bedrock randomness hardcoded would be a major improvement if it is even possible as currently the randomness is "which part of the processor finishes first" kind of randomness I am pretty sure. This causes a problem where if you have multiple piston based randomizers lined up and activate them at the same time, the piston randomizers closest to each other tend to give the same output, not always, but most of the time. This makes the randomness not very useful as a randomizer either.

  • 1
    Registered User commented
    Comment actions Permalink

    im sorry but, NO!

  • 0
    Registered User commented
    Comment actions Permalink

    I have a lot to talk about: The Redstone wire changes are going to break many contraptions using quasi connectivity and as a QC user my self I don't like this change. The Minecart entity change breaks almost every redstone missile I have built so slime tech is a lot more limited. The Cartstone contraptions are now desynced but I like the speed change. The randomness tries to make you avoid that scenario and I see where you are going but redstone is based on real life electronics and stuff is not random there so why here? The tick stuff broke almost every tick based contraption I have. I get you are trying to optimize Minecraft but please revert this change.

  • 1
    Registered User commented
    Comment actions Permalink

    ACK this sound best to minecraft java performance

  • 1
    Registered User commented
    Comment actions Permalink

    No, I refuse. Revert this NOW.
    This breaks EVERYTHING

  • 1
    Registered User commented
    Comment actions Permalink

    To make something different, perhaps better, change is required, so it must be first broken and then rebuilt.

    The changes are good and make perfect sense, but we all know it will not make the community happy since it will break many contraptions. It's always like this; then people will adapt, and it will become the new standard.

    Since redstone is based on logic, it should also be intuitive. Some randomness makes sense if applied correctly.

    Keep it up! We want more of these changes to keep up with the new content. :)
    Quality-of-Life changes and tweaks like these are what the Minecraft community needs.