Could you provide a screenshot. I'm not the greatest at comprehending text instructions.
Cobble Compression
- Thread starter mattp_12
- Start date
Here are the ender chests used for the cobble generation. Each chest have a matching ender chest in the first crafting step (next picture).
Here is the first part of the chain of in-world crafting setups, with the matching ender chests.
After the first crafting step you need pretty high speed item transfer, so I use four routers there to distribute to the next chests.
What mod are the routers from?Here are the ender chests used for the cobble generation. Each chest have a matching ender chest in the first crafting step (next picture).
Here is the first part of the chain of in-world crafting setups, with the matching ender chests.
After the first crafting step you need pretty high speed item transfer, so I use four routers there to distribute to the next chests.
Can't you just use one ender chest hooked to the cobblegen and have the other nine all the same color
SFM and XU are far and away the fastest most compact method: http://imgur.com/a/3Ldgh
This setup will make an octuple compressed cobble every 13 hours, uses no power, fits in a 3x3x1 block space, and takes about as much processor time as 15 vanilla chests just sitting there.
This setup will make an octuple compressed cobble every 13 hours, uses no power, fits in a 3x3x1 block space, and takes about as much processor time as 15 vanilla chests just sitting there.
Yes, I think that should work as well. The purpose of having 9 separate pairs was to have one dedicated cobble gen per chest in the first crafting step.
Since a cyclic assembler can perform one craft per tick we should be able to feed it 180 cobble/second. One item transfer node with 20 speed upgrades, 1 stack upgrade, and 63+63+54 world interaction upgrades keeps a cyclic assmebler busy 100% of the time. If I add one more world interaction upgrade, the cyclic assembler starts building up a backlog of cobble.
I should point out that that maxed out cyclic processor consumes 820 microseconds of the game tick loop while a machine inventory manager which is compressing 960 cobble/second is only taking 0.257 microseconds. A really massive cobblegen using TE4 can lag out my machine but there is no chance on earth a SFM setup can.
I just finished building a compression system with 8 iron chests with SFM compressing the cobble lol. I'll build this and I'll compare.SFM and XU are far and away the fastest most compact method: http://imgur.com/a/3Ldgh
This setup will make an octuple compressed cobble every 13 hours, uses no power, fits in a 3x3x1 block space, and takes about as much processor time as 15 vanilla chests just sitting there.
I really hope I'm not breaking the rule on grave digging, but:
I copied your setup but instead used an ender chest. It lets me use all four sides for cobble gen, and I have a matching ender chest that imports the final result (septuple compressed) into my AE system, which then has crafting patterns for de-compressing it when I need it.
Thank you for this design! It was also the first time I ever used SFM
Your new avatar:I really hope I'm not breaking the rule on grave digging, but:
I copied your setup but instead used an ender chest. It lets me use all four sides for cobble gen, and I have a matching ender chest that imports the final result (septuple compressed) into my AE system, which then has crafting patterns for de-compressing it when I need it.
Thank you for this design! It was also the first time I ever used SFM
