GenDeathrow
commented
5 years ago I'm guess by the way you started the message, a few dev's responses wasn't so nice. I'll just say is I will try and look into this as soon as I can. Right now I have a lot of projects. But this is a pretty in-depth description of whats happening. All I can think is something has changed with the way forge energy and cofh handles the energy between each other. Hatchery actually uses FE, but when I wrote this.. everyone only really knew RF. So I just labeled it that. Cause it was cross compatible anyways. But maybe not so much the case atm.
First I will start off by saying, Yes I did already search for and see that there are bug reports for these listed issues, however said reports are both closed and old. The bugs listed were previously marked as fixed and confirmed as bugs previously and are now back in Hatchery 2.1.4 for Minecraft 1.12.2
The modpack in question is StoneBlock V 1.0.31 Minecraft 1.12.2 Java version 8 Forge 14.23.5.2768
1) Power output only from sides with vents: If you place a block that needs power to run on any side of the engine, that block will receive power. The problem here is that the only 2 sides that will output power beyond 1 block is the sides with the vents. What I means is this: If you connect a leadstone Fluxduct, Ender IO energy conduit, or any other method to the back, front, top, or bottom of the engine and extend that beyond 1 block space before connecting it to a "something" then no power is transmitted along the conduit. If you place ANYTHING (machine, battery, some other energy consuming device) to the conduit at the first connection to the engine, then power is sent down the entire length of the conduit. However, if you connect that same conduit to the sides of the engine where the vents are, it does not matter if you have a "something" on that first block space as power is sent down the entire length of the conduit without issue. Pics below for example:
1) Pic showing Engine on left, Autosieve for testing purpose on right.
2) Pics showing current internal energy storage of both devices.
3) Pis showing Fluxduct, EnderIO Conduit, and XU Energy Transfer Node setups and results when connected to a non-vent side.
4) Pis showing Fluxduct, EnderIO Conduit, and XU Energy Transfer Node setups and results when connected to a vent side.
As you can see, if connected to a non-vent side, none of the conduits transmit power. If connected to a vented side, the only conduit that transmits power is the Leadstone one from Thermal Expansion. Through further testing I have also discovered that even the Leadstone one shows an issue in that if only 1 conduit is placed, and an energy consuming thing is placed at the side of the conduit instead of the end (see pics below) then the device does not receive power. However if the conduit is extended to a length of 2, then the item on the side of the first conduit receives power.
Additionally it would appear that the EnderIO conduits do not transmit power at all beyond 1 block space from the engine unless the first energy consuming device is "inline" with the engine itself:
As for the second issue that has returned, and that is of the engines pulling power into themselves and acting in a way as a type of energy conduit.