Version of Mekanism: 7.0.0.82

Even if it is full of power and not processing items, it continues to use power from the system. Our power generation is currently coming from Thermal Expansion, but even if a fully charged energy cube is put on its own separate grid, the metallurgic infuser will pull power from the cube even if it doesn't need it. Also, I cannot test other machines in single player because single player crashes after placing down any Mekanism block with the following:

[18:38:32] [Server thread/ERROR]: There was a critical exception handling a packet on channel MEK
java.lang.NullPointerException
at cpw.mods.fml.common.network.FMLOutboundHandler$OutboundTarget$6.selectNetworks(FMLOutboundHandler.java:158) ~[FMLOutboundHandler$OutboundTarget$6.class:?]
at cpw.mods.fml.common.network.FMLOutboundHandler.write(FMLOutboundHandler.java:273) ~[FMLOutboundHandler.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeWrite(DefaultChannelHandlerContext.java:644) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.write(DefaultChannelHandlerContext.java:698) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.write(DefaultChannelHandlerContext.java:637) ~[DefaultChannelHandlerContext.class:?]
at io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:115) ~[MessageToMessageEncoder.class:?]
at io.netty.handler.codec.MessageToMessageCodec.write(MessageToMessageCodec.java:116) ~[MessageToMessageCodec.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeWrite(DefaultChannelHandlerContext.java:644) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.write(DefaultChannelHandlerContext.java:698) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.writeAndFlush(DefaultChannelHandlerContext.java:688) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.writeAndFlush(DefaultChannelHandlerContext.java:717) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:893) ~[DefaultChannelPipeline.class:?]
at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:239) ~[AbstractChannel.class:?]
at cpw.mods.fml.common.network.simpleimpl.SimpleNetworkWrapper.sendToDimension(SimpleNetworkWrapper.java:195) ~[SimpleNetworkWrapper.class:?]
at mekanism.common.PacketHandler.sendToDimension(PacketHandler.java:232) ~[PacketHandler.class:?]
at mekanism.common.tile.TileEntityBasicBlock.setFacing(TileEntityBasicBlock.java:187) ~[TileEntityBasicBlock.class:?]
at mekanism.common.block.BlockMachine.func_149689_a(BlockMachine.java:249) ~[BlockMachine.class:?]
at net.minecraft.item.ItemBlock.placeBlockAt(ItemBlock.java:213) ~[abh.class:?]
at mekanism.common.item.ItemBlockMachine.placeBlockAt(ItemBlockMachine.java:244) ~[ItemBlockMachine.class:?]
at net.minecraft.item.ItemBlock.func_77648_a(ItemBlock.java:103) ~[abh.class:?]
at mekanism.common.item.ItemBlockMachine.func_77648_a(ItemBlockMachine.java:210) ~[ItemBlockMachine.class:?]
at net.minecraft.item.ItemStack.func_77943_a(ItemStack.java:127) ~[add.class:?]
at net.minecraft.client.multiplayer.PlayerControllerMP.func_78760_a(PlayerControllerMP.java:360) ~[bje.class:?]
at net.minecraft.client.Minecraft.func_147121_ag(Minecraft.java:1435) ~[bao.class:?]
at net.minecraft.client.Minecraft.func_71407_l(Minecraft.java:1941) ~[bao.class:?]
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:961) ~[bao.class:?]
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:887) ~[bao.class:?]
at net.minecraft.client.main.Main.main(SourceFile:148) ~[1.7.10.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_60]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_60]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_60]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_60]
at net.minecraft.launchwrapper.Launch.launch(Launch.java:134) ~[launchwrapper-1.9.jar:?]
at net.minecraft.launchwrapper.Launch.main(Launch.java:28) ~[launchwrapper-1.9.jar:?]

Let me know if this is a bug or if I have something improperly installed.

-MastaC

That crash was a bug I fixed a while ago but forgot to cherry-pick onto the master branch, thanks for letting us know, I've now fixed it. The Infuser leaking power isn't something I can replicate, does it happen without other mods installed? Which other power mods (BuildCraft, IC2) do you have installed? Does it happen with other Mekanism machines? If you leave it disconnected from power, does it drain its internal buffer or is it just draining from connected cables for no apparent reason?

We also have Thermal Expansion, BuildCraft, IC2, and ExtraUtils in terms of other mods that use power, but I am assuming that Thermal Expansion is the culprit due to its recent release.

It does happen with other Mekanism machines, and when disconnected from power the machines properly use their internal buffer. However, when a cable is reconnected to the energy cube, the cube will drain its power into the machine even if the machine's internal buffer is full and it's not processing items.

Hope this helps.

I believe it is just with Mekanism cables I just tried EnderIO cables "Energy Conduit" and had no isssue.
It is all machines, if its just the Mekanism cable on the energy cube it will not drain.

OK, I think this looks awfully like a BuildCraft power API issue I solved a few days back. I'll see if I also forgot to merge that into the master branch

Should be fixed in the latest build

Works in .84, thank you.
Now when you have EnderIO cables attached to universal cables it will drain the cube

Hmm, yeah. Thought that would probably be the case... Solving that will require a bit more of an in-depth change. I've done some work in it already in a development branch but I'm not confident enough yet that it doesn't break other things to merge into master. I'll try and get it sorted as quickly as possible

Yep, it's working for me; thanks for pushing out a fix so fast.