[6.2.4] Redstone engines won't connect to extraction pipes. [Remote IO]
shadowsyllvet opened this issue · 22 comments
This is a major issue for me as I don't have the patience to make multiple autartic pulsars for all of my pipes
I have no idea whats going on in this image.
My mod list server side
Welp.. This is awkward.. the engine that is supposed to be powering the pipe is powering everything but the pipe. I assume this isn't intentional?
Uhh. Outdated BC API in RemoteIO, i think.
2014-12-13 13:54 GMT+06:00 Adrian Siekierka [email protected]:
By RemoteIO!? What!?
—
Reply to this email directly or view it on GitHub
#2301 (comment)
.
using the latest build of remote IO, I just updated from build b26 to b84... since railcraft, buildcraft, and logistics pipes no longer support MJ. Dmillerw also removed MJ related items in the latest builds so I figured they'd mesh well.. they do not.
Seems that way I have no idea why but the engine orientation is of and the redstone is acting weird
I can't think of what I could've done that'd break it, since I don't do anything strange, but I'll investigate.
It look like the redstone block is treating the first engine as a solid block and that engine is providing a redstone signal to all surrounding blocks
That's really weird... this is all I do, and it's supposed to replicate vanilla behavior
Going to test a theory. Put redstone lamps in place of the engines with and without RIO installed
@dmillerw - Can you reproduce this?
This happens on SMP with RC, Logistics Pipes, BC, and RemoteIO as the only installed mods. Going to try to reproduce with only RIO and BC installed(might be a weird triangle issue)
Ohh, you know what it might be, update RemoteIO. I, er, broke Redstone but it was fixed in 1.8.1.
@dmillerw - When I spent 8 hours making the pipe handling of redstone vanilla-exact, I learned one thing.
NEVER MESS WITH REDSTONE.