Buildcraft pumps don't work...

[joeSHMO8347]

Title: Buildcraft pumps don't work...

Version: 3.1.2

OS: MS wWndows Vista 32 bit

Java Version: Java 7 32 bit

Description of Problem:

One of my players noticed that his Buildcraft pumps was not working. Then we all noticed none of the pumps on the entire server were working. They were fine this afternoon, but now no longer work. there no warning or error event i could find that said this happened. we all tried different engines to make sure it wasn't just on type, but to no avail... i went and downloaded a new tekkit sever and started it and pulled the buildcraft mod files and droppped them in my server files and that did not solve it either. Any help is appreciated!

Error Messages:

none...

Error Log:

17.08 20:45:09 [server] SEVERE [buildCraft] Pipe failed to load from NBT at 205,63,21

17.08 20:45:09 [server] INFO [buildCraft] Error creating pipe type 0 (class=null)

17.08 20:45:06 [server] SEVERE [buildCraft] Pipe failed to load from NBT at 384,67,353

17.08 20:45:06 [server] INFO [buildCraft] Error creating pipe type 0 (class=null)

I keep getting these here and there and fix them, but i'm not quite sure if they have anything to do with our pump no working

[KJSniper]

You wouldn't happen to have CoreProtect, would you?

[joeSHMO8347]

i HAD it now i took it out and the pumps still don't work. A fellow admin recommended CoreProtect and i dropped it in thinking nothing of compatability. now what? put in fresh bc serverside mod file?

[KJSniper]

The reason I ask is because whenever you rollback pipes with CoreProtect, the pipes glitch and have the pipe's outline but are invisible. I got the same errors you are getting when I rolled back pipes for the first time.

I would try opping [buildCraft], if you haven't already, and see if that works.

[joeSHMO8347]

Yeah I opped [buildcraft] a long time ago...I only had CoreProtect for like 4 days and someone must've rolled someting back, but all of the bc pumps in the world will not work at all even after taking out C/P and putting new buildcraft zip in the server mods folder. So...

[KJSniper]

Hmm, and you're positive it's setup right?

[profjb]

ok ile explain the problem as i have fixed it and i had the same problem

17.08 20:45:09 [server] SEVERE [buildCraft] Pipe failed to load from NBT at 205,63,21 <--- LOOk at these coords! X Y Z

GO To these coords via tp or using the map. If you cannot get on the server then use

mcedit to remove these pipes. It is literaly the ONLY way to remove them without removing ALL the buildcraft pipes.

[joeSHMO8347]

All of my people know how to set up a pump and the error code was only thee for reference to help in figuring out my problem. I'll gibe you all my plugins list:

autosaveworld

BKCommonLib v1.18

ChatManager

CityWorld

Essentials

EssentialsChat

EssentialsGeoIP

EssentialsProtect

EssentialsSpawn

LogBlock

LWC

Modifyworld

MyWorlds

NoLagg

NoLaggChunks

NoLaggExamine

NoLaggItemBuffer

NoLaggItemStacker

NoLaggMonitor

NoLaggTNT

PermissionsEx

Residence

Safe Creeper

VanishNoPacket

WorldEdit

ZavAutoMessager

[joeSHMO8347]

Bump! the logged stuff is only there for reference. the pumps themselves are not working. the suction pipes coming from the bottom of the pump are NOT extending and the engines just run til they blow up

[joeSHMO8347]

I'm wondering if this is a tick rate issue. I'm using a hosting company that specializes in hosting tekkit servers and it may be a tick rate problem on their end. but could there be a rate problem due to one of my plugins I've listed above?

[dataspiller]

I was having this same issue - then your reference to "tick rate" gave me a clue... I had frozen time using commandbook's "/time -l 12pm" command.

As soon as I set the normal time cycle in motion (/time 8am) the pumps started working normally.

Since I like the time to be frozen, I have tried setting the time-lock-delay setting in plugins/CommandBook/config.yml to 200 (default is 20), froze time again, restarted the server and tried it again.

After several hours, the pumps are continuing to work fine.