Closed 1.0.2: Ender IO Conduits don't like being placed on other conduits (ME ones)

  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

xBlizzDevious

New Member
Jul 29, 2019
110
0
0
Version:
1.0.2

What is the bug:
Subject kinda says it all. When I place down an ME conduit (from Ender IO) on top of an Ender IO energy conduit (basic one), my client crashes. Server and other clients all continue to work fine.

Code:

Mod & Version:
Infinity 1.7.10 (1.0.2)

Paste.feed-the-beast.com log:
http://paste.feed-the-beast.com/view/ccdfe719

Can it be repeated:
Yes - Every time I try. I have three of basically the same log.

Known Fix:
Not known
 

b0bst3r

New Member
Jul 29, 2019
2,195
0
1
You are using an old EnderIO version - all known ME conduit issues have been fixed in EnderIO 2.2.8 build 349

Infinity uses build 345
 

xBlizzDevious

New Member
Jul 29, 2019
110
0
0
You are using an old EnderIO version - all known ME conduit issues have been fixed in EnderIO 2.2.8 build 349

Infinity uses build 345

I was using the version that comes with 1.0.2. I don't think users should be expected to update FTB modpacks manually because of a known issue that's been fixed. But it's updated and fixed, so whatever.

Fixed in 1.0.3

Interesting. There's no 1.0.3 as far as I can tell. There's an update to 1.1.0 that I've just switched to and can confirm that it's definitely fixed on that version.
 

tfox83

New Member
Jul 29, 2019
1,588
0
0
I was using the version that comes with 1.0.2. I don't think users should be expected to update FTB modpacks manually because of a known issue that's been fixed. But it's updated and fixed, so whatever.



Interesting. There's no 1.0.3 as far as I can tell. There's an update to 1.1.0 that I've just switched to and can confirm that it's definitely fixed on that version.
1.0.3 never went public but 1.1.0 is newer and it is fixed in that version as well :)