I also want to say RIGHT HERE this is not an excuse to harass individual devs! I wanted to make this video as objective as possible, only about the changes and things that have been said by Mojang! Also the option of completely changing Bedrock's redstone IS NOT EASY! The video kinda frames it as an "obvious solution" but that's because that's the only long term one. Making Bedrock's redstone 20tps is a huge undertaking, and no it's not because of "performance" on low end devices. It's just really hard to undo a system that has been in place for years. Anyway #RevertTheCopperBulb
I'm not very experienced in complex redstone, so I don't know if I use uneven redstone ticks. Though I probably am without knowing. I have several builds (2x3 hidden glass door, and fully hidden staircase with no pistons visible) that are quite complicated in my opinion, and I fear would completely break if Mojang is actually going to match Java's redstone system to bedrock's system. Not to mention how other things would become impossible or at least become 10 times as big for full compatability (quasi connectivity disappearing would be an absolute nightmare).
Bedrock's Redstone is already running completely differently from that of Java ; as such, it makes no sense to try justifying downgrading a feature on one version under the umbrella of "parity". There is no need to rework Bedrock's Redstone ; simply implement the components differently, just like all the others. Either some redstone illiterate morons at the top have enforced those changes onto the devs (I doubt technical individuals would have intentionally ruined such a praised feature for the sake of a single misinformed bug report, much less for that of "parity"), or Mojang is confirming that they are ran by their greed first and foremost, and that they absolutely do not care about their community, in spite of what they claim. I think there has been enough negative feedback thus far for them to have noticed, yet I doubt those changes will be reverted. It seems more and more likely to me that they are intentionally ruining "their" game under the influence of Microsoft ; because, if there's no financial gain, why should they bother delivering. We were already robbed of fireflies -a two single pixels ambient particle pretending to be an actual mob- for the same, nonsensical, illogical reasons. I will not bring up the concepts that didn't get released, as I agree on that they were but concepts. But here, more than sketches and draft implementations, we have been given a fully working feature to toy around with ; and yet, they *chose* to take it away from us. This is unacceptable. I mean, Redstone has never really known any love ever since Microsoft took over (it already wasn't getting much before then) ; but you'd think with younger, independent, popular devs joining the team, surely we'd be seeing improvements in that regard. And we did. Except that it would seem someone *else* had to intervene and actively worsen the content we had finally been given. This is why mods exist. Does any serious player still consider the purely vanilla experience of the game as "Minecraft" ? With its unusable bloated restrictive launcher, lack of basic features and customisation, and unpolished artifacts, be they visual or mechanical ? I need about a hundred or so mods to fill in the gaps they won't fill, and those are but client side mods. Then you get the content mods that should not even require a mod to play with, such as gnembon's carpet mod. Of all requested features, the only technical one we got has been the tick command, and I suppose the return command as well. There have certainly been some improvements over the last few years when it comes to datapacks, but no significant ones regarding redstone. Apart from this long awaited update. Now is our time. May they listen, for once ; May they not, and yet another mod will become mandatory. I long for the day they will discontinue the game (even if it's just Java), as I strongly believe it can be ran by the community, perhaps even as an open source project. I am aware of the existence of clones, but none are truly faithful in their approach. They feel more like Bedrock's interpretation than the actual game we had come to know and love. TL ; DR - I forgot what I wrote lol
The trick is just let java and bedrock readstone be different so much of it is completely different already it wouldn't matter. bedrock doesn't have quis connectivity, the hoppers just don't work in any logical way (items skip so horribly on bedrock), and like you said the detector doesn't even work proper
"This is not an excuse to harass individual devs" Yeah guys, the incompetent losers at Mojang can easily fix the dumbass mistakes that shouldn't even exist in the first place. Not like they have a reputation of being lazy, ego-infalted jerks. Just trust me on this one, absolutely do not do anything that will actually force the devs to improve their shitty game.
@@ReboTheVaporeon Please, do not blame it on the devs. It is extremely unlikely that they had a word to say when it came to such decisions. This, to me, seems like it was imposed from higher up executives *onto* the devs, as it would otherwise go against the flow it would seem they had been able to exert on the game recently.
What is the point of pushing for component parity if components as important as observers don't behave the same on both versions? In that case this is just parity for parity, and that feels wrong
If they wanted parity, glasstone, pushable tile entities and other amazing bedrock redstone features should come to java. Also, everything that makes the superior version superior.
@@hero-bo7qc you can maybe use it for its T-flip flop capabilities but the 1 tick delay functionality is now removed which means that we need to stick to the big clunky trapdoor + scaffolding + observer or log + leaves + observer solutions which means no reduction in size for current instant piston doors
There are a few problems with this change: -The supposed consistency between other redstone components is nonsense to any redstoner. -One of the devs said that the one tick delay was intentional so they should've just said they reverted this because of Bedrock (as speculated) -Odd tick delay is already possible in Minecraft, just not as conveniently as the new bulb would've been -If this was really because they couldn't get the odd tick delay on Bedrock and they changed it for the sake of "consistency", there are SOOOOOO many other things they should've changed for Mojang to stay consistent
if youre so so so mad about consistency why not only have a piston and thats it since for example a repeater isnt consistent with a piston cuz it doesnt push blocks
Also, they say that all redstone components should consistently take 1 redstone tick? Pistons take 1 1/2 to extend and 0 to retract, comparators take 2 redstone ticks to output in certain situations (why you can't have a 1 tick monostable with one tick), and observer clocks don't output every 2 tick, it's closer to 3. This is another reason why the consistency argument is invalid.
@@creeper6530its not because they are lazy, but because it’s really hard to remake a system that has been in place for YEARS. Im gonna edit this, because the replies are a bit much now. As a bedrock player, I say that they should simply let java have the 1 tick delay, and bedrock can have the 0 tick delay. Basically nobody would complain, and it’s good for the devs and the players.
The bedrock observer is still technically 2gt, it’s just that under certain conditions it can appear slower. This is because of really complicated reasons about how bedrock redstone fundamentally works.
The video they made about the crafter is flooded with protests about it and the bulb. Have they listened? Hell no. Do they know? Hell yes. Do they care? With probably the exception of some, *NO*
@@catsdogswoof3968 Bruh as if the majority of players actually know how redstone works, why is it that this change depends on people who literally dont know crap about redstone and tick delays, I dont understand this white-knighting for mojang.
One suggestion I've heard is to make the copper bulb delay dependent on the level of oxidation. Regular Copper Bulbs are instant, exposed are 1 game tick, weathered are 2 game ticks, and oxidized are 3 game ticks.
They didn't change it because the 1-tick delay was boring or a bad feature, they changed it because bedrock is dog. Suggestions to make it a "more interesting" trait fall on ears so deaf stones will listen first.
Better in it consistency. Bugrock has some good features like moving tile entities but it is inconsistent and weird (like pistons always firing when powered).
@@kacperkonieczny7333 if only mojang would hire gnembon, the guy who made a mod for pushable tile entities. O wait they did and that's why the game tick control is a command now (cause he also made that)
Neither redstone system is completely better, they are just different. They are each better at doing some things, but worse at others. They should not make bedrock the same as Java because that would break just about everything on bedrock, and there is no reason to change something small but good on Java to make it like bedrock because they are so different anyway.
@@spacefun101 They are different, in that when notch was making java he decided it's better for contradictory redstone to arbitrarily pick an outcome, even if it doesn't make sense so long as it's consistent, where as the bedrock devs decided it's better for it to be random because you shouldn't rely on arbitrariy parameters like its coordinates or the placement direction of a block anyway. These both have upsides and downsides but because bugrock is bugrock the advantages of random redstone don't show as much.
So... to make their bad product (bedrock redstone decision) look less bad, they took their excellent product and made it worse. So that when compared, the worse one wouldnt look so bad... That is not great Mojang... Consistency over quality.......
Neither system of redstone is bad, they are just different. They can be better at specific things, but are worse at others. But still because they are different, there is no reason to change one system for the worse so that it is like the other.
Don't just revert the copper bulb. MAKE IT EVEN BETTER! Keep it instant, but with 1 game tick of delay for each oxidation stage! Normal = instant, exposed = 1 game tick, weathered = 2 game ticks, oxidized = 3 game ticks. FOUR TIMES THE OPTIONS! Two on even ticks, two on odd ticks! (Seriously, as a tinkerer myself, odd game ticks make synchronizing redstone circuits a nightmare unless you specifically need them.)
I think that is a reasonable solution. This video actually makes me happy that they removed the delay. Instant makes much more sense. Obviously the reason everyone is upset is because that 1gt in a useful package is very helpful. But considering that the bulb is a small t-flip flop, that delay might just get in the way. Mojang should either implement the suggestion above or make odd gt intervals easily obtainable via another block.
@@Foxeyify Agreed. This doing two things at all times would get annoying for some build, but having the option to choose which or both options you use is the best of both worlds
If the change was ACTUALLY made for consistency with other components, then Mojang would’ve seen the backlash and immediately reverted the change in the next snapshot. I absolutely agree that this is *once again* bedrock getting in the way of minecraft
@@superhond1733 dawg. if you've seen the creations in just the first 3 hours of the crafter being released, you'd understand how important it was for redstone. obviously, it doesn't matter; it's a kids game. but outrage calls for change, and that's what they want
Bedrock Observers are already broken compared to Java Observers. I don't see why Java has to suffer for Bulb parity when Bedrock's system is already broken. The longer they wait to fix Bedrock, the harder it will be and the longer it will take. They have to start eventually. Why not start now?
True, i wouldnt mind haveibg no ipdates next you so mojang can focus on fixing the codebase and make good paraty and fix broken systems on both versions. Also this could make update development easier if they fix the code, as it seems to be slowed from bad code wich was written in the beginning.
At this point mojang really need to stop treating java and bedrock the same because they arent the same and they don't need to be. This comes from a bedrock player, we don't need 100% parity with java if it means everyone gets the worst of both worlds.
their goal is to migrate people off of java. they originally planned to stop updating java after 1.20 but backed out after massive backlash. but like that's what we java players deserve for the crime of not having an in-game store...
Parity should've been about bringing good features from one version to the other, not removing them just so they can be the same. no one wins on this one, java players are mad and bedrock players are now crying because they realize that mojang would rather remove a feature from java than add them to their version.
@@tawsifking9336 Not exactly lmao. Java was the original Minecraft back when Mojang was independent. Bedrock came when Microsoft bought them. Bedrock was made by Microsoft specifically to try to make a more unified version of Minecraft and bring it to console and mobile. Get informed before making dumb claims lmao.
Use curseforge for that. There's mods that revert bad game decisions such as the villager nerfs, I can imagine copper bulbs getting their mods as well..
Well that's also a "parity issue" as they say, but they're doing nothing to fix it, so why fixing the redstone ones in a way that 90%+ of people doesn't like.
Maybe they should have a general redstone update where they fix the redstone on bedrock and add a bunch of things the redstone community has been wanting
Bedrock redstone is not broken (at least not more than Java is) so please don’t fix it. There are a couple bugs that would be nice to fix, but the vast majority of differences don’t need to be fixed. Full redstone parity will never be reached, so we should just let them stay different. I think the best solution to bring more parity would be to maybe add copy components, so like maybe tuff and honeyed pistons, with one acting like a bedrock component and the other acting like a Java component. The fundamentals of the systems are still so different that these wouldn’t work exactly the same, but it could cover a lot cases while not taking away from either version.
@@spacefun101 when I said fix bedrock’s redstone I mostly meant giving access to all tick delays instead of having every other one since it would more or less allow Mojang to revert the copper bulb back to how it was without completely breaking both versions, it would give bedrock and Java players what they want with no real downside, I wouldn’t want them to completely change bedrock’s redstone either since it’s the only redstone I know and build with
@@WhoAmI7504-d2l Making every tick available would break a whole lot of redstone in bedrock, while making bedrock redstone a whole lot more laggy, especially for those on lower end devices. Having components activate every other tick is immensely beneficial for performance because it firstly halves the amount of processing needed and gives leeway time for it to speed up if it needed extra time. As someone with a lot of experience in Bedrock redstone, trust me when I say that there would be huge downsides for bedrock in terms of performance and breaking existing redstone. However, Bedrock is not a good reason to have changed it in Java, because they are so different anyway, a one tick difference in one component really would not matter.
MC 1.21 changelog: observers are now 3 times slower for consistency. Leaves and scaffolding update every 2 gameticks instead of 1. Removed quasi connectivity.
>Removed quasi connectivity. unironically a bug they just called a "feature" because they were lazy... bedrocks redstone is the most accurate redstone system they wanted from the beggining of minecraft
@minecraftreports sure, I mean the only use case for them is skyblock and that trend died many years ago and if you search "Minecraft" very little , I mean very very little of the search results is Skyblock... so it will at most anger like couple hundred people and potentially improve performance as they can remove the block/chunk update from the lava/water interactions
They don't have the balls to drop QC almost every complex Redstone build in java would fail, 90% of the Redstone community would just simply quit the game
Because bedrock kids will cry that their product is different than the java... That is literally the only reason i can think that they cant make them SLIGHTLY different (when they already are, like pistons being able to push things that java pistons cant)
"parity" never mind that they have no parity in almost every other system (a brush can get 4 scutes from an armadillo on Java but 5 on bedrock), they HAVE to nerf java redstone additions to maintain parity
Redstone on bedrock sucks bad and is inconsistent with java anyways, so it really wouldn't matter if the bulb was different. Bedrock players wouldn't be able to utilize them properly even if they were consistent with java because of how broken everything else is.
@@FaeiGD Bedrock player spotted. And for your interest, the main playerbase of bedrock is kids 7-13 whilst that of Java is 15-21. So there's your reason.
What people liked about the copper bulb was that it WASN'T consistent with other redstone (1 GT delay) so there is no point in making it more consistent
@@enkvadrat_that and they bumrushed it out the door. What java spent nearly a decade making they rushed out with next to no QC in under 4 years in a code that handles odd numbers like a alcoholic in withdrawal
java doesnt have the tech debt of being retrofitted out of the incredibly basic jank mobile port from back when mobile devices couldnt really run full minecraft lol
I feel like Mojang cannot read the room anymore. The people rallied against the mob vote. The pressed on with the mob vote. The people wanted 1 tick delay copper light bulbs. The devs want "parity between versions" and said no. The problem with the second statement is that there is still no parity between versions for older blocks. Cauldrons can be dyed in Bedrock, why not Java? There are more but the honest truth is that they are both completely different in terms of software. So until a complete rework of Bedrock occurs Mojang needs to embrace differences.
mojang continuing to try and keep "parity" with bedrock and java has only served to make java updates worse. i don't know why they continue to push for this when there are already buckets of features from bedrock not in java and vice versa and when the two versions have completely different engines and structure from one another (see: quasi-conectivity)
Whats funny is that a lot of people who know nothing about redstone reported the 1 gametick delayand no parity for bedrock and java as a bug, so mojang changed it without even CONSIDERING the redstone comunity
After the first few snapshots I thought Mojang would make a great update after the failures since they had to split 1.17... then they came out of nowhere with 23w46a and everyone is mad again. Mojang, you never learn...
@@cherricake1796 They botch Java for bedrock parity but have made no effort to add any bedrock exclusive features to java (armor stand posing, dyed cauldron water, etc)
Then they decided to cook some of the best stuff in the game for this upate by reworking bad omen and opening the door for many more structures to have ominous events of their own on top of some other cool stuff the update also added lol
@@Pickledotno one blames the players, it's entirely Mojang's fault for the absolute state bedrock is in, and at this point Java is getting pulled down with it.
@@Pigismal I have had like twenty people going dam you a bedrock player and then starts talking about every dam redstone feature we wished we had and makes it look like it’s my fault
Yeah, the only thing that threw me off from Bedrock is Java Redstone tbh. With Java Redstone you can make cool stuff with it but Mojang is just too lazy to change the Bedrock Redstones. Heck might cause Spaghetti coding at this point.
@@tsuaririndokuYou can make cool things with bedrock redstone too, it’s not bad just different. Just as with Java, all you need is experience and to practice.
@@spacefun101 Bedrock Redstone isn’t as fun tbh. You can’t make a very effective flying machine or compact 3x3 piston door. I play test some of the Bedrock redstone and tries to learn and practice with it. But in the end, it just my preferred choice to stick with Java Redstones hence Bedrock redstone is a lot more unpredictable when making big redstone contraptions. Only thing I like about Bedrock is how easy it is to place blocks on creative mode. Plus I don’t like Bedrock’s observers which is suppose to be my fav, redstone type block in Java. It is too delayed which somewhat ruins some of the smooth contraptions. Plus, I keep seeing this, Bedrock Pistions are weird to use at times.
Haphazardly pursuing parody between Java and Bedrock Edition could be the worst decision Minecraft has ever made. Instead of making the best game they can, they make one version worse to match the other.
parity* I think the idea of both versions being the same is a good one. However, they seem to be choosing the easier way in most cases, which makes both games worse overall.
Honestly I'm sick and tired of mojang thinking that they know minecraft more then it's players when in reality the players know more about every single aspect of minecraft then them (and yes that includes the code)
@@catsdogswoof3968 not theyre not, notch is left, jeb is just supervising their employees, now jebs job is not even developing anymore. itis simple far as i can tell mojang newcomers employees now they Dont Know What Theyre Doing. please go do some search about mojang few years ago, go find some trailers in their channel, the era even notch still in this company, as long as you can often see them shows up coding more than todays trailers... all i can see today is this company product whether not quite the same as they advertized or is tooo difficult got lazy enough for them to fix anything, all i can trust their action, the future, is to add more blocks more feature. the game used to build as reliable, now i can see is corrupting it One By One from their root
After 10 years of minecraft modded experience... I will assure you, they don't fucken know their code. @@catsdogswoof3968 If DrZhark hadn't entered mojang, We wouldn't have horses, and probably he is charged in making mob ideas and implementations. I'm still sad he makes 3 fun mobs for the community to choose only one of them. I hope he sometimes releases himself from this job that is killing his passion slowly since Microsoft adquired mojang.
Honestly, I'm repeatedly convinced that Bedrock's code is just a mess, since at least looking from an outside observer who knows how Java Minecraft works, Bedrock's system should be *easy* to add in odd game ticks. Java developers are quickly adding in lots of neat debugging tools (like official tick commands) and new stuff relatively quickly, whereas Bedrock gets things slower and (appears) clunkier. I dunno, it feels like Mojang is digging their heels into Bedrock and it feels like largely a decision being made from high up, since the devs are given a lot of freedom and then seemingly having their decisions reverted on a whim. I don't like it, but I'm not surprised.
@@DecayedPagethe language shouldnt be a problem since it uses c++ but maybe the overkill code optimization. I'd be down for an updafe pause so the devs can fix and refactor the code so its easier to develop on wich maybe would imporve future update dev time
some dude on Minecraft Feeback proposed that the bulbs could have a different time response based on its oxidation level : the more oxidized the bulb is, the slower it gets (for exemple, 1, 2 3 then 4 game ticks, or 0, 1, 2 and 3, or even 1, 2, 4, and 8). I think this could be a good alterative to the solution mojang gave, plus it would add a bit of variety to redstone systems, given you could always wax the copper bulbs so they don't change stage. [sorry foor bad english]
Just thinking back to the old times, the good old days where Honey Blocks existed, and we said something like 'Make them not stick to slime blocks' and Mojang was like 'Yep! No problem.' And they didn't stick. Whatever happened to those days?
As a bedrock player, just give bedrock the instant bulb, and let java have the 1 tick bulb. Timings are already not consistent between the two versions, why ruin java redstone by starting now.
Because the more they make differences between java and bedrock redstone the more bedrock players will get madder about it, Mojang doesn't want that which sadly is why they try to make them similar not by fixing bedrock but ruining java because thats the easier route.
mojang dosent listen to massive groups of people asking the same thing, but when one person complains about fireflies, mojang is like: Oh my bad lets ruin this update so this angry twitter user can be happier.
First time watcher here. You've got great presentation skills and good production value. I understood everything well despite being a novice with Redstone. The lil pop-up you added showing the Resource Pack you used is NOT something you see often and I just have to comment on how neat it was that you included that!
Mojang are never going to bridge the gap between bedrock and java redstone, like I cannot imagine they ever add quasi-powering into bedrock nor can they really remove it from bedrock for instance. Just let java players have 1gt, and if the problem really is that bedrock redstone needs an overhaul.... maybe give them an overhaul??? I'm sure bedrock players would love some consistent update orders
@@thatemocat When I read your comment, I first thought to myself “Yeah, of course they're not going to go out of their way to make redstone worse”. Then I realized...
Interesting, I didn't think about making the delay double each time. That's a pretty unique solution. Still, I think the bulb should be instant by default so that it's consistent at first, but "degrades" over time. So the delays would be 0 tick, 1 tick, 2 tick, 3 tick. That gives players two odd delays to use!
One thing I can say about your content which I'm actually quite proud of, is how much you've matured. Your scripting feels much stronger with less 'salt' in it. It's quite refreshing and I'm really happy to see a flourishing channel out of you
If they really wanted to promote "consistency" and "tinkering," they could have varied the delay depending on the oxidization state of the bulb: 1 game tick delay per oxidization level, starting at 0 and ending with 3. That way it doesn't feel as random and haphazard, and it integrates the unique oxidization feature of the block into redstone in a really interesting way that gives the player more control. It would even make sense logically: the old circuitry grows slower as the block grows more oxidized.
Probably not, since it's going to be only red stoners who would care enough to download it, which is a much smaller portion of the community. Probably not the most downloaded mod, but it will definitely be useful
Mojang acting like they didn't literally choose to make this parity problem, they choose again to ignore it repeatedly and act like ruining both games is somehow betting than fixing one.
@@catsdogswoof3968You're clearly a bedrock player at this point you could listen to newton describing why parity actually ruins the game and you still wont listen XD.
I say make the instant nature of the bulb exclusive to bedrock. Java redstoners will remain happy And UA-camrs will have another thing to slap onto their 100 things that make Bedrock unique from Java video, it's a win win...except for the bedrock users. As someone who grew up with bedrock I cannot deny that we got the short end of the stick when it comes to redstone by a large margin. Like if fixing it is too hard then this feels like the least you can do for both parties.
This is a very well explained video, so it should reach non-redstoners as well. I normally don't comment feedback/ideas, because it can be perceived as rude, but I think a title that instead of just keyword "how", also has something like " - Redstone Timings Explained", could be better.
@@FireroseNekowolfthey can do it whenever they want but it will destroy the fps bedrock gets it runs 2x as good by running 1/2 as much same with every thing else on bedrock it runs "better" because it does less. they don't want to remove the only selling point for bedrock so they can continue to scam people on the marketplace
I disagree, 1.9 is still the most controversial update in the game because it forced everyone to relearn PVP. I think PVP parity is the biggest example, but there are many compounding smaller examples of unparity that would cause issues to unify.
Sorry. Noob question here🙋♀️ if bedrock and java redstone components are already different from each other, Why can't it just be on even ticks in bedrock and on odd ticks on java?
That's not even true. For example: working pots, cherry forests, uses for copper(and tuff), new armadillo texture, the crafter and many other features from the newer updates were added because of the comunity.
@@AndrewP24314 You are just lying at this point :/ I saw many people online talking about how they wanted to see more uses for copper and wanted pots to contain loot. Cherry forest is popular on Minecraft Feedback. I know there are many things Mojang should've done that they didn't, I know they constantly make many mistakes (it's the theme of the video), but it doesn't excuse lying and blaming them for the mistakes they didn't make.
All arguments I have heard for why changing the copper bulbs to what they became was a good idea are terrible reasons for why to make it like that. And the only one that is close being sensible is also stupid. That one being: making it more in sync with how Bedrock edition works. The reason why this is stupid is: why not just fix bedrock edition to make it work like Java edition, rather than ruining Java edition to make them more alike. Also, if they really wanted it all to be consistent, then there is a lot of other stuff they should have looked at first. Making it consistent to bedrock like this is a fools errand.
@@catsdogswoof3968 How would NOT complaining about this encourage Mojang to fix it? Also obligatory, stopped*, would*, there should be a comma between it and but, and periods exist. Stop acting like the mega-corporation is a tiny studio that can't handle feedback, perhaps come up with actual arguments, or at the very least spend more than 3 seconds putting together your keyboard smash so that it's almost somewhat legible.
Before they go and "make copper bulbs consistent with other blocks", they should be making bedrock's redstone mechanics actually consistent. What is the point of consistency when the rest of the mechanics in 1 version are vastly more inconsistent?
I've always felt that Mojang (Microsoft) see the quirks of Java that have developed into features as bugs that need to be "fixed". Minecraft is fundamentally a sandbox game so unintentional things that end up affecting the way the game plays are usually seen as optional and fun or useful and helpful by the community. Unfortunately the developers don't seem to quite feel the same way.
Why should redstone even be limited to 10 ticks in the first place? In fact why is bedrock so limited when it could have been better than java if it wasn't trying to be just like java? Because they are programming with a systems level language, now it will be harder to fix then doing it right in the first place.
I dont get their vision with parity... they remove good features on both versions to make them the similar, slightly worse versions... they cant keep doing that
Ugh... I want parity to to be ACTUALLY good, not parity for the sake of parity! When we say "we want parity," we mean we want waterlogged anvils in java, snowlogged flowers and grass in java, armorstands with arms in java, dyeable cauldron water in java, offhand compatibility for bedrock, more responsive mouse movements for bedrock, and any other really cool feature! Bedrock's redstone is already super different (and debatably broken) compared to Java, so WHY did they feel the need to do this???
Honestly the management there is weird. The whole thing with the firefly in the past was one of the managers taking a complaint too seriously. Ain't suprised if their idea of perfect parody despite coding limitations is influencing this despite the developers under them wanting otherwise.
Fireflies weren't removed because they were poisonous to frogs, it was because they were resource hogs and devs couldn't get them to work without unplayable lag
@@jonnyblaze2692 100 entities flying around aimlessly is not laggy, your world likely already had 80 loaded, just community manager took a complaint to heart. Spawn 100 bats and tell me what happens.
I originally thought it was resources too but sadly no, management is just bad, for devs to be more public and in touch than the community manager is the problem.
Very well put together video. You made Redstone look easy, you're really good with explaining it in great detail on how it works. I hope Mojang reverts the Copper Bulb too, you redstoners are some of the most creative folks I've seen in this community.
This is just like the times they said they couldn't implement fireflies into the the game because "they're poisonous to frogs" or when they gave the excuse to slow down Elytra speed by 20% after the Caves and Cliffs update because "they wanted to allow the player to take in the new sights easier", all absolutely bullshit excuses around the fact that they were omitted/changed due to technical limitations. This I'd argue is even worse because it's not even due to any sort of technical limitations, they're just trying to treat Bedrock as their main game and therefore Java has to be more like it, not the other way around (even tho Bedrock's redstone is still inferior in so many ways).
I just have to correct you in soemthing. Bedrock edition does actually run on 20 gameticks. Its just that some redstone components run on odd numbered ticks and some on even numbered ticks
I have barely touched these new redstone components so I knew there was something people didn’t like about the new bulb but I didn’t actually know why. I thought they removed the entire t-flip-flop functionality. Glad to see that’s not the case, but the 1gt delay would be super nice to have. Hopefully mojang can understand this and restore it to it’s old version
I dont see why java cant just keep the copper bulb as it was while bedrock gets the updated one. This reminds me of the young ahamkara's spine nerfs destiny had a while back. They were nerfed to fit better with the balance of pvp (like bedrock) and the pve side (java) also got nerfed because of it.
it really sucks that java is suffering from bedrock, however i just wanna point out that does not give anyone the right to bash on bedrock players. in a lot of videos where diffrences between bedrock and java were discussed, i saw comments that just straight up hated on the players. things like "i hate every bedrock player they are turning mojang into EA" lets not do that here
Tbf it might not be every player but microtransactions target the "whale" playerbase that play exorbitant amounts of money. I dont know if minecraft is like that considering their form of microtransactions is world downloads or skins and emotes. Their argument might make sense in a flawed way but even if its true not app players spend money and even less are "whales" Still there are some people who hate just to hate those people's minds you can never change no matter what you say.
If every bedrock player quit bedrock and started playing Java, bedrock would cease to exist. All of this is caused by bedrock players. I used to be a bedrock player on the Xbox and I converted and have never once looked back.
Sometimes you have to wonder what the point of this is. The community is SCREAMING at the top of their lungs that this is a terrible and completely unnecessary change, which it is. And yet, Mojang goes ahead with this anyway, almost as if they are paying literally zero attention to the community or otherwise intentionally trying to dismiss them. Does Mojang even listen? Do they even care? It’s a mystery with this level of negligence.
I doubt bedrock is the reason. rather I would say that it is due to the logical structures. The bulb seems to be designed to behave like a memory bit and I suppose the tick delay it has could be a drawback in logic mechanisms, so it makes sense (I assume they meant this by "consistency"). I don't think all the mechanics presented in the video were mojang's main idea. And yes, I know we had mechanisms for representing memory bits, but there's no reason to get too complicated when we've been given this block that clearly does it better and I also don't think it should be the primary method for getting odd ticks.
WHAT'S EVEN THE POINT THEN?!!?! 😭 I mean, why can't they change it if it's just a bug? I though that the game runned at other speed, BUT THIS IS EVEN DUMBER.
10:31 actually it would take 2 redstone ticks or 4 gameticks to activate since because you're using a lever to power the redstone line, the comparator and redstone repeater actually have a zero tick delay (so setting the repeater to 3 ticks will actually only give it a 2 tick delay when powering it with a lever)
Honestly, what could have been done for both versions? Unoxidized and shiny copper bulb = no tick/instant. Each level of oxidation adds 1 tick delay. That way, we can have our instant copper bulbs, 1-tick copper bulbs, 2-tick copper bulbs, and 3-tick copper bulbs in one package. After all, a buildup of copper oxide _does_ reduce conductivity. Just wax the copper bulb once you get the desired oxidation level.
Mojang lied as naturally as they breathed, consistency is the most obvious lie for a redstoner, if all redstone features had to be consistent, decorated pots would have had a GUI like any other storage, but it doesn't, because it has a unique interaction, which makes it a valuable redstone block, sure the bulb has t-flip flop as a feature but if droppers hadn't had a randomized drop and instead just drops from top left to bottom right like the new crafter with hopper it, it would lose so much value as a redstone block.
The worst thing is: they said that redstone _never_ will get full parity between Java and Bugrock, but they are now breaking something in Java to make it consistent with Bugrock. Or they just saw that "Ooh, the MC community is happy about something we do - let's change that!" and broke it just to make us less happy.
@Lampe2020 Java has more bugs than bedrock, Java's bugs are just rebranded as features. Also the bugs that happen in bedrock like randomly dying only happen on awful devices, or if you're playing multiplayer with a bad wifi connection.
Everyone should just always use a mod to revert mojangs stupid decisions and call that vanilla if java is going to continue being affected by bedrock in all these sorts of ways
@@catsdogswoof3968 I'm talking about ALL the dumb features, continue piling them onto a mod. Everyone use that mod. Ofc it wouldn't work, since everyone has their own opinions, some like features that others dont, but just wish it could
As a Redstoner myself its funny hearing people say "bedrock is weird" and am not saying its better its just that java is the broken one its just that most people got used to the glitches that the intended Redstone is weird.... but as always "its not a glitch its an intended feature" that makes java redstone feel a lot better than bedrock And then there is weird differences like how bedrock doesnt have a priority list based on the power source so its actually 100% random in bedrock and said tick difference btween observer in bedrock and java
a logic system needs to be consistent bedrock redstone does not have a fixed subtick update order the same contraption in the same place can do different things, just, randomly How is that better? Java might be unintuitive, but it's behaving logically! If a logic circuit system is inconsistent, it is absolutely worthless.
I also want to say RIGHT HERE this is not an excuse to harass individual devs! I wanted to make this video as objective as possible, only about the changes and things that have been said by Mojang!
Also the option of completely changing Bedrock's redstone IS NOT EASY! The video kinda frames it as an "obvious solution" but that's because that's the only long term one. Making Bedrock's redstone 20tps is a huge undertaking, and no it's not because of "performance" on low end devices. It's just really hard to undo a system that has been in place for years.
Anyway #RevertTheCopperBulb
I'm not very experienced in complex redstone, so I don't know if I use uneven redstone ticks. Though I probably am without knowing. I have several builds (2x3 hidden glass door, and fully hidden staircase with no pistons visible) that are quite complicated in my opinion, and I fear would completely break if Mojang is actually going to match Java's redstone system to bedrock's system. Not to mention how other things would become impossible or at least become 10 times as big for full compatability (quasi connectivity disappearing would be an absolute nightmare).
Bedrock's Redstone is already running completely differently from that of Java ; as such, it makes no sense to try justifying downgrading a feature on one version under the umbrella of "parity".
There is no need to rework Bedrock's Redstone ; simply implement the components differently, just like all the others.
Either some redstone illiterate morons at the top have enforced those changes onto the devs (I doubt technical individuals would have intentionally ruined such a praised feature for the sake of a single misinformed bug report, much less for that of "parity"), or Mojang is confirming that they are ran by their greed first and foremost, and that they absolutely do not care about their community, in spite of what they claim.
I think there has been enough negative feedback thus far for them to have noticed, yet I doubt those changes will be reverted.
It seems more and more likely to me that they are intentionally ruining "their" game under the influence of Microsoft ; because, if there's no financial gain, why should they bother delivering.
We were already robbed of fireflies -a two single pixels ambient particle pretending to be an actual mob- for the same, nonsensical, illogical reasons. I will not bring up the concepts that didn't get released, as I agree on that they were but concepts.
But here, more than sketches and draft implementations, we have been given a fully working feature to toy around with ; and yet, they *chose* to take it away from us.
This is unacceptable.
I mean, Redstone has never really known any love ever since Microsoft took over (it already wasn't getting much before then) ; but you'd think with younger, independent, popular devs joining the team, surely we'd be seeing improvements in that regard. And we did. Except that it would seem someone *else* had to intervene and actively worsen the content we had finally been given.
This is why mods exist. Does any serious player still consider the purely vanilla experience of the game as "Minecraft" ? With its unusable bloated restrictive launcher, lack of basic features and customisation, and unpolished artifacts, be they visual or mechanical ?
I need about a hundred or so mods to fill in the gaps they won't fill, and those are but client side mods.
Then you get the content mods that should not even require a mod to play with, such as gnembon's carpet mod.
Of all requested features, the only technical one we got has been the tick command, and I suppose the return command as well. There have certainly been some improvements over the last few years when it comes to datapacks, but no significant ones regarding redstone.
Apart from this long awaited update.
Now is our time.
May they listen, for once ;
May they not, and yet another mod will become mandatory.
I long for the day they will discontinue the game (even if it's just Java), as I strongly believe it can be ran by the community, perhaps even as an open source project. I am aware of the existence of clones, but none are truly faithful in their approach. They feel more like Bedrock's interpretation than the actual game we had come to know and love.
TL ; DR - I forgot what I wrote lol
The trick is just let java and bedrock readstone be different so much of it is completely different already it wouldn't matter.
bedrock doesn't have quis connectivity, the hoppers just don't work in any logical way (items skip so horribly on bedrock), and like you said the detector doesn't even work proper
"This is not an excuse to harass individual devs" Yeah guys, the incompetent losers at Mojang can easily fix the dumbass mistakes that shouldn't even exist in the first place. Not like they have a reputation of being lazy, ego-infalted jerks. Just trust me on this one, absolutely do not do anything that will actually force the devs to improve their shitty game.
@@ReboTheVaporeon Please, do not blame it on the devs.
It is extremely unlikely that they had a word to say when it came to such decisions.
This, to me, seems like it was imposed from higher up executives *onto* the devs, as it would otherwise go against the flow it would seem they had been able to exert on the game recently.
What is the point of pushing for component parity if components as important as observers don't behave the same on both versions? In that case this is just parity for parity, and that feels wrong
Also, QC
If they wanted parity, glasstone, pushable tile entities and other amazing bedrock redstone features should come to java. Also, everything that makes the superior version superior.
@@Noteturtle90
Everything that makes the superior version superior is already on Java, because it *is* the superior one
They want to be able to keep pretending that bedrock is just as good as Java
@@Yegor_Mechanicnot gonna lie, movable tile entities would be nice in Java
the Copper bulb wouldve gotten us insanely small instant piston doors :(
Ikr? Although I don't do Java redstone, lol
Let's add this to Redstone tweaks!
Couldn't you still use it though?
You still can?
@@hero-bo7qc you can maybe use it for its T-flip flop capabilities but the 1 tick delay functionality is now removed which means that we need to stick to the big clunky trapdoor + scaffolding + observer or log + leaves + observer solutions which means no reduction in size for current instant piston doors
"Mom, why can't I have any milk?"
"Because your brother is lactose intolerant."
"Dad, why can't I participate in any marathons?"
"Because your siblings is paraplegic."
E
“Uncle, why can’t I swim”
“Because you cousin is hydrophobic”
"Aunt, why can't I have friends?"
"Cause your sister is dead!"
@@ChainsawMixx "kid flasher!" 🤮🤮🤮
@@chloeholmes4641 I'm sorry
There are a few problems with this change:
-The supposed consistency between other redstone components is nonsense to any redstoner.
-One of the devs said that the one tick delay was intentional so they should've just said they reverted this because of Bedrock (as speculated)
-Odd tick delay is already possible in Minecraft, just not as conveniently as the new bulb would've been
-If this was really because they couldn't get the odd tick delay on Bedrock and they changed it for the sake of "consistency", there are SOOOOOO many other things they should've changed for Mojang to stay consistent
if youre so so so mad about consistency why not only have a piston and thats it since for example a repeater isnt consistent with a piston cuz it doesnt push blocks
@@emre_ez What? Did you even read the comment?
@@mioszantas4462I think they were agreeing with you, saying that “consistency” is a stupid excuse.
Also, they say that all redstone components should consistently take 1 redstone tick? Pistons take 1 1/2 to extend and 0 to retract, comparators take 2 redstone ticks to output in certain situations (why you can't have a 1 tick monostable with one tick), and observer clocks don't output every 2 tick, it's closer to 3. This is another reason why the consistency argument is invalid.
Yeah, as if Redstone between Java and bedrock were consistent to begin with. Not gonna lie, that may be the worst argument they could bring
So they decided to make java worse instead of making bedrock better
@@creeper6530it wouldn't exactly be easy to rework all of bedrock redstone
@@creeper6530its not because they are lazy, but because it’s really hard to remake a system that has been in place for YEARS.
Im gonna edit this, because the replies are a bit much now. As a bedrock player, I say that they should simply let java have the 1 tick delay, and bedrock can have the 0 tick delay. Basically nobody would complain, and it’s good for the devs and the players.
Why did they change anything at all?
@@penginguy2177mojang is a multi million dollar company, if not multi billion. They could do it if they actually wanted
@@nicolaecalin4217 No, MICROSOFT is. Mojang is a SUBSIDIARY.
If Bedrock observers have 6 gt, and Java have 2 gt, why can't Bedrock and Java cooper bulbs also have different tick-delays?
im scared that if mojang saw this comment they would change java observor speed to 6gt to keep it "consistent with badruok"
The bedrock observer is still technically 2gt, it’s just that under certain conditions it can appear slower. This is because of really complicated reasons about how bedrock redstone fundamentally works.
because microsoft owned mojang don't want to have to admit bedrock is super janky and playing poorly with the source code
@@lukasjetu9776time to report it as a bug 🤓
(which is literally what someone did with copper bulbs...)
because they are too lazy.
In the Minecraft feedback page for 1.21, 8 out of the 10 most voted posts protesting this change.
The video they made about the crafter is flooded with protests about it and the bulb. Have they listened? Hell no. Do they know? Hell yes. Do they care? With probably the exception of some, *NO*
@@Noteturtle90 yep with how the fireflies went down im sure they wont be changing their minds on this either
Ask all half a billion players
@@catsdogswoof3968 Bruh as if the majority of players actually know how redstone works, why is it that this change depends on people who literally dont know crap about redstone and tick delays, I dont understand this white-knighting for mojang.
@@catsdogswoof3968 This guy does not know how many players Minecraft actually has.
One suggestion I've heard is to make the copper bulb delay dependent on the level of oxidation. Regular Copper Bulbs are instant, exposed are 1 game tick, weathered are 2 game ticks, and oxidized are 3 game ticks.
Yeah that actually seems like a good idea
Sadly mojang doesn’t really care much. They are slowly dooming themselves.
They didn't change it because the 1-tick delay was boring or a bad feature, they changed it because bedrock is dog. Suggestions to make it a "more interesting" trait fall on ears so deaf stones will listen first.
@@chaotixthefox Why would they change it for consistency between versions when they're already different?
@@tweer64 To make the versions less different.
Redstone already is version dependent. And Java Redstone is just better so keep it different or make bedrock fit Java.
Better in it consistency. Bugrock has some good features like moving tile entities but it is inconsistent and weird (like pistons always firing when powered).
@@kacperkonieczny7333 if only mojang would hire gnembon, the guy who made a mod for pushable tile entities. O wait they did and that's why the game tick control is a command now (cause he also made that)
Neither redstone system is completely better, they are just different. They are each better at doing some things, but worse at others. They should not make bedrock the same as Java because that would break just about everything on bedrock, and there is no reason to change something small but good on Java to make it like bedrock because they are so different anyway.
@@kacperkonieczny7333Neither redstone system is consistent, but they both are if you can do it right.
@@spacefun101 They are different, in that when notch was making java he decided it's better for contradictory redstone to arbitrarily pick an outcome, even if it doesn't make sense so long as it's consistent, where as the bedrock devs decided it's better for it to be random because you shouldn't rely on arbitrariy parameters like its coordinates or the placement direction of a block anyway. These both have upsides and downsides but because bugrock is bugrock the advantages of random redstone don't show as much.
So... to make their bad product (bedrock redstone decision) look less bad, they took their excellent product and made it worse. So that when compared, the worse one wouldnt look so bad...
That is not great Mojang... Consistency over quality.......
youre wrong
@@tenidiotaodpizzy4603prove it
That sound like enshittification
@@tenidiotaodpizzy4603*you're
Neither system of redstone is bad, they are just different. They can be better at specific things, but are worse at others. But still because they are different, there is no reason to change one system for the worse so that it is like the other.
Don't just revert the copper bulb. MAKE IT EVEN BETTER! Keep it instant, but with 1 game tick of delay for each oxidation stage! Normal = instant, exposed = 1 game tick, weathered = 2 game ticks, oxidized = 3 game ticks. FOUR TIMES THE OPTIONS! Two on even ticks, two on odd ticks! (Seriously, as a tinkerer myself, odd game ticks make synchronizing redstone circuits a nightmare unless you specifically need them.)
So basicaly a repeater with extra steps
@@noelka8134 yes a repeater with inbetween repeater steps.
I think that is a reasonable solution. This video actually makes me happy that they removed the delay. Instant makes much more sense.
Obviously the reason everyone is upset is because that 1gt in a useful package is very helpful. But considering that the bulb is a small t-flip flop, that delay might just get in the way.
Mojang should either implement the suggestion above or make odd gt intervals easily obtainable via another block.
@@Foxeyify Agreed. This doing two things at all times would get annoying for some build, but having the option to choose which or both options you use is the best of both worlds
If the change was ACTUALLY made for consistency with other components, then Mojang would’ve seen the backlash and immediately reverted the change in the next snapshot. I absolutely agree that this is *once again* bedrock getting in the way of minecraft
What's the logic?
Or....
You java players could stop crying about something that doesnt matter
@@superhond1733 dawg. if you've seen the creations in just the first 3 hours of the crafter being released, you'd understand how important it was for redstone. obviously, it doesn't matter; it's a kids game. but outrage calls for change, and that's what they want
So that's why it's called bedrock edition huh
@@Crimery1 child
Bedrock Observers are already broken compared to Java Observers. I don't see why Java has to suffer for Bulb parity when Bedrock's system is already broken. The longer they wait to fix Bedrock, the harder it will be and the longer it will take.
They have to start eventually. Why not start now?
laziness and a will to not listen to their dwindling playerbase
True, i wouldnt mind haveibg no ipdates next you so mojang can focus on fixing the codebase and make good paraty and fix broken systems on both versions. Also this could make update development easier if they fix the code, as it seems to be slowed from bad code wich was written in the beginning.
Yea.... they are starting now demoting any attempt will stop them
@@SydneyPawYTfalse
@@ItsCOMMANDer_yea
At this point mojang really need to stop treating java and bedrock the same because they arent the same and they don't need to be. This comes from a bedrock player, we don't need 100% parity with java if it means everyone gets the worst of both worlds.
their goal is to migrate people off of java. they originally planned to stop updating java after 1.20 but backed out after massive backlash.
but like that's what we java players deserve for the crime of not having an in-game store...
If they did that I would be sad and then boom they can't
@@unflexian there's also the part that it runs only on pc but relax the current bedrock problems will stay until the end of Minecraft
Parity should've been about bringing good features from one version to the other, not removing them just so they can be the same.
no one wins on this one, java players are mad and bedrock players are now crying because they realize that mojang would rather remove a feature from java than add them to their version.
or opposite
removing a bedrock feature to be in line with java
mojang hates both versions
@@doctornobody105 Microsoft*
@@river559 Microsoft owns mojang so same thing
@@tawsifking9336 Not exactly lmao. Java was the original Minecraft back when Mojang was independent. Bedrock came when Microsoft bought them. Bedrock was made by Microsoft specifically to try to make a more unified version of Minecraft and bring it to console and mobile. Get informed before making dumb claims lmao.
we need to make a copper bulb behavior revert plugin the norm and refuse to use the useless,
vanilla version
Impossible unless you finally do something other than complain and raid mojang
@@catsdogswoof3968 no that is an easy thing to fix with mods.
@@catsdogswoof3968 java is known for modding its very easy to make such a thing. through mods they had autocrafting and even more
Use curseforge for that. There's mods that revert bad game decisions such as the villager nerfs, I can imagine copper bulbs getting their mods as well..
@@catsdogswoof3968it is as easy as copying the blocks data from the snapshot and making a datapack to replace the logic of this block in particular
Copper Blub would have been one of the best additions if they didn't make it instant
I love the Copper Blub ❤❤
Copper Blub my beloved ❤❤❤
Copper *Blub*
True,could have been on targetblock level
Ah yes the Copper *Blub*
So Bedrock and Java can have entirely different combat systems, but a 0.05 second difference for the copper bulb is too far. Alright.
Well that's also a "parity issue" as they say, but they're doing nothing to fix it, so why fixing the redstone ones in a way that 90%+ of people doesn't like.
Really tells me that the ones who went through with theses changes were left in charge of something they had 0 clue about redstone at all.
Maybe they should have a general redstone update where they fix the redstone on bedrock and add a bunch of things the redstone community has been wanting
Would be nice but faith in mojang is at an all time low
Bedrock redstone is not broken (at least not more than Java is) so please don’t fix it. There are a couple bugs that would be nice to fix, but the vast majority of differences don’t need to be fixed. Full redstone parity will never be reached, so we should just let them stay different. I think the best solution to bring more parity would be to maybe add copy components, so like maybe tuff and honeyed pistons, with one acting like a bedrock component and the other acting like a Java component. The fundamentals of the systems are still so different that these wouldn’t work exactly the same, but it could cover a lot cases while not taking away from either version.
@@spacefun101 when I said fix bedrock’s redstone I mostly meant giving access to all tick delays instead of having every other one since it would more or less allow Mojang to revert the copper bulb back to how it was without completely breaking both versions, it would give bedrock and Java players what they want with no real downside, I wouldn’t want them to completely change bedrock’s redstone either since it’s the only redstone I know and build with
@@WhoAmI7504-d2l Making every tick available would break a whole lot of redstone in bedrock, while making bedrock redstone a whole lot more laggy, especially for those on lower end devices. Having components activate every other tick is immensely beneficial for performance because it firstly halves the amount of processing needed and gives leeway time for it to speed up if it needed extra time. As someone with a lot of experience in Bedrock redstone, trust me when I say that there would be huge downsides for bedrock in terms of performance and breaking existing redstone. However, Bedrock is not a good reason to have changed it in Java, because they are so different anyway, a one tick difference in one component really would not matter.
@@blademasterzero which makes modding the game at an all time high.
MC 1.21 changelog: observers are now 3 times slower for consistency. Leaves and scaffolding update every 2 gameticks instead of 1. Removed quasi connectivity.
>Removed quasi connectivity.
unironically a bug they just called a "feature" because they were lazy... bedrocks redstone is the most accurate redstone system they wanted from the beggining of minecraft
@@petrkdn8224 bait used to be believable
@@petrkdn8224guess cobblestone gens should also be removed since it was a bug that got called a feature
@minecraftreports sure, I mean the only use case for them is skyblock and that trend died many years ago and if you search "Minecraft" very little , I mean very very little of the search results is Skyblock... so it will at most anger like couple hundred people and potentially improve performance as they can remove the block/chunk update from the lava/water interactions
They don't have the balls to drop QC almost every complex Redstone build in java would fail, 90% of the Redstone community would just simply quit the game
I was excited to see what the noteblock makers would come up with but then this happened.
tbh why cant they just make them diffrent on bedrock and java
Because bedrock kids will cry that their product is different than the java... That is literally the only reason i can think that they cant make them SLIGHTLY different (when they already are, like pistons being able to push things that java pistons cant)
"parity"
never mind that they have no parity in almost every other system (a brush can get 4 scutes from an armadillo on Java but 5 on bedrock), they HAVE to nerf java redstone additions to maintain parity
Redstone on bedrock sucks bad and is inconsistent with java anyways, so it really wouldn't matter if the bulb was different. Bedrock players wouldn't be able to utilize them properly even if they were consistent with java because of how broken everything else is.
@@rafalstimagine calling people kids for playing a specific Minecraft edition, no wonder why this community is so fucking awful
@@FaeiGD Bedrock player spotted.
And for your interest, the main playerbase of bedrock is kids 7-13 whilst that of Java is 15-21. So there's your reason.
What people liked about the copper bulb was that it WASN'T consistent with other redstone (1 GT delay) so there is no point in making it more consistent
It's crazy how they made bedrock so it was compatible on multiple devices in a better/faster language, yet fucked up beyond all reason.
C++ is in theory a faster language, but it is harder to code in and does not equal good code and a good game.
@@enkvadrat_that and they bumrushed it out the door. What java spent nearly a decade making they rushed out with next to no QC in under 4 years in a code that handles odd numbers like a alcoholic in withdrawal
???? better/language??? it's written in Segfault++ and you call it better?????
java doesnt have the tech debt of being retrofitted out of the incredibly basic jank mobile port from back when mobile devices couldnt really run full minecraft lol
I feel like Mojang cannot read the room anymore. The people rallied against the mob vote. The pressed on with the mob vote. The people wanted 1 tick delay copper light bulbs. The devs want "parity between versions" and said no. The problem with the second statement is that there is still no parity between versions for older blocks. Cauldrons can be dyed in Bedrock, why not Java? There are more but the honest truth is that they are both completely different in terms of software. So until a complete rework of Bedrock occurs Mojang needs to embrace differences.
Just a FYI in the early snapshots on BEDROCK the copper bulb was very capable of odd tick uses.
ah, yes, it was for no reason
mojang continuing to try and keep "parity" with bedrock and java has only served to make java updates worse. i don't know why they continue to push for this when there are already buckets of features from bedrock not in java and vice versa and when the two versions have completely different engines and structure from one another (see: quasi-conectivity)
They don't want to make Bedrock better, so they make Java worse as to superficially make Bedrock look less bad
And you know what's worse LEGACY CONSOLE REDSTONE WAS ALREADY THERE
The opposite also happens
@@fares_gamer603 And it also HAD Java redstone
@@EaglexEyeGaming literally where. I don't see it.
Whats funny is that a lot of people who know nothing about redstone reported the 1 gametick delayand no parity for bedrock and java as a bug, so mojang changed it without even CONSIDERING the redstone comunity
Maybe they regretted it
@@catsdogswoof3968 No, no regret. They have no regrets. They want Java to be like Bedrock and slowly doing just that.
Yall got it all wrong. They changed it because copper bulbs are toxic for steve to cosume obviously 💀
real
Real, now kids are safe frome consuming a lightbulb 😊
yeah kids should only be eating rotten flesh and spider eyes
And the eviles will spawn and consume your opinians and enslave you
can confirm I died after eating copper
Just one question for mojang. WHY WOULD YOU TRY TO MAKE JAVA AND BEDROCK COMPATIBLE IF THERE IS NO CROSS-PLAY?
After the first few snapshots I thought Mojang would make a great update after the failures since they had to split 1.17... then they came out of nowhere with 23w46a and everyone is mad again. Mojang, you never learn...
I mean what were they supposed to do
@@catsdogswoof3968not undo the 1gt delay?
@@catsdogswoof3968make java and bedrock have DIFFERENT copper bulb features
Just like observers.
@@cherricake1796 They botch Java for bedrock parity but have made no effort to add any bedrock exclusive features to java (armor stand posing, dyed cauldron water, etc)
Then they decided to cook some of the best stuff in the game for this upate by reworking bad omen and opening the door for many more structures to have ominous events of their own on top of some other cool stuff the update also added lol
Tfw Bedrock Edition is now officially ruining Java Edition
Us Bedrock users don't even get to have a say :( we want these changes too
As a bedrock player I’m officially switching to Java
@@bokiekitten4591 as opposed to unofficially?
@@Pickledotno one blames the players, it's entirely Mojang's fault for the absolute state bedrock is in, and at this point Java is getting pulled down with it.
@@Pigismal I have had like twenty people going dam you a bedrock player and then starts talking about every dam redstone feature we wished we had and makes it look like it’s my fault
As a bedrock player, I WISH JAVA WOULD FIX OUR REDSTONE.
Yeah, the only thing that threw me off from Bedrock is Java Redstone tbh. With Java Redstone you can make cool stuff with it but Mojang is just too lazy to change the Bedrock Redstones. Heck might cause Spaghetti coding at this point.
@@tsuaririndokuYou can make cool things with bedrock redstone too, it’s not bad just different. Just as with Java, all you need is experience and to practice.
It just different alot of cool things can be done with bedrock redstone
I don’t mind most of it, I just wish it was consistent. @@spacefun101
@@spacefun101 Bedrock Redstone isn’t as fun tbh. You can’t make a very effective flying machine or compact 3x3 piston door. I play test some of the Bedrock redstone and tries to learn and practice with it. But in the end, it just my preferred choice to stick with Java Redstones hence Bedrock redstone is a lot more unpredictable when making big redstone contraptions. Only thing I like about Bedrock is how easy it is to place blocks on creative mode. Plus I don’t like Bedrock’s observers which is suppose to be my fav, redstone type block in Java. It is too delayed which somewhat ruins some of the smooth contraptions. Plus, I keep seeing this, Bedrock Pistions are weird to use at times.
Haphazardly pursuing parody between Java and Bedrock Edition could be the worst decision Minecraft has ever made. Instead of making the best game they can, they make one version worse to match the other.
parity* I think the idea of both versions being the same is a good one. However, they seem to be choosing the easier way in most cases, which makes both games worse overall.
@@AndrewP24314minecrafy was never that yet look
@@AwesomeTMC I think parody works here, as Mojang has become a parody of its former self.
Honestly I'm sick and tired of mojang thinking that they know minecraft more then it's players when in reality the players know more about every single aspect of minecraft then them (and yes that includes the code)
They... do though
It's infuriating
@@catsdogswoof3968 not theyre not, notch is left, jeb is just supervising their employees, now jebs job is not even developing anymore. itis simple far as i can tell mojang newcomers employees now they Dont Know What Theyre Doing. please go do some search about mojang few years ago, go find some trailers in their channel, the era even notch still in this company, as long as you can often see them shows up coding more than todays trailers... all i can see today is this company product whether not quite the same as they advertized or is tooo difficult got lazy enough for them to fix anything, all i can trust their action, the future, is to add more blocks more feature. the game used to build as reliable, now i can see is corrupting it One By One from their root
@@a17waysJackinnI can barely read your comment (that says something) and no racism was banished from mojang don't worry Jeb is still sad though
After 10 years of minecraft modded experience... I will assure you, they don't fucken know their code. @@catsdogswoof3968 If DrZhark hadn't entered mojang, We wouldn't have horses, and probably he is charged in making mob ideas and implementations.
I'm still sad he makes 3 fun mobs for the community to choose only one of them. I hope he sometimes releases himself from this job that is killing his passion slowly since Microsoft adquired mojang.
Honestly, I'm repeatedly convinced that Bedrock's code is just a mess, since at least looking from an outside observer who knows how Java Minecraft works, Bedrock's system should be *easy* to add in odd game ticks. Java developers are quickly adding in lots of neat debugging tools (like official tick commands) and new stuff relatively quickly, whereas Bedrock gets things slower and (appears) clunkier.
I dunno, it feels like Mojang is digging their heels into Bedrock and it feels like largely a decision being made from high up, since the devs are given a lot of freedom and then seemingly having their decisions reverted on a whim.
I don't like it, but I'm not surprised.
Bedrock can actually be harder to work with, since its coding language is made for performance. Its also harder to mod
@@DecayedPagethe language shouldnt be a problem since it uses c++ but maybe the overkill code optimization. I'd be down for an updafe pause so the devs can fix and refactor the code so its easier to develop on wich maybe would imporve future update dev time
Despite being made with more modern tools and language the Bedrock is like an anchor made of rocks in a plastic bag.
some dude on Minecraft Feeback proposed that the bulbs could have a different time response based on its oxidation level : the more oxidized the bulb is, the slower it gets (for exemple, 1, 2 3 then 4 game ticks, or 0, 1, 2 and 3, or even 1, 2, 4, and 8). I think this could be a good alterative to the solution mojang gave, plus it would add a bit of variety to redstone systems, given you could always wax the copper bulbs so they don't change stage. [sorry foor bad english]
I’m a bedrock player, I don’t mind we get the 2 tick bulb & Java getting the 1 tick bulbs 🤷🏻♂️
I do
@@catsdogswoof3968Whys that?
Just thinking back to the old times, the good old days where Honey Blocks existed, and we said something like 'Make them not stick to slime blocks' and Mojang was like 'Yep! No problem.'
And they didn't stick. Whatever happened to those days?
I read this in Wheatley’s voice. Also I agree
Mojang went so downhill after 1.16. Makes me wonder if Microsoft has finally started calling the shots
As a bedrock player, just give bedrock the instant bulb, and let java have the 1 tick bulb. Timings are already not consistent between the two versions, why ruin java redstone by starting now.
Because the more they make differences between java and bedrock redstone the more bedrock players will get madder about it, Mojang doesn't want that which sadly is why they try to make them similar not by fixing bedrock but ruining java because thats the easier route.
mojang dosent listen to massive groups of people asking the same thing, but when one person complains about fireflies, mojang is like: Oh my bad lets ruin this update so this angry twitter user can be happier.
When a single troll bug report is filed, they ruin the bulb and crafter
You know it's not how it really works, right?
@@Yegor_Mechanicyes it is?
Its probably their opinian
You know that there is an internal reason they removed the fireflies and the excuse Agnes gave isn't true, right?
First time watcher here. You've got great presentation skills and good production value. I understood everything well despite being a novice with Redstone. The lil pop-up you added showing the Resource Pack you used is NOT something you see often and I just have to comment on how neat it was that you included that!
Mojang are never going to bridge the gap between bedrock and java redstone, like I cannot imagine they ever add quasi-powering into bedrock nor can they really remove it from bedrock for instance. Just let java players have 1gt, and if the problem really is that bedrock redstone needs an overhaul.... maybe give them an overhaul??? I'm sure bedrock players would love some consistent update orders
I feel they will remove the leaves and scafolding too
@@catsdogswoof3968 that’s not gonna happen
@@thatemocat When I read your comment, I first thought to myself “Yeah, of course they're not going to go out of their way to make redstone worse”. Then I realized...
It feels like going from 240hz monitor to 60hz monitor
As a redstoner the update broke my heart into a trillion pieces
i think that mojang should make it so the light bulb's delay will be the the oxidation of the bulb(1tick,2tick,4tick,8tick)
Interesting, I didn't think about making the delay double each time. That's a pretty unique solution. Still, I think the bulb should be instant by default so that it's consistent at first, but "degrades" over time. So the delays would be 0 tick, 1 tick, 2 tick, 3 tick. That gives players two odd delays to use!
One thing I can say about your content which I'm actually quite proud of, is how much you've matured. Your scripting feels much stronger with less 'salt' in it. It's quite refreshing and I'm really happy to see a flourishing channel out of you
If they really wanted to promote "consistency" and "tinkering," they could have varied the delay depending on the oxidization state of the bulb: 1 game tick delay per oxidization level, starting at 0 and ending with 3. That way it doesn't feel as random and haphazard, and it integrates the unique oxidization feature of the block into redstone in a really interesting way that gives the player more control.
It would even make sense logically: the old circuitry grows slower as the block grows more oxidized.
mojang on their way to ruin java edition for the sake of "bedrock parity" (they still haven't fixed the crossbow durability difference)
The Problem is that I think there will soon be a mod that reverts this, and it will be the Most Dowloaded mod.
I hope so
Probably not, since it's going to be only red stoners who would care enough to download it, which is a much smaller portion of the community. Probably not the most downloaded mod, but it will definitely be useful
This is such a simple change that it wouldn't even need a full mod, just a plugin.
Mojang acting like they didn't literally choose to make this parity problem, they choose again to ignore it repeatedly and act like ruining both games is somehow betting than fixing one.
Your also acting like it ruins the game
@@catsdogswoof3968You're clearly a bedrock player at this point you could listen to newton describing why parity actually ruins the game and you still wont listen XD.
@@catsdogswoof3968 cope harder
I say make the instant nature of the bulb exclusive to bedrock.
Java redstoners will remain happy
And UA-camrs will have another thing to slap onto their 100 things that make Bedrock unique from Java video, it's a win win...except for the bedrock users.
As someone who grew up with bedrock I cannot deny that we got the short end of the stick when it comes to redstone by a large margin. Like if fixing it is too hard then this feels like the least you can do for both parties.
Mojang really saw people enjoying themselves and said
“Nah. We can’t have that.”
This is a very well explained video, so it should reach non-redstoners as well. I normally don't comment feedback/ideas, because it can be perceived as rude, but I think a title that instead of just keyword "how", also has something like " - Redstone Timings Explained", could be better.
Niet echt denk ik want hij wil de aandacht juist op de copper bulb richten
Nah, current title is better
To get person click on video u need to spark curiousity via title
I'm so glad that you're pushing for it again, it make me sad that mojang persist not to respond and listen the redstone community
Mojang using the cosmic power of the universe to make the worst update decisions mathematically possible
I hope they change Bedrock's tick system to be like Java's so we can have the copper bulb back at its peak
It WILL break almost all of bedrocks already buggy redstone machines
I suspect it may not be possible for them to do, which is why they haven't done it yet.
@@FireroseNekowolfthey can do it whenever they want but it will destroy the fps bedrock gets it runs 2x as good by running 1/2 as much same with every thing else on bedrock it runs "better" because it does less. they don't want to remove the only selling point for bedrock so they can continue to scam people on the marketplace
@@billboeinwonder if they could make it togglable
As a redstoner from 1.8 this would have been an unintentional but super useful mechanic kind of like quasi connectivity
It’s not like the Minecraft devs are working on anything else. Wouldn’t be surprised if they showed most of what they had in that Minecraft live
Redstone is the one area that version parity needs to be broken
I disagree, 1.9 is still the most controversial update in the game because it forced everyone to relearn PVP. I think PVP parity is the biggest example, but there are many compounding smaller examples of unparity that would cause issues to unify.
every mojang employee:
"hey they like our update."
"oh... we cant have that"
Sorry. Noob question here🙋♀️ if bedrock and java redstone components are already different from each other, Why can't it just be on even ticks in bedrock and on odd ticks on java?
There's literally no reason why they couldn't.
mojang ruining the game is basically a law of physics now.
This truly is soo frustrating, but of course just in line with Mojangs habit of always doing the opposite of what people want!!
That's not even true. For example:
working pots, cherry forests, uses for copper(and tuff), new armadillo texture, the crafter and many other features from the newer updates were added because of the comunity.
@@Yegor_Mechanicnew armadillo is bald and some how more ugly
@@Yegor_Mechanicfound the mojang employee
@@AndrewP24314
You are just lying at this point :/
I saw many people online talking about how they wanted to see more uses for copper and wanted pots to contain loot. Cherry forest is popular on Minecraft Feedback.
I know there are many things Mojang should've done that they didn't, I know they constantly make many mistakes (it's the theme of the video), but it doesn't excuse lying and blaming them for the mistakes they didn't make.
@@cherricake1796
Unoriginal. "Hey, I found a Microsoft employee!" would be better imo
All arguments I have heard for why changing the copper bulbs to what they became was a good idea are terrible reasons for why to make it like that. And the only one that is close being sensible is also stupid. That one being: making it more in sync with how Bedrock edition works. The reason why this is stupid is: why not just fix bedrock edition to make it work like Java edition, rather than ruining Java edition to make them more alike. Also, if they really wanted it all to be consistent, then there is a lot of other stuff they should have looked at first. Making it consistent to bedrock like this is a fools errand.
You know if you dtopped complaining maybe they woukd do it but the moment your contraption breaks all of a sudden you change your mind
@@catsdogswoof3968 How would NOT complaining about this encourage Mojang to fix it? Also obligatory, stopped*, would*, there should be a comma between it and but, and periods exist. Stop acting like the mega-corporation is a tiny studio that can't handle feedback, perhaps come up with actual arguments, or at the very least spend more than 3 seconds putting together your keyboard smash so that it's almost somewhat legible.
@@theburgerboy5936 that guy is shilling for mojang, he wrote bunch of stupid comments like that defending bedrock edition
@@catsdogswoof3968 cope harder
I really do wish they would go back on those changes, however unlikely it would be
Before they go and "make copper bulbs consistent with other blocks", they should be making bedrock's redstone mechanics actually consistent.
What is the point of consistency when the rest of the mechanics in 1 version are vastly more inconsistent?
I've always felt that Mojang (Microsoft) see the quirks of Java that have developed into features as bugs that need to be "fixed". Minecraft is fundamentally a sandbox game so unintentional things that end up affecting the way the game plays are usually seen as optional and fun or useful and helpful by the community. Unfortunately the developers don't seem to quite feel the same way.
Why should redstone even be limited to 10 ticks in the first place? In fact why is bedrock so limited when it could have been better than java if it wasn't trying to be just like java? Because they are programming with a systems level language, now it will be harder to fix then doing it right in the first place.
Minecraft: adds a feature
Everyone: Super happy about it
Minecraft: that shouldn't be right!
I dont get their vision with parity... they remove good features on both versions to make them the similar, slightly worse versions... they cant keep doing that
Ugh... I want parity to to be ACTUALLY good, not parity for the sake of parity! When we say "we want parity," we mean we want waterlogged anvils in java, snowlogged flowers and grass in java, armorstands with arms in java, dyeable cauldron water in java, offhand compatibility for bedrock, more responsive mouse movements for bedrock, and any other really cool feature!
Bedrock's redstone is already super different (and debatably broken) compared to Java, so WHY did they feel the need to do this???
Honestly the management there is weird. The whole thing with the firefly in the past was one of the managers taking a complaint too seriously.
Ain't suprised if their idea of perfect parody despite coding limitations is influencing this despite the developers under them wanting otherwise.
Fireflies weren't removed because they were poisonous to frogs, it was because they were resource hogs and devs couldn't get them to work without unplayable lag
@@jonnyblaze2692 100 entities flying around aimlessly is not laggy, your world likely already had 80 loaded, just community manager took a complaint to heart.
Spawn 100 bats and tell me what happens.
I originally thought it was resources too but sadly no, management is just bad, for devs to be more public and in touch than the community manager is the problem.
@@jonnyblaze2692 source?
@@doctornobody105 straight from the developers mouths... Toycat just posted a video today with the responses to that question the devs.
Very well put together video. You made Redstone look easy, you're really good with explaining it in great detail on how it works. I hope Mojang reverts the Copper Bulb too, you redstoners are some of the most creative folks I've seen in this community.
This is just like the times they said they couldn't implement fireflies into the the game because "they're poisonous to frogs" or when they gave the excuse to slow down Elytra speed by 20% after the Caves and Cliffs update because "they wanted to allow the player to take in the new sights easier", all absolutely bullshit excuses around the fact that they were omitted/changed due to technical limitations. This I'd argue is even worse because it's not even due to any sort of technical limitations, they're just trying to treat Bedrock as their main game and therefore Java has to be more like it, not the other way around (even tho Bedrock's redstone is still inferior in so many ways).
I just have to correct you in soemthing.
Bedrock edition does actually run on 20 gameticks. Its just that some redstone components run on odd numbered ticks and some on even numbered ticks
i never said bedrock ran on 10tps, i said it was impossible to get odd gt delays
@@CraftyMasterman Oh okay mb. I shouldve listened more carefully.
That sounded saracstic but I wasnt being sarcastic
I have barely touched these new redstone components so I knew there was something people didn’t like about the new bulb but I didn’t actually know why. I thought they removed the entire t-flip-flop functionality. Glad to see that’s not the case, but the 1gt delay would be super nice to have. Hopefully mojang can understand this and restore it to it’s old version
I dont see why java cant just keep the copper bulb as it was while bedrock gets the updated one.
This reminds me of the young ahamkara's spine nerfs destiny had a while back. They were nerfed to fit better with the balance of pvp (like bedrock) and the pve side (java) also got nerfed because of it.
it really sucks that java is suffering from bedrock, however i just wanna point out that does not give anyone the right to bash on bedrock players. in a lot of videos where diffrences between bedrock and java were discussed, i saw comments that just straight up hated on the players. things like "i hate every bedrock player they are turning mojang into EA" lets not do that here
Didn't want to bash anything, I kept it as isolated to the problem as I could
@@CraftyMasterman no you didnt say anything bad but the comments tend to be toxic especially when it comes to bedrock & java
Fuck it, I'm a bedrock player and at this point *I* hate bedrock players
Tbf it might not be every player but microtransactions target the "whale" playerbase that play exorbitant amounts of money. I dont know if minecraft is like that considering their form of microtransactions is world downloads or skins and emotes. Their argument might make sense in a flawed way but even if its true not app players spend money and even less are "whales"
Still there are some people who hate just to hate those people's minds you can never change no matter what you say.
If every bedrock player quit bedrock and started playing Java, bedrock would cease to exist. All of this is caused by bedrock players.
I used to be a bedrock player on the Xbox and I converted and have never once looked back.
Sometimes you have to wonder what the point of this is. The community is SCREAMING at the top of their lungs that this is a terrible and completely unnecessary change, which it is. And yet, Mojang goes ahead with this anyway, almost as if they are paying literally zero attention to the community or otherwise intentionally trying to dismiss them. Does Mojang even listen? Do they even care? It’s a mystery with this level of negligence.
it is not a mystery. they do not care.
i don't play minecraft and idk why i got recomended this video but MOJANG PLEASE GIVE BACK THE ORIGINAL COPPER BULB
Why not just make the copper bulb have a different delay on bedrock like the observers
Yeah! That would be nice! We want Java to be better than Bedrock!
@@kate_isawesome1207 It already is
@@remu6841 Ok.
i mean the copper bulb is still useful, especially for computational redstone (also the copper bulb had a odd gametick on bedrock before the patch)
I doubt bedrock is the reason. rather I would say that it is due to the logical structures. The bulb seems to be designed to behave like a memory bit and I suppose the tick delay it has could be a drawback in logic mechanisms, so it makes sense (I assume they meant this by "consistency"). I don't think all the mechanics presented in the video were mojang's main idea. And yes, I know we had mechanisms for representing memory bits, but there's no reason to get too complicated when we've been given this block that clearly does it better and I also don't think it should be the primary method for getting odd ticks.
you can very easily access every tick in bedrock with command blocks but yea you can’t do that in survival
WHAT'S EVEN THE POINT THEN?!!?! 😭
I mean, why can't they change it if it's just a bug? I though that the game runned at other speed, BUT THIS IS EVEN DUMBER.
Mojang: "We won't add vertical slabs to encourage creativity"
Also Mojang: "We'll strip the redstone of all uniqueness to discourage creativity"
Thats pretty much what they did, yeah.
"strip redstone of *all* uniqueness"
Is an overstatement
@@Yegor_Mechanic you get the point
I mean yea that is consistant you have to do stuff yourself
@@AndrewP24314
How is it related to the comments?
10:31 actually it would take 2 redstone ticks or 4 gameticks to activate since because you're using a lever to power the redstone line, the comparator and redstone repeater actually have a zero tick delay (so setting the repeater to 3 ticks will actually only give it a 2 tick delay when powering it with a lever)
Hey I really like your incredible bedrock redstone system and I wanted to thank you
Honestly, what could have been done for both versions? Unoxidized and shiny copper bulb = no tick/instant. Each level of oxidation adds 1 tick delay. That way, we can have our instant copper bulbs, 1-tick copper bulbs, 2-tick copper bulbs, and 3-tick copper bulbs in one package. After all, a buildup of copper oxide _does_ reduce conductivity. Just wax the copper bulb once you get the desired oxidation level.
Mojang lied as naturally as they breathed, consistency is the most obvious lie for a redstoner, if all redstone features had to be consistent, decorated pots would have had a GUI like any other storage, but it doesn't, because it has a unique interaction, which makes it a valuable redstone block, sure the bulb has t-flip flop as a feature but if droppers hadn't had a randomized drop and instead just drops from top left to bottom right like the new crafter with hopper it, it would lose so much value as a redstone block.
What does pots have to do with this an also item frame and Chinle bookshelf and armor stands have no gui
And that's the same on all versions
The worst thing is: they said that redstone _never_ will get full parity between Java and Bugrock, but they are now breaking something in Java to make it consistent with Bugrock.
Or they just saw that "Ooh, the MC community is happy about something we do - let's change that!" and broke it just to make us less happy.
Using petty insults for Bedrock Edition isn't going to do anything and just angers people.
@@CNYTE
That's not an insult, it's a combination of the game's description and it's name.
@Lampe2020 Java has more bugs than bedrock, Java's bugs are just rebranded as features. Also the bugs that happen in bedrock like randomly dying only happen on awful devices, or if you're playing multiplayer with a bad wifi connection.
@@Tyranid_Hive_Mind stop cucking for bedrock bugs. also bedrock bugs being removed despite not being harmful is just as bad and happens all the time
@@sus6221 Stop cucking for Java bugs. All the unintended "features" on Java should be removed
Everyone should just always use a mod to revert mojangs stupid decisions and call that vanilla if java is going to continue being affected by bedrock in all these sorts of ways
Yea no for such a small feature no one will boycott it
@@catsdogswoof3968 I'm talking about ALL the dumb features, continue piling them onto a mod. Everyone use that mod. Ofc it wouldn't work, since everyone has their own opinions, some like features that others dont, but just wish it could
Although maybe it could if all the features could be toggled, so u can choose which dumb features to keep as is or revert/change
Its CRAZY to me that they want version parity for this when STEAK DOESNT EVEN HAVE VERSION PARITY
STEAK
As a Redstoner myself its funny hearing people say "bedrock is weird" and am not saying its better its just that java is the broken one its just that most people got used to the glitches that the intended Redstone is weird.... but as always "its not a glitch its an intended feature" that makes java redstone feel a lot better than bedrock
And then there is weird differences like how bedrock doesnt have a priority list based on the power source so its actually 100% random in bedrock and said tick difference btween observer in bedrock and java
a logic system needs to be consistent
bedrock redstone does not have a fixed subtick update order
the same contraption in the same place can do different things, just, randomly
How is that better? Java might be unintuitive, but it's behaving logically! If a logic circuit system is inconsistent, it is absolutely worthless.
holy shit bedrock is terrible
Yeah! I agree!
Why do I recognize the beat at the beginning of the video?
I think it's geometry dash intro song but only percussion
ah the classic, for the bedrock "parity" mojang just butchers anything that does not work on bedrock and refuses to port other small features to java.
I agree. Let's blame it on Bedrock, I blame everything bad on Bedrock anyway.
As a bedrock Redstone builder, I can personally agree with you that your observers are much faster than ours :D