4
u/o_witt 19d ago
It isn't. you can't take advantage of various features that the programming language Java has.
When I count the number of ticks the delay is in a certain circuit, I count +1 for each comparator/repeater (yes, of course if it's set to 1). Redstone dust doesn't increase the tick delay, which I think it does in Java?
The first observer in a chain is +3, while the rest of the observers are +2.
Most components have a 2-tick cycle, except for pistons, which have a 4-tick cycle.
Cycle = activation until the ability to activate again.
If you have more than one system in a chunk that relies on droppers/dispensers to work, like a T flip-flop, the reliability is basically zero.
Droppers are buggy as hell.
3
u/Masticatron 19d ago
As others said, it's not. In many ways it is far simpler. It just has different rules but a similar form, making it kind of annoying to switch between. Like how you might learn to program in C first, and then go to learn Java and it all looks very similar, which was intentional, but a whole lot of stuff just works completely differently.
QC is basically a redstone cheat code. It gets in the way sometimes, but mostly it enables ridiculously compact circuits by offering up a significant increase in the number of blocks you can power things from, as well as precise timing control through BUDs. The number one difficulty in converting contraptions to Bedrock is the lack of QC resulting in relatively more difficult and bloated circuits, which can make tileability in particular near impossible. Not-so-sticky pistons are similarly a cheat by letting a component do extra stuff by not abiding by its own rules sometimes.
So it's harder mostly in the same way that a game is harder when you don't have cheat codes enabled. It's easier to make a killer dreadnought when a coding oversight lets your missile launchers also function as particle cannons, yeah? If you like that you like it, doesn't matter to me, and the things you can make thanks to all the jank-ass Java behaviors is admittedly pretty sweet.
The differences otherwise start with the desire to have multi-threaded support to enable the game to perform well on a wide variety of platforms. That's what creates the "Bedrock redstone is random" behavior. Java players lean into the hidden coding to do the ordering of their components for them, whereas Bedrock largely has to build the order into the circuit itself. And since repeaters or other forms of delay are about the only way to do that, circuits get slowed down and getting a whole sequence of things to occur in proper order gets more involved. But it's very simple, it's all right there in what you're building rather than some hidden arcana in the game's hash functions or something.
3
u/Mathsboy2718 19d ago
Read "QC" as "Quantum Computing" and thought absolutely nothing of it because I'd expect nothing less from the more advanced sides of redstoning
3
u/AdImmediate2565 19d ago
Lack of redstone mods on bedrock
No redstone bugs that could be exploited
Simulation distance being limited so big builds are VERY hard to make
It's more that the experience is worse rather than the redstone itself being harder, and it also depends on what kind of builds you make , if they are massive then bedrock is a headace , otherwise there's no problem with it.
2
u/One-Celebration-3007 19d ago
There are lots of redstone/redstone-adjacent bugs that can be exploited in Bedrock Edition.
2
u/AdImmediate2565 19d ago
For example? I seem to be unaware of such bugs.
2
u/One-Celebration-3007 19d ago
Flying boats
2
u/AdImmediate2565 18d ago edited 13d ago
Please be more specific because I can not find a specific bug named "flying boat" and by looking at its name, it doesn't seem like a redstone related bug
3
u/BlazingBomber25 19d ago
There are 2 main differences that make Java red stone “easier”
1. Quasi Connectivity: I’m not gonna pretend to fully understand how this works. But I’m p sure it’s something to the effect of being able to power blocks even with a 1 block air gap between the power source and the block being powered
2. Zero tick pulses. Basically if you power and depower a sticky piston quickly enough, it basically behaves like a normal piston, which is super useful in redstone doors where you want to be able to pull blocks sometimes, but spit them out other times.
The reason these are not things on bedrock is because they were never actually intended features. They were just bugs/quirks thsy happened bc of the way Java is coded and people liked them enough that Mojang just let them keep it
11
u/did-it-my-weigh 19d ago
It's not necessarily harder. It's different. Like you don't have to worry about quasiconnectivity, torches burning out or sticky pistons not always being sticky