Error creating pipe type 0 (class=null) , Havent rolled back blocks

[johnlukey]

Launcher/pack Version:Tekkit 2.1.0 (Recommended)

Operating System: Debian

Version of Java: 1.7u3

Description of Problem:

From my understanding of the problem, if pipes are deleted and then attempted to be reloaded (by hawkeye or something) they spawn back with 'type 0' which is null, and then spits out TONS of errors as it attmpts to find the class.

I created my server with this bug in mind, not allowing any kind of creeper regeneration, and never once used world edit on tekkit blocks, or rolled back anything with hawkeye. I thought i had prevented all means of Pipe type 0 of occuring, but even my new users are managing to create the pipes. The problem seems to be exponential, users log in and the CMD is spammed with a bunch of

2012-04-27 14:03:17 [iNFO] [buildCraft] Error creating pipe type 0 (class=null)

2012-04-27 14:03:17 [iNFO] [buildCraft] Error creating pipe type 0 (class=null)

2012-04-27 14:03:17 [iNFO] [buildCraft] Error creating pipe type 0 (class=null)

2012-04-27 14:03:17 [iNFO] [buildCraft] Error creating pipe type 0 (class=null)

As time goes on, more of these messages when the users log in. I doubt that the pipes are actually replicating, but since i have almost positively prevented any kind of reload of deleted pipes, i come to the conclusion that the problem is internal, or relying on another factor.

Here is my log of server startup, Buildcraft loads up error free so im not sure if the problem is mod related.

I end the pastie at the first time the pipe type 0 is spawned, every time the same error messages are created. But this is a slightly dated log, today users are logging into " [iNFO] [buildCraft] Error creating pipe type 0 (class=null)" being spammed on the CMD 20+ times

Pastie: http://pastebin.com/negv46d0

I know a fix is to delete the pipes by hand, this was once a reasonable method. But my server now averages 30 players constant, and the problem is too widespread for me to continue solving by hand. There must be a problem higherup that is allowing these pipes to exist

Would it be possible to add a fake class for type 0? so atleast it loads something

Or possibly to add type 0 to the config to be ignored?

On my old server Pipe type 0 would crash clients if you came near, my current dedi is holding up, but the problem just started getting BAD today. Im afraid this will bog down and destroy the entire map :S

Anyone have any suggestions?

It seems to be a fairly common problem

[aldrigviking]

Same problem here. Have a server with 20-30 players at all times. There must be some way of fixing this, and/or prevent it in the future.

Will gladly help out anyone who can fix this.

[j2ther]

If you have world edit you can try fixing it by going to the area that was rollback/edited and do

//removenear 166 radius

Replace radius with however big of an area you want the //removenear to effect.

If your using LogBlock to rollback griefs then you can also prevent this by adding the item id 166 to the "do not rollback" list in your LB Config.

[xpresas]

If you have world edit you can try fixing it by going to the area that was rollback/edited and do

//removenear 166 radius

Replace radius with however big of an area you want the //removenear to effect.

If your using LogBlock to rollback griefs then you can also prevent this by adding the item id 166 to the "do not rollback" list in your LB Config.

Thanks man you really helped me.

[theallboarder]

same problem here