Windows .exe Direwolf 20 1.6.4 v1.0.11 logistics pipes crash

  • 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
Status
Not open for further replies.

lavarthan

New Member
Jul 29, 2019
2,437
0
0
I believe this is the known error with LP and was fixed in the next version. You need to either backup and remove the pipe at 'Block location: World: (2,63,159)' with MCEdit or update the version of LP. If you choose to remove the pipe and not update you can use a chest as an go between so there is no error.
 

JamiePhonic

New Member
Jul 29, 2019
404
0
0
and one more time....

FOR ANYONE WHO'S GAME CRASHES WHEN USING LOGISTICS PIPES WITH THERMAL EXPANSION MACNINES:
the crash that occurs when connecting almost any logistics pipe DIRECTLY to the OUTPUT of a thermal expansion machine is a know bug.
2 solutions can be found below.


the easiest way to fix this problem put a chest between the output of the furnace and the logistics pipe. this is usually good practice anyway as it will give you TE machines a sort of buffer. In the mean time, you will need to use MCEdit to remove the offending pipe(s) to recover your world
you can also update the mod to build #89, where this problem has been fixed. its not recommended and you will still need to use MCEdit to remove the offending pipe(s) to recover your world, but if you still want to update the mod, download it from Here, then open the launcher, select your modpack then hit "edit modpack" at the top and select "add mod" and point it at the new file. make sure you disable the older version or your game WILL crash.
if you do this, you WILL NOT be able to connect to any multiplayer servers, unless they have updated it too.
if your interested, here's the reason i think the crash happens:
from what i remember, thermal expansion machines will try to output anything they create to an adjacent inventory, but since logistics pipes is technically an add-on to buildcraft, it follows that it may share some code with buildcraft.
i know from testing that thermal expansion machines can output directly into a buildcraft pipe and a basic logistics pipe, so it follows that the furnace will try to output into the supplier logistics pipe too.
i suppose the crash happens because the code says the supplier pipe is supposed to make the request for items to enter the network, not to have them inserted into it, and because no one requested a gold bar or whatever, it doesn't know why its there and just crashes

Note: all that could be completely and utterly wrong, its just my guess
 

Joe Nemeth

New Member
Jul 29, 2019
2
0
0
JamiePhonic,

You ROCK!! I had no idea what the heck I was doing on the MCedit program, but I wandered through my crashed world and deleted blocks that I thought were the culprits and I still couldn't load the world. So, I resolved myself to starting over and this time, I would update the logistics mod first. At launch, my old crashing world came up and because I liked the name and would use it again, I renamed it, "crashed world". Just for S&G's, I decided to try loading the now renamed world with the new mod enabled update and BAM!! I was back in business and back in my old world.

Thank you (from a frustrated 40 something playing FTB) and thank you for my 9 year old who now thinks I am a hero for saving our world! I appreciate the help.

Sincerely,

Joe
 

DeadEyeSavage

New Member
Jul 29, 2019
8
0
0
how to open a ftb modpack in mc edit? when I navigate to the folder where my map is in idk which 1 will I need to open I tried a few and so far nothing opens.
 

JamiePhonic

New Member
Jul 29, 2019
404
0
0
choose "open" in MCEdit, the go to the folder your save is in, the open the file called "level.dat"
 

DeadEyeSavage

New Member
Jul 29, 2019
8
0
0
choose "open" in MCEdit, the go to the folder your save is in, the open the file called "level.dat"

that's the problem I saw no level.dat until I notice there was one called level.dat_old I removed the _old saved it, then open in mcedit then fixed it then change it back to level.dat_old. Its all working now thank you for the help!
 
Status
Not open for further replies.