I've been playing with finite water in my world and it's quite fun. It causes water to become a resource that you must properly manage instead of a mindless annoyance that only requires spamming Aqueous Accumulators.
People may be opposed to it because it leaves ugly water messes from draining oceans. That is true; don't drain oceans. Although it is easier, it's not a great idea. I would recommend draining lakes and rivers. This option just leaves sand/dirt holes and shallow ravines, which look much nicer than a messed up ocean. Also, observing drained lakes and rivers from your progress looks great.
If you are draining a lake or river, keep in mind that the BuildCraft Pump's maximum range is 64 blocks from each side. If the water you are draining extends further than this, build a dam between them so it doesn't make a mess. Ensure that the dam separates the water completely; right down to the ocean floor. If the water is touching, the pump will be able to suck it up. If you block it with solid blocks, it will stop.
The lines represent some possible dam placements. I will use the purple line in my example.
Dam is done. Of course, this is a quick and cheap dam, you can make yours look prettier.
Pump aftermath
Water gained
How to do it below. The CodeChickenCore and BuildCraft configs are required because they affect water in the world. The rest are optional because you can just choose not to use water generators, but this disables them if you lack self control.
What do you guys think?
People may be opposed to it because it leaves ugly water messes from draining oceans. That is true; don't drain oceans. Although it is easier, it's not a great idea. I would recommend draining lakes and rivers. This option just leaves sand/dirt holes and shallow ravines, which look much nicer than a messed up ocean. Also, observing drained lakes and rivers from your progress looks great.
If you are draining a lake or river, keep in mind that the BuildCraft Pump's maximum range is 64 blocks from each side. If the water you are draining extends further than this, build a dam between them so it doesn't make a mess. Ensure that the dam separates the water completely; right down to the ocean floor. If the water is touching, the pump will be able to suck it up. If you block it with solid blocks, it will stop.
The lines represent some possible dam placements. I will use the purple line in my example.
Dam is done. Of course, this is a quick and cheap dam, you can make yours look prettier.
Pump aftermath
Water gained
How to do it below. The CodeChickenCore and BuildCraft configs are required because they affect water in the world. The rest are optional because you can just choose not to use water generators, but this disables them if you lack self control.
minecraft/config/CodeChickenCore.cfg
#If set to true two adjacent water source blocks will not generate a third.
finiteWater=true
minecraft/config/buildcraft/main.conf
# set to true if the Pump should consume water
B:consumeWater=true
minecraft/config/cofh/ThermalExpansion.cfg
B:Machine.WaterGen=false
minecraft/config/railcraft/railcraft.cfg
B:machine.alpha.tank.water=false
minecraft/config/powercrystals/minefactoryreloaded.cfg
B:WeatherCollector.Recipe.Enabled=false
minecraft/config/minetweaker
Forestry's raintank does not have a config option that I can locate. Add the below line to the cfg file. Note that this is the ID in Monster, if it's different in your package use that instead.
recipes.remove(<1406:1>);
#If set to true two adjacent water source blocks will not generate a third.
finiteWater=true
minecraft/config/buildcraft/main.conf
# set to true if the Pump should consume water
B:consumeWater=true
minecraft/config/cofh/ThermalExpansion.cfg
B:Machine.WaterGen=false
minecraft/config/railcraft/railcraft.cfg
B:machine.alpha.tank.water=false
minecraft/config/powercrystals/minefactoryreloaded.cfg
B:WeatherCollector.Recipe.Enabled=false
minecraft/config/minetweaker
Forestry's raintank does not have a config option that I can locate. Add the below line to the cfg file. Note that this is the ID in Monster, if it's different in your package use that instead.
recipes.remove(<1406:1>);
What do you guys think?