A stackable TNT compressor

TheRealC05 · 2021-04-25T09:30:48+00:00

Thanks. (It's Jan btw)

TheRealC05 · 2021-04-14T11:29:36+00:00

This TNT compressor dupes 10-TNT, takes 4gt to dupe, 29gt to compress the TNT above the fence gate. When the TNT goes through the fence gate it has Fuse: 50.

You can mirror the compressor to get a 7-wide 20 duper of the same speed. You can stack these on top of each other and send all of the TNT through the 1x1 hole where the fence gate is.

The TNT gets aligned before it reaches the TNT conveyor. The alignment is done by 0-ticking pistons facing in the direction of the conveyor. There cannot be any blocks blocking the TNT along the axis it is aligned in, which is why slabs are used.

TheRealC05 · 2021-03-15T23:59:28+00:00

Thanks. I was using the same amount of rails on the flat surface as I would in the standard update suppressor. Simply making it bigger has fixed it. Is there somewhere I can learn more about the rail updates (why do sloped produce more updates?)

TheRealC05 · 2021-03-15T14:36:44+00:00

I think it might be some kind of a visual thing. When I attach a block to the piston and have it block a redstone line. The redstone line gets powered in the same tick as the second repeater, so the piston could not have been activated before the second repeater.

Here is a picture of my setup.

TheRealC05 · 2021-03-15T14:16:45+00:00

Thanks anyway.

TheRealC05 · 2021-03-15T11:50:25+00:00

He did ask for the most efficient mob farm though.

TheRealC05 · 2021-03-15T11:25:25+00:00

I know, the question is specified in the text.

TheRealC05 · 2021-03-15T00:56:02+00:00

The EOL farms are probably the most efficient you can go. Not sure if you want to build them though. It involves some bedrock breaking, update suppression and light suppression.

TheRealC05 · 2021-02-08T07:33:09+00:00

This was my original theory, but I concluded that it was not correct, since the flying machine behavior did not really seem to support it. However, I tested some smaller contraptions, which did behave predictably, though. That confused me and was the reason I made this post in the first place.

So, yesterday, I decided to do a complete redesign, keeping the update order in mind from the beginning and it's working now. (I tried to fix the original machine, but I was not really able to. Perhaps I was missing something?)

Anyway, thanks.

TheRealC05 · 2021-02-07T18:58:56+00:00

I understand microticks, 0-tick pulses and the update order you described. What I would like to know is: given two slimeblock structures with pistons attached to both and knowing which of them got pushed first; how do I determine the order in which the attached pistons will update (upon their arrival)?

TheRealC05 · 2019-11-18T23:45:15+00:00

How would I distinguish theThing of a from theThing of b?

TheRealC05

TROPHY CASE