OK, so i'm sick of waiting to be able to harvest ICE, and really don't want to break into creative to attain it, so the team and i build a pretty good harvester, and I got to thinking of actually pushing the ice the 200 or so blocks to a location then I can actually use them, then push them into place as needed, (I know insane right).
The harvester is working great, but that's when I start to encounter an issue I'm not really sure how to handle. ICE is transparent and thus doesn't allow redstone signals to pass through, and thus any sort of smart piston is out.
I have setup a kinda smart bud piston pusher so to speak, but I think this is rather laggy, and very kludgy. I also thought of doing some type of latch timer sequence, but the 200 line of redstone and repeaters just doesn't seem the way to go either.
Curious if anyone has a solution, or ideas on how to accomplish this. I'd be eternally grateful if someone could point me in the right direction.
OK, so i'm sick of waiting to be able to harvest ICE, and really don't want to break into creative to attain it, so the team and i build a pretty good harvester, and I got to thinking of actually pushing the ice the 200 or so blocks to a location then I can actually use them, then push them into place as needed, (I know insane right).
The harvester is working great, but that's when I start to encounter an issue I'm not really sure how to handle. ICE is transparent and thus doesn't allow redstone signals to pass through, and thus any sort of smart piston is out.
I have setup a kinda smart bud piston pusher so to speak, but I think this is rather laggy, and very kludgy. I also thought of doing some type of latch timer sequence, but the 200 line of redstone and repeaters just doesn't seem the way to go either.
Curious if anyone has a solution, or ideas on how to accomplish this. I'd be eternally grateful if someone could point me in the right direction.
Seems like you could use a similar design as the day light sensor. The idea behind it is that it uses redstone and a piston to detect the block ID change from a dirt block into a grass block.
You should be able to set something similar up to cause a piston to fire and trip a redstone circuit to push an ice block up when the water changed block ID from water source to ice block and reset again. Some things you will have to consider is that you will need to make it so that it will only fire on the one ice block around it and there there is enough thawed water source blocks (3 out of 4) in the rest of the 2x2 square surrounding the one that freezes, so that the water source will respawn when the piston resets... you may have to set up a delay in triggering again, as that block ID change could cause a rapid fire glitch in the piston sequence going from an air block back to a water flow block and again to a water source block.
I already stated that the ice harvesting was complete, that part was rather simple. A BUD was all that was needed.
What i need to do now is 'push' the ice a long, long, long ways to where i'm going to be needing them and would like some type of 'smart' piston as they won't work as ICE doesn't carry a redstone signal.
I have tested several types of BUD triggers so that when a piece of ice is pushed in front of it it will fire itself, but it uses quite a bit of resources. I could also send out a redstone signal along the path that the ice is traveling but that also would eat up a crapload of redstone and repeaters.
Gota keep in mind that I need the ice at least 200 to 300 blocks away from where its being created.
You can't harvest ice in our MC. If you want ice blocks, you must freeze water in a biome where that's possible, then push the ice blocks to where you want them. It's so ridiculously tedious that I quickly gave up on the idea of ice-bottomed water conveyors for things like cactus farms. They work so fantastically well in creative mode too. Damn shame.
Thanks cobra at least you seem to be able to read. I did figure it a pretty ingenuous method of transporting them over long distances thankfully. Hopefully next update silk touch does work on ice, its a damn shame such a useful block requires alot of work to actually use.
Well... you're going to have to do this in parts... because I don't think a redstone circuit/signal will register that many blocks away.
You could use a push-pull sled to move those iceblocks across that distance (up to 12 at a time).
I made one, that was pretty self sufficient set to a clock cycle to alternate which feed was getting redstone power and when that feed was cut.
Basic premise is:
point a normal piston in the direction you want to travel
load an opposing sticky piston against it pointing back toward the normal piston (pointing backward).
Have redstone leads go in on the sides to feed the sled as it travels, using a 2-beat firing sequence.
1 2 3 4 5 6 7 8 9 10
| | | | | | | | | |
[]||[]
1 fires, extends pushing sticky piston to #3 slot and retracts.
3 fires and retract, pulling normal piston to #2
2 fires, extends pushing sticky piston to #4 slot and retracts.
4 fires and retract, pulling normal piston to #3
3 fires, extends pushing sticky piston to #5 slot and retracts.
5 fires and retract, pulling normal piston to #4
4 fires, extends pushing sticky piston to #6 slot and retracts.
6 fires and retract, pulling normal piston to #5
etc.
Basically, you just want the odd lines firing alternate from the even lines, and can move blocks in both directions as long as the back end piston is normal, and the second block in the line is the sticky piston pointing backward.
I also thought of doing some type of latch timer sequence, but the 200 line of redstone and repeaters just doesn't seem the way to go either.
Since I don't know a way to externally (or mechanically) "move" a redstone circuit without it breaking, nor can pistons push more than 13 blocks at a time... I don't know how you are going to get around the "200 line of redstone and repeaters", unless you want to "break as you go" which is not the best option if you are moving a massive number of ice blocks...
Actually I chose to use 'several' buds, and to create a 'network' so to speak with various buildings staggered around 100 blocks in a outward spider like position. The ice arrives at each building and it stores around 80 ice blocks, once full it shuts off the incoming supply line and they continue onwards to the next supply base.
Each building houses a sand generator and can push ice to the general area. Sand can carry a redstone signal and thus can be detected within the system and disposed off automatically within its chain as new ice arrives to re-stalk its supply.
The best thing about this is that once the network is setup ice will be available to the entire map (cept desert areas), giving every member of the team access to ice, though you must still setup a small push system to push the ice to wherever the need is.
The harvester uses 6 ice buds creating ice blocks approximately every 30 seconds. The small snow biome is located almost directly in the middle of the map. The team consists of 6 of us, and thus the network is expanding pretty good, I figure about a week before we have ice available all over the map.
Its still a crapload of work 'just' to get ice but I think the rewards will be worth the effort.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The harvester is working great, but that's when I start to encounter an issue I'm not really sure how to handle. ICE is transparent and thus doesn't allow redstone signals to pass through, and thus any sort of smart piston is out.
I have setup a kinda smart bud piston pusher so to speak, but I think this is rather laggy, and very kludgy. I also thought of doing some type of latch timer sequence, but the 200 line of redstone and repeaters just doesn't seem the way to go either.
Curious if anyone has a solution, or ideas on how to accomplish this. I'd be eternally grateful if someone could point me in the right direction.
Seems like you could use a similar design as the day light sensor. The idea behind it is that it uses redstone and a piston to detect the block ID change from a dirt block into a grass block.
You should be able to set something similar up to cause a piston to fire and trip a redstone circuit to push an ice block up when the water changed block ID from water source to ice block and reset again. Some things you will have to consider is that you will need to make it so that it will only fire on the one ice block around it and there there is enough thawed water source blocks (3 out of 4) in the rest of the 2x2 square surrounding the one that freezes, so that the water source will respawn when the piston resets... you may have to set up a delay in triggering again, as that block ID change could cause a rapid fire glitch in the piston sequence going from an air block back to a water flow block and again to a water source block.
What i need to do now is 'push' the ice a long, long, long ways to where i'm going to be needing them and would like some type of 'smart' piston as they won't work as ICE doesn't carry a redstone signal.
I have tested several types of BUD triggers so that when a piece of ice is pushed in front of it it will fire itself, but it uses quite a bit of resources. I could also send out a redstone signal along the path that the ice is traveling but that also would eat up a crapload of redstone and repeaters.
Gota keep in mind that I need the ice at least 200 to 300 blocks away from where its being created.
Why not make a 1 block platform, put a snow golem on it, and build a fence/barrier at his head height (so you can get to his feet).
Then just walk up to it and shovel the snow off the ground that he constantly refreshes because he can't move around.
That's how you make an infinite snow generator.
What problem are you trying to solve that's not this?
Snow golems won't give you ice, unfortunately.
You could use a push-pull sled to move those iceblocks across that distance (up to 12 at a time).
I made one, that was pretty self sufficient set to a clock cycle to alternate which feed was getting redstone power and when that feed was cut.
Basic premise is:
point a normal piston in the direction you want to travel
load an opposing sticky piston against it pointing back toward the normal piston (pointing backward).
Have redstone leads go in on the sides to feed the sled as it travels, using a 2-beat firing sequence.
1 2 3 4 5 6 7 8 9 10
| | | | | | | | | |
[]||[]
1 fires, extends pushing sticky piston to #3 slot and retracts.
3 fires and retract, pulling normal piston to #2
2 fires, extends pushing sticky piston to #4 slot and retracts.
4 fires and retract, pulling normal piston to #3
3 fires, extends pushing sticky piston to #5 slot and retracts.
5 fires and retract, pulling normal piston to #4
4 fires, extends pushing sticky piston to #6 slot and retracts.
6 fires and retract, pulling normal piston to #5
etc.
Basically, you just want the odd lines firing alternate from the even lines, and can move blocks in both directions as long as the back end piston is normal, and the second block in the line is the sticky piston pointing backward.
Since I don't know a way to externally (or mechanically) "move" a redstone circuit without it breaking, nor can pistons push more than 13 blocks at a time... I don't know how you are going to get around the "200 line of redstone and repeaters", unless you want to "break as you go" which is not the best option if you are moving a massive number of ice blocks...
Each building houses a sand generator and can push ice to the general area. Sand can carry a redstone signal and thus can be detected within the system and disposed off automatically within its chain as new ice arrives to re-stalk its supply.
The best thing about this is that once the network is setup ice will be available to the entire map (cept desert areas), giving every member of the team access to ice, though you must still setup a small push system to push the ice to wherever the need is.
The harvester uses 6 ice buds creating ice blocks approximately every 30 seconds. The small snow biome is located almost directly in the middle of the map. The team consists of 6 of us, and thus the network is expanding pretty good, I figure about a week before we have ice available all over the map.
Its still a crapload of work 'just' to get ice but I think the rewards will be worth the effort.