BuildCraft|Core

BuildCraft|Core

7M Downloads

buildcraft.factory.BlockPump

Syer10 opened this issue ยท 18 comments

commented

Something about Fluid Registrey. I have allot of mods installed so idk in the past it worked bud i updated to latest version then i dident
crash: http://pastebin.com/FJaRaBby

commented

This is highly unlikely to be a BuildCraft issue.

Your crashlog is odd. From the log it appears that the LAVA Fluid in the FluidRegistry is not being registered in your setup. That is something that shouldn't happen.

I'd try the standard mod debug routine: remove mods one at a time to see if the issue becomes resolved. Failing that, you may want to try downgrading your forge version; forge 964 doesn't have an installer for a reason, 953 is I believe the latest version built for general use.

commented

Yeah...I don't know why you'd be using .964, as .953+ are really just Gradle-debug builds.
Try re-installing Forge 9.11.1.953 and see if the problem persists (and nice catch taelnia).

commented

It had a installer and it works with everything i don't think that's my problem.

commented

I'm curious where that installer for 964 is from, as there is no official Forge installer above 953: http://files.minecraftforge.net/

If someone custom built Forge, there is a chance that they changed other code. You still may wish to try downgrading to the last official installer version (953)

commented

Nome, came from that site. I saw they took it down. Same with the universal version.
PS: I still have it

commented

My original suggestion still stands. Try removing other mods. One of them may be messing with the FluidRegistry.

I tested a fresh 953 forge install with only BuildCraft. I created a new world in creative, went to the nether, setup a pump over lava that output into a void pipe, watched lava disappear, saved and exit the world, and rejoined into it. At no point did I receive an error like the one you had in your log.

That NPE should not be happening unless either the FluidRegistry code was changed, or a mod is messing with the FluidRegistry maps

commented

How about you try my test world cause that is where the crash is coming from. I made this so people don't have my problem.

commented

thx

commented

I would test your setup, but I don't see a link to download configs and a world save.

I'm not trying to be mean or imply that you're wrong. I'm just stating what your log says. Specifically your log is showing a NullPointerException crash because the fluidIDs Map in the FluidRegistry does not contain an entry for "lava"; something that should not happen as the LAVA fluid is registered a few lines below where it is defined. This is what is leading me to believe that another mod is messing with the FluidRegistry.

commented

Want to try it? I have a mod-pack set up for my testing on my Technic launcher. Just start a world and place a pump in the nether and power it. Then use the latest version of build-craft and deleat the old one.
Oh and don't forget the chunkloader.

commented

I was unable to reproduce.

I Googled your name and technic, found your pack installed it. I created a new creative world, went to the nether, setup a pump powered by a TE3 creative energy cell, had the pump output into golden fluid pipes that went into void fluid pipes. setup a chunkloader, saved and exited. replaced the BC mod with the latest. I started the client back up and logged back in without a problem, note I tested logging back into the world in both the Nether and the Overworld.

Either your pack that is on technic doesn't have your exact mod/config setup, or there may be an issue with the particular test world that you have.

commented

Weird. That's all I have to say.

commented

I concur, Weird fits the bill. As I stated earlier. the NPE you received should never happen.

commented

Does keeping it in an endertank do anything?

commented

No change. I set up an endertank in the nether next to the pump, and one in the overworld that is being pumped into a void pipe. Logged out and back in with no issue.

commented

Weird you have my exact setup now and nothing is happening?

commented

You might try increasing your PermGen space: -XX:MaxPermSize=128M