I once came up with my design for an instant repeater. Place a sticky piston facing horizontally. Place a redstone block in a way that the SP pushes it when powered. Place a normal block horizontally adjacent to the SP not on the opposite side. Place a redstone dust block on the block and next to it and the RB. It will activate the SP but should instantly (because the piston retraction is instant) stop powering it. I don't know why but the RD will be active for a tick and the piston won't spit out the RB. If you attach another SP to the redstone line, it will spit its block out, and if you make two such contraptions sharing the same redstone line, one of them will work (MCJE is asymmetric). If you connect a redstone wire to the piston and another one to where the RB is when it's powered, it will act as an instant repeater for signals that can be either active or changing quickly between active and inactive states; any other signal will be converted to such. There is a version that doesn't use the phenomenon of not spitting out the block, but I haven't tested it.
I actually made this exact thing(edit not exact but similar concept I think) (it uses a block, Redstone line, sticky pistons, and slime/honey with Redstone block that touches Redstone line when retracted, allowing it to quasi-power/unpower without updating, then extending/retracting all at once when updated When any piston gets updated, they all do, thoigh I haven't yet found a video with it I was wondering if anyone also came up with the idea
@@orisphera well the slime/honey is for a longer line since it will self quasi-power/unpower, it only really needs to have it every 14 or 16 pistons though, but it is an instant design (though the big part is pretty chunky and was built with pretty rudimentary understanding of quasi-connectivity) I'll try to type how to build the big part of it (might need to make it slightly taller though, I'll have to double check) |red |red block|slime| |block|air. |slime| |air |piston> |slime| Alternatively if it needs to be taller |red block|slime. |air. | |red |slime. |slime| |block. |air. |slime| |air |piston> |slime| Edit 2, I think you may be thinking of something like ruclips.net/video/r5Wfzfq9kKs/видео.html or ruclips.net/video/eH3sg97DW6w/видео.html which might be modifiable to make an instant pulse, but idk
Should not be a problem. Quasi connectivity is (according to the devs) going to be staying in the game. As for redstone redirection not giving updates, I am not sure why they would change that, but you never know. I use it anyway, because I know that nearly anything redstone related is prone to breaking eventually. Take the time when they changed redstone in 1.16. A lot of contraptions had to be fixed or redesigned. Back to the topic of QC, I would say that it is pretty safe to say that it will stay, and if they do remove it, it would be one of their stupidest decisions, because the whole technical and redstone community depend on it and it would cause an uproar. Remember when they removed sticky pistons spitting out blocks in the 1.13 snapshots? It was added back in the next one. As a conclusion, I would say that it is pretty safe to use it.
@@amplitudemc am.... actually i stopped minecraft at 1.8.x then i continued back at 1.15.2. So i havent heard about the sticky piston thing, what happened tho????? Im also more on command blocks that time, instead of using pure redstone on a combination lock i made, I used more command blocks instead with a bit of redstone
@@noname-codm4590 About the sticky pistons, in the 1.13 snapshots, Mojang decided to start messing around with the pistons, and at one point removed sticky pistons spitting out their blocks. About the command blocks, I think that's really cool!
@@noname-codm4590 Sorry, it means when a sticky piston is powered with a short pulse (less than 3 gameticks), it will not retract the block back. Because normally a sticky piston will pull the block in front of it back, but if it is a short pulse, it will not pull it back.
I have an advice:
/gamerule doMobSpawning false
and all mobs magically gone
I once came up with my design for an instant repeater.
Place a sticky piston facing horizontally. Place a redstone block in a way that the SP pushes it when powered. Place a normal block horizontally adjacent to the SP not on the opposite side. Place a redstone dust block on the block and next to it and the RB.
It will activate the SP but should instantly (because the piston retraction is instant) stop powering it. I don't know why but the RD will be active for a tick and the piston won't spit out the RB. If you attach another SP to the redstone line, it will spit its block out, and if you make two such contraptions sharing the same redstone line, one of them will work (MCJE is asymmetric). If you connect a redstone wire to the piston and another one to where the RB is when it's powered, it will act as an instant repeater for signals that can be either active or changing quickly between active and inactive states; any other signal will be converted to such.
There is a version that doesn't use the phenomenon of not spitting out the block, but I haven't tested it.
I actually made this exact thing(edit not exact but similar concept I think) (it uses a block, Redstone line, sticky pistons, and slime/honey with Redstone block that touches Redstone line when retracted, allowing it to quasi-power/unpower without updating, then extending/retracting all at once when updated
When any piston gets updated, they all do, thoigh I haven't yet found a video with it
I was wondering if anyone also came up with the idea
@@raymondwiggins354 I think you read my comment incorrectly because I didn't use slime/honey
@@orisphera well the slime/honey is for a longer line since it will self quasi-power/unpower, it only really needs to have it every 14 or 16 pistons though, but it is an instant design (though the big part is pretty chunky and was built with pretty rudimentary understanding of quasi-connectivity)
I'll try to type how to build the big part of it (might need to make it slightly taller though, I'll have to double check)
|red |red block|slime|
|block|air. |slime|
|air |piston> |slime|
Alternatively if it needs to be taller
|red block|slime. |air. |
|red |slime. |slime|
|block. |air. |slime|
|air |piston> |slime|
Edit 2, I think you may be thinking of something like ruclips.net/video/r5Wfzfq9kKs/видео.html or ruclips.net/video/eH3sg97DW6w/видео.html which might be modifiable to make an instant pulse, but idk
@@raymondwiggins354 Can you send a link to a screenshot of your contraption on Imgur please?
@@orisphera it should be on reddit now. Comment with the link keeps getting removed though...
bedrock?
does not work on bedrock :(
@@Novacreeper231 why does the video not mention it's ONLY for Java? And is there really no option for Bedrock?
Great video keep it up👍
Thanks!
Is there any reason all those use BUDs and yet the description/title doesn't specify Java-only?
m o b s
So cool!
Are these budded pistons going to be a problem in future updates?? I want to pretty much make redstone inmy singleplayer world future-proof
Should not be a problem. Quasi connectivity is (according to the devs) going to be staying in the game. As for redstone redirection not giving updates, I am not sure why they would change that, but you never know. I use it anyway, because I know that nearly anything redstone related is prone to breaking eventually. Take the time when they changed redstone in 1.16. A lot of contraptions had to be fixed or redesigned. Back to the topic of QC, I would say that it is pretty safe to say that it will stay, and if they do remove it, it would be one of their stupidest decisions, because the whole technical and redstone community depend on it and it would cause an uproar. Remember when they removed sticky pistons spitting out blocks in the 1.13 snapshots? It was added back in the next one.
As a conclusion, I would say that it is pretty safe to use it.
@@amplitudemc am.... actually i stopped minecraft at 1.8.x then i continued back at 1.15.2. So i havent heard about the sticky piston thing, what happened tho?????
Im also more on command blocks that time, instead of using pure redstone on a combination lock i made, I used more command blocks instead with a bit of redstone
@@noname-codm4590 About the sticky pistons, in the 1.13 snapshots, Mojang decided to start messing around with the pistons, and at one point removed sticky pistons spitting out their blocks. About the command blocks, I think that's really cool!
@@amplitudemc not entirely sure what “spitting out blocks” means lol. Also thanks.
@@noname-codm4590 Sorry, it means when a sticky piston is powered with a short pulse (less than 3 gameticks), it will not retract the block back. Because normally a sticky piston will pull the block in front of it back, but if it is a short pulse, it will not pull it back.
No longer functional, unfortunately.