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).

← Redstone
72
Follow

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

Pinned

We are trying out some new redstone features in this snapshot. We know redstone changes are scary, so please note that the experimental features behind this toggle are not aimed at any future release at this time. Instead, this is a place for us to try out changes and gather your valuable feedback. We are excited to hear what you think about these changes.

In this update we have improved the impact of redstone wire and changed the update order around wires.

  • Redstone wire now only triggers block updates on blocks that may receive power from the wire
  • Before a line of wire causes block updates, the new signal strength of all connected wires is set

New update order around redstone wires:

  • When a line of wire turns on or off, the wires closer to the power source will cause block updates first
  • When two wires have the same distance to the power source, which of them causes updates first is picked at random
  • The order in which blocks around the wire update is based on the direction the wire received an update from
  • Currently, the order is: back, front, left, right, down, up where left and right may be swapped depending on the random choice made by the line of wire
  • When the updates are further distributed through solid blocks, the same order is applied there

How to try it out:

To enable the redstone changes, go to the Experiments menu and select "Redstone Experiments" when creating a new world.

You can find all previous changelogs in the Knowledge Base in Snapshot Information and Changelogs.

Avatar
Registered User shared this idea

104 Comments

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 2
    Registered User commented
    Comment actions Permalink

    hi Mojang i think the minecart improvements are awesome! that they sould not be undone and added ti the 1.21 final update. on the other hand the redstone wire improvements have some downsides. i think removing the randomicity from the pistone was a great addition but, quasi-connettivity wise i didn't like it, since It broke most of my machines. in the end I hope you restore the "only for the ones who may recive power" function

  • 5
    Registered User commented
    Comment actions Permalink

    Other updates is OK but please don't introduce randomness into the redstone system.

  • 7
    Registered User commented
    Comment actions Permalink

    This is horrible. We need this reverted now.

  • 6
    Registered User commented
    Comment actions Permalink

    Doesn't Mojang know about the things they create work? Do they not know that many things rely on quasi connectivity and the redstone dust updates?? This broke so many redstone builds, so DO NOT implement this.

  • 2
    Registered User commented
    Comment actions Permalink

    I suppose you had better make this red stone update more like gnembom's carpet mod,with all features free to open or close independent ly，defaultly closed. I mean you can create more redstone gamerule.

  • 6
    Registered User commented
    Comment actions Permalink

    Plz don’t change the redstone

  • 4
    Registered User commented
    Comment actions Permalink

    I think most people are overreacting. It is true that a lot of contraptions would break, but throughout the history of the game plenty of changes have been made that have broken some contraptions and it's been fine. People are averse to change, but after a while you learn the new system and you get used to it.

    Locationality is the worst mechanic in the game, so I'd love to see it go. The update order change is so so good. I'm also onboard for reducing the amount of updates from dust. However, I do think that dust should update the blocks adjacent to it, even if it's not powering that block.

    On the introduced randomness, I understand why randomness is disliked. However I feel that people are overlooking the fact that it's not always random, only the 'edge cases' are random. That means that the randomness is trivial to avoid, just make sure everything powered is at different distances from the source. Not to mention that randomness also has its place. There are plenty of contraptions dedicated to creating random results, because sometimes that's useful.

    To conclude, I think it was the right decision for these changes to be experimental and I think it's wonderful that you're taking feedback. I also think most of the negativity just comes from the fact that people dislike change. All in all I believe the changes have lots of potential, great work!

  • 4
    Registered User commented
    Comment actions Permalink

    Do you understand that implementing randomness into redstone will break a lot of machines and farms?
    You slowed down crafters for consistency, then added inconsistent redstone dust.

  • 0
    Registered User commented
    Comment actions Permalink

    REDSTONE DUST: This change takes away the specialty of redstone dust.  I like redstone dust mainly for the fact that it all activates at the same time no matter how far away it is from the power source however, I do agree that the change makes things more logical so here is my idea to fix this:  add another dust/redstone dust look-alike that uses the change and the original redstone dust can work the original way, or swap them, if both options are available then everyone could be happy.  The only flaw that I see with this is that it could make the game more laggy, in which case I would prefer to revert the changes.

    RANDOMNESS: This is a hard one to solve and I understand the pain of trying to find something that both makes sense and doesn't upset people.  Even though the directional system is weird and doesn't make sense, it is consistent and therefore changing it would only bring inconsistency to the game however, what I'm suggesting is another situation where both are added to the game.  Again, Idk what all of the flaws would be if that idea is pursued but having the choice of both is better than only one.  The biggest reason Java redstone is preferred over bedrock redstone is because it's not random and I am on the side of not keeping that change if having both can't be an option.

    I hope this feedback helps in some way and I do appreciate everything that Mojang and the developers have done for this community so far, you are all doing a fantastic job, keep it up.

  • 1
    Registered User commented
    Comment actions Permalink

    Every time you change the deeper mechanics of redstone it ends up breaking all the pre-existing machines. Stop changing the mechanics of redstone, it's already how the community likes it, this is fixing something that was never broken.

  • 0
    Registered User commented
    Comment actions Permalink

    I would like to suggest a compromise for the redstone dust changes. Those of you at Mojang or players who aren’t well-versed in the hidden complexities of redstone may not understand why it is so many people are upset about them right now, but understanding the problem isn’t necessary for you as long as you provide an alternative that keeps everyone happy.

    So, here’s my suggested alternative- add a collection of blocks that are ALWAYS updated by redstone dust in the way they used to be- I’d suggest copper as it’s thematically appropriate, and has both solid AND transparent block variants to it.

    The purpose of this is to give redstoners a way to accomplish the same builds as they did before, WITHOUT needing everyone else to compromise on the lag reduction that reducing block updates provides.

    Don’t want extra block updates? Then don’t put active redstone lines on this block, simple as that, but it doesn’t destroy older machine when would be otherwise unnecessary.

    You don’t need to win every battle, you just need to make sure nobody loses.

  • 0
    Registered User commented
    Comment actions Permalink

    The new Redstone system is not good. I dont even know why you guys are changning it. When its about Matching the Bedrock system, then please not do this! You would destroy another Genuis Part of the game and nobody should want this! The players are Frustaded because of the ideas you guys had!

  • 1
    Registered User commented
    Comment actions Permalink

    Not having redstone wire produce block updates around it anymore is absolutely detremental. An example:

    Previously it was possible to create a button control things without any wirering behind the wall it was on by placing a piston 2 blocks underneath the block it was on and then constantly updating that piston with a redstone wire running along side it. Why would you take that away, it is just unnecessary.

    Not to speak of basically removing QC for Redstone on transparent blocks. Sometimes you just need this capability!

    Deterministic behavior is sooo important to anyone who wants to build and share redstone, by introducing randomness of this kind you are breaking the hard work of thousands. Guess what: if you are far enough along that locationality become a factor, you can look up why it happens. If you are just a casual, you dont really run into that anyway. This new change adds no new capabilities to redstone, because there already is a block in the game that can compare signal strength: the comparator! And it also doenst just do whatever when you try to compare signals of the same strength, it activates if the signal you put in is the same strength as the one you compare it to. Every time. That is easy to understand, this change you propose here is unnecessary.

    If you introduce this change in the name of the casuals and make all the people actually passionate about redstone mad at you I have news for you: the casuals are not gonna care. They will wonder why tutorials broke.

     

  • 1
    Registered User commented
    Comment actions Permalink

    The randomness is utterly awful. I'm sorry but I don't understand how that would ever be considered a good idea.

    What you propose aside, would destroy the technical community. The reason why many of us havn't transferred over to Bedrock from Java is because Bedrock redstone is just plain awful. Why make Java redstone bad as well?

    I'm sorry I'm normally in support of most of your recent changes but this 100% ain't it. This is so bad I can't even.

  • 2
    Registered User commented
    Comment actions Permalink

    Why don’t you make mine-carts that hold blocks stackable while minecarts that don’t non-stackable.

  • 1
    Registered User commented
    Comment actions Permalink

    I'd like if the redstone torch was a bit warmer/more yellow in the center

  • 1
    Registered User commented
    Comment actions Permalink

    I have to say that I like the sequence order of Redstone update. This makes powering a dropper line way easier. This also make any update block lines more predictable and non directional dependent.

    Something that I would add is the ability to right-click on the redstone while facing a direction to direct the redstone line in that direction. Like when the target block redirects the Redstone line. 

    That way you can have a Redstone line behind a piston line and you can choose which pistons get powered by it. This would pair well with the current piston behavior and allow for more compact circuits.

  • 1
    Registered User commented
    Comment actions Permalink
  • 1
    Registered User commented
    Comment actions Permalink

    I like the *principle* behind these changes, it makes redstone follow a clearer set of rules which are easier to understand. This makes redstone more accessible to more players and invites more people to play with more complicated redstone components. With these chages however, there are certain blocks that would need to be added. For example, a transparent, updatable, immovable block.
    I like the randomness aspect, not only do I think it makes sense, I think it can be quite useful.
    As for maintaining previous contraptions working, I think this is important but it's more important to move to a system with clear rules that are easy and intuitive to understand. I look forward to future iterations of these changes that fix moe of the bugs and jankyness that are some times present on this first iteration. Overal this is something I am very excited about!
    P.D. I think people coming here to complain are more motivated than people that come to praise a feature, which is why I decided to chip in support for this cool idea.

  • 0
    Registered User commented
    Comment actions Permalink

    I like the change to redstone block updates. While I appreciate that it removes a functionality that some redstone builds relied upon I think it is really valuable to reduce lag and make redstone more sensible and accessable for new users. I think it will let us do more overall with redstone because we will be able to make redstone builds with less risk to game performance.

    The change to stacking minecarts I think is justified. The only really significant loss is that you now can't create a super dense stack of tnt minecarts, but I think that aspect of the game was kind of overpowered in the first place. With skulk sensors it is way to easy to create an undetectable trap that will instantly vaporize someone and all of their items. Preventing tnt minecarts from stacking will overall improve the play experience an encourage more creative trap designs.

     

  • 1
    Registered User commented
    Comment actions Permalink

    This is not the right way to reduce lag... We know almost every update will break a few things when it comes to redstone; such is the nature of playing a game that is being constantly updated.

    But these changes on Redstone Dust's update range do not merely break pre-existing restone contraptions, the make some of the things that were previously possible using redstone completely unavailable and impossible to recreate.

    This will kill large chunks of the Minecraft redstone community. This is, perhaps, the worst change ever made to redstone in the history of this game, and it is imperative that you do not implement it into the full game.

    Please, let this remain an unfinished experiment.

  • 0
    Registered User commented
    Comment actions Permalink

    I think this is a good thing. In previous versions, the update sequence of redstone powder was difficult to utilize due to its positional nature. Although the modification of directionality may affect some machines, it adds new possibilities, which has both advantages and disadvantages. As for the update range, since it has a significant impact on machines in previous versions, and considering its potential impact on performance is not so significant, perhaps it should be reverted to its original state.

  • 1
    Registered User commented
    Comment actions Permalink
    • Redstone wire now only triggers block updates on blocks that may receive power from the wire
      While this may significantly decrease related lag issues, this change is very harmful to redstone contraptions, especially more complicated ones. Redstone dust updating surrounding blocks has been a staple in making redstone contraptions; for example, when wire runs across a non-solid block above a piston.
    • Before a line of wire causes block updates, the new signal strength of all connected wires is set
      I believe this is a great change since this can remove most of the (duplicate) updates that cause lag with redstone wire.
    • When a line of wire turns on or off, the wires closer to the power source will cause block updates first
      In my opinion, this is a nice addon since the update order for redstone components is now simplified and easier to understand/visualize than locational hashes. However, there may be concerns about how this affects current and future redstone contraptions.
    • When two wires have the same distance to the power source, which of them causes updates first is picked at random
      With the current state of Java redstone, this randomness is not good; besides restricting possibilities, it may even perform worse than direction-based update order, which I encourage to replace the randomness.
    • The order in which blocks around the wire update [. . .] the same order is applied there
      (refer to "This is a nice addon...")
  • 0
    Registered User commented
    Comment actions Permalink

    Pls add the texture for redstone torches for the new update pls pls pls pls
    it is the best texture change on the whole game

  • 0
    Registered User commented
    Comment actions Permalink

    I am NOT a red stoner. I play single player Java only. Removing quasi-connectivity from red stone wire brakes a lot of the farms I do have. I don’t have time to completely relearn red stone then rebuild a bunch of my farms. Please don’t make these changes or make it a setting that can be turned on or off, if you truly believe this will make it easier for new players.

  • 1
    Registered User commented
    Comment actions Permalink

    Redstone is (finally) getting some proper attention, which can benefit greatly the community and game.

    The argument for more intuitive for new players comming into redstone is not the proper question, if you start redstone you rely on delays, not the update order. The new update order (from source to out) can allow more use of the sub-gt update order, that is, without randomness which makes a build unreliable in time !

    Locationality should be avoided, replaced by directionality (or relative directionality as is the update order in theses changes (great !)), but randomness should be avoided at all costs in such a critical component of redstone circuits.

    Setting the SS on the wire before the updates is a great addition, less block updates (and lag), but the 2 block update range is a fundamental feature for the complexity of redstone.

    The power (and fun) of Java's redstone finds roots in its (1) consistency and (2) complexity that, even if not intentional, bring a lot (qc, redstone wire updates 'far', directionality over randomness, little 'quirks') that when well used makes it much better and usefull !

    I see 2 objectives in theses changes:

    1. Reduce lag (by less unecessary block updates) : if all the fonctionnalities are kept then it's always a +
    2. Make redstone more intuitive/acessible : often at the cost of complexity (= beauty) of redstone by removing 'weird' mechanics

    PS: Polling the tech community when making changes to redstone IS the way forward (avoid copper bulb situation...)

  • 1
    Registered User commented
    Comment actions Permalink

    What about adding a new wire, "copper wire," without changing the current functionality of dust?
    Unlike dust, copper wire only transmits signals directly.
    This makes it easier for beginners to understand the specifications of copper wire than dust.
    Since it does not transmit signals to the surrounding area, lag will also be reduced.
    In addition, copper is easier to obtain than redstone dust, and can be obtained at low levels.
    By making more use of copper, beginners will be able to learn circuits more easily.
    Furthermore, if copper wire can be used underwater, I think it will bring a new revolution to circuits.
    Since circuits are very sensitive, I would like to change the environment by adding functions rather than changing the specifications.

  • 0
    Registered User commented
    Comment actions Permalink

    honestly i love the new redstone update some asspects should deffinately be changed but i love the redstone wire realism now it makes it so much better

  • 0
    Registered User commented
    Comment actions Permalink

    We know you want more pairity between bedrock and java. But making java redstone RANDOM is NOT the way. We already have plenty of ways to generate randomness and really i prefer a system that is locational and directional over one that goes out of the source its activated from (and even that isnt consisten, you didnt even make the consistency consistent). Just know that if you keep ignoring the redstone playerbase as you have done with the copper bulb changes that there will be a HUGE uproar. While redstone is the main reason for lag on big servers, how about improving the server jar to just be more efficient overall with things like entity culling. Take a look at what some of the server optimization mods do. You've taken inspiration from mods before like with pistons and horses for example. I think it would be a huge honor for the modders that made sodium and lithium for example to assist you in making the overall playerbase like the game more. Not just cater to one specific part of the playerbase (in this case less redstone-savvy players). Listen to your community and accept their help when needed. A game isnt only shaped by it's creators but by their community as a whole. For example games like TF2 and Geometry Dash. These games and minecraft wouldnt be where they are right now with their huge connected communities, all uniting to make the game they play better for themselves and others. If you are reading this, please help us make the subcommunities in minecraft better.<3

  • 1
    Registered User commented
    Comment actions Permalink

    I'd say keep the random Piston behaviour if they're an equal distance from a source. It provides an easy method of getting randomness when needed and the situations where it'll be annoying are going to be less then the ones where it is helpful. Fix updates not passing through transparent blocks tho since that is the thing honestly breaking most people's builds and honestly the minecart changes where overdue.

    I for one think the changes should not be reverted.