Xirema

Please find a new tutorial. If you want, I'll even write one up for you. The information on that page is not only outdated in a few sections, but also has tons of formatting problems.

Then you don't understand how power works. All generators, machines, storage units take and receive power in "packets" of some variable size. Solar panels output packets of size 1, regular coal/charcoal/fuel generators output in packets of size 10. As packets travel down cables, they lose energy at a certain rate, but packets only carry integer-sized amounts of energy, so no reductions occur until you incur a single loss of 1 EU/p (or more). In the case of (insulated) copper cable, you lose .2 EU/p/b, which is to say that for every packet that travels through the cable, you lose .2EU per block of cable. Since Solar Panels output at 1EU/t (or 1EU/p, though do NOT confuse the two) the current is only able to travel 5 blocks in (insulated) copper cable before losing all of its power. If you want it to make it through the copper cable, you need to put a batbox in front of the panel first before it goes to the machines, and before the 5-cable limit at which point the resistance is too high for the current to make it. Once it makes it past the batbox, it will be in packets of size 32EU/p, which can easily bridge the length of cable you've provided. Alternatively, use tin cable, which can handle the output from solar panels (it has a limit of 5EU/p, Solar Panels are only 1EU/p) but unlike copper cable, they only reduce .025EU/p/b, which means that a 1EU packet can travel 40 blocks before losing all its power. Tin cable can't handle charcoal generators though (10EU/p) so you'll have to experiment and find an appropriate solution. One more thing: Don't use Solar panels without a storage unit. You need a way to store energy overnight when the panel isn't working, or else if it starts to rain on the server.

They also take lava directly from buildcraft pipes, but clearly that wasn't the desired solution. ;)

Hmph. The only thing I can suggest at this point is perhaps using buckets, and then using an auto-crafting table from Buildcraft to move the lava into the cells, returning the empty buckets to the deployer. I personally dislike that particular solution, but it would work.

If you're running any redpower device, don't set the time to less than half a second. The logic boards can usually handle < .500 seconds, but most of the machines can't. EDIT: Also, what is the deployer targeting? A BC tank? Direct lava?

I assume the problem is extracting the full cells after the fact? Use a retriever or a cleverly placed filter to remove them.

Buildcraft pump -----> BC tanks Tanks -------> RP Deployer w/Tin Cells Extract Lava Cells with Filter/Retriever ---------> Ender Chest EnderChest --------> Same code in overworld Overworld Enderchest --------> Whatever the hell you want lava for The only limitation is that you need to put world anchors, or else keep people present near all the important components.

I don't own the server. I'll ask my friend what they're using.

I'm not able to do a lot of debugging on this issue, since rebuilding my reactor every time this happens is expensive, but I'm finding that if I log out when I have a reactor running, it will have more heat than it should when I log back in (sometimes it damages me for a few seconds before it cools off properly), and if I'm logged out more than a minute, (It generates like 1.5k heat per second, I cool it with ice blocks, so that much heat == dead) the reactor explodes immediately after I log back in. I know the code for IC2 is pretty awful in general (inefficient, unoptimized, etc.) but this seems like a pretty critical flaw. Is there any way the code could be fixed to prevent this?

Most minecraft accounts have been migrated, try using your e-mail address instead of your username.

Are they actually failing, or do they just have the appearance of failing? There's a graphical bug where items will appear to be travelling down the wrong pipe after passing through a diamond pipe, but they still end up in the correct location anyways.