BuildCraft pipe errors potential fix

[kysoto]

I discovered a potential fix for the buildcraft pipe errors. IF you have FTP access to your server, you can download your world to your computer and put the world into your .minecraft/saves folder. when you do that you can start your world up in single player and go find the pipes that have stuff going through them and turn them off. my friends server has had this error happen like 3 times the first time i have no idea what caused it but it caused a world wipe, the second time i created an infinate loop using dia pipes n such, the 3rd time our quarry overloaded our sorting system.

[KakerMix]

Or you can do what all the 'cool' and 'in the know' and 'I read well' people do and simply read the current bug list and see that a solution to this issue

[kysoto]

i did read the current bug list and tried that solution. it didnt work. i spent 12 hours beating my face into the proverbial wall on that till i found out the worlds worked in single player.

[KakerMix]

Shame it doesn't work for you because up until now its worked for everyone else.

[thebird]

I also had a problem with the fix for buildcraft listed in the buglist. When I tried using the fix I got this error:

[buildCraft] EntityItem.toEntityItem: World was null! Using default world.

I was able to fix this by renaming the new buildcraft zip. I added [1] to the front of the filename and now the errors I was encountering are gone.

Just to make it clear, I had to change the original filename, buildcraft-2.2.11-b1.0.1R1-r3.zip to the following:

[1]buildcraft-2.2.11-b1.0.1R1-r3.zip

EDIT: Forgot a word.