Interfaces can only accept items from the top, and be extracted from the bottom. This is really weird behaviour, and makes automation a pain.

In addition, I was able to pump items into the bottom of an interface and the items ended up in the "exported items" slots of the interface.

Also, connecting an interface to a system by connecting a cable along the line from an external storage can cause the interface to not connect at all. EDIT - Chunk unloading also causes it to disconnect.

@gr4y You have to push / pull the items to the interface with a pipe... (it doesn't auto eject or auto pull)

And Mekanism pipes do not work on RS blocks because Mekanism does not support Forge's item handler system yet.

@msrEagle

Interfaces can only accept items from the top, and be extracted from the bottom. This is really weird behaviour, and makes automation a pain.

What do you propose instead? Interfaces can take from any side items besides the bottom side. The bottom side is meant for output.

What do you propose instead? Interfaces can take from any side items besides the bottom side. The bottom side is meant for output.

Being able to insert/extract from any side, just like AE interfaces.

I tried to use the interface myself to automate Mekanism Metallurgic Infuser and it didn't work at all, because Mekanisms Pipes won't connect to the interface, nor the ex- and/or importer. I just placed a chest on top of an Interface and dropped Dirt into it and it wasn't imported.

Then I configured the Exporter of the Interface to give me 5 Dirt, but the Chest on the top of the interface just stayed empty. So I put the Chest to the right, the left, the right and in the front of the interface, but it stayed empty.

I have to revert this, the current way I'm doing it is broken and there is no way for me to know from the getCapability call if an insert or extract is requested