Do you know how to adapt this to work on bedrock? I’ve tried adapting the monostable circuits but timings appear to be off. Items get spit out, sometimes items are taken from the wrong boxes and the shulkers aren’t splitting correctly
@@exnoh_ nice one, really appreciate it, tried using an observer/piston monostable for the bottom and switched the note lock to a redstone lamp, everything is technically working I think. Just all timings off and can’t work it out
@@adamwhittam3474 it looks like theres a bug on bedrock with observers taking 2 ticks of delay instead of java's 1 tick. i replaced the monostable circuit thats there with a rising edge monostable from bedrock - redstone dust(unpowered) where the target block and torch is, piston with block, repeater, block, rails (observer under). i then also changed up the observers to the first shulker-breaking piston - it was receiving 4 ticks instead of 2 because of this bug, so i used one observer (for 2 ticks) and looped the signal round with dust. this helped with the timing quite a bit, so i imagine that's the issue with the rest too
@@exnoh_ wow didn’t expect you to have tested so quick! Appreciate it, so basically I should just have to half the number of observers used? Feel like this cold get extremely complicated to sort😂
hypothetically that should fix it, yes! the observers are all luckily in more open spaces so it wont be as compact but hopefully should function the same
I've noticed it breaks if it gets a few positives in a row - Doesn't break, will just skip the next number of positive results until there is a negative between them What Will break it is searching for something that stacks to 16
huh interesting. with the first thing, maybe double check the observers going to the piston by the barrels; im guessing that problem might be that delay (if that isnt the issue you could try adding extra observers there for more delay and test that).
Should the piston at 4:36 be a sticky piston instead of a normal piston? I tried with a normal piston but it wouldn't work.
yes it should! good spot, my bad. the woes of multiple takes
Which one should be a sticky piston?
the one at the bottom of the device, it has a repeater going into the block on top of the piston. check the timestamp above for a visual :)
A comprehensive tutorial! Something that Etho hasn't done in years! /j
wh…how??? You’re a god of redstone Ex
You got this tutorial made so fast!
Can you make a world download
cool
Thank you!
Do you know how to adapt this to work on bedrock? I’ve tried adapting the monostable circuits but timings appear to be off. Items get spit out, sometimes items are taken from the wrong boxes and the shulkers aren’t splitting correctly
ill look into it and get back to you if i manage to get it working - im not all too familiar with bedrock redstone but ill have a play around
@@exnoh_ nice one, really appreciate it, tried using an observer/piston monostable for the bottom and switched the note lock to a redstone lamp, everything is technically working I think. Just all timings off and can’t work it out
@@adamwhittam3474 it looks like theres a bug on bedrock with observers taking 2 ticks of delay instead of java's 1 tick.
i replaced the monostable circuit thats there with a rising edge monostable from bedrock - redstone dust(unpowered) where the target block and torch is, piston with block, repeater, block, rails (observer under).
i then also changed up the observers to the first shulker-breaking piston - it was receiving 4 ticks instead of 2 because of this bug, so i used one observer (for 2 ticks) and looped the signal round with dust. this helped with the timing quite a bit, so i imagine that's the issue with the rest too
@@exnoh_ wow didn’t expect you to have tested so quick! Appreciate it, so basically I should just have to half the number of observers used? Feel like this cold get extremely complicated to sort😂
hypothetically that should fix it, yes! the observers are all luckily in more open spaces so it wont be as compact but hopefully should function the same
Redstone woow cool
I've noticed it breaks if it gets a few positives in a row - Doesn't break, will just skip the next number of positive results until there is a negative between them
What Will break it is searching for something that stacks to 16
huh interesting. with the first thing, maybe double check the observers going to the piston by the barrels; im guessing that problem might be that delay (if that isnt the issue you could try adding extra observers there for more delay and test that).