Perhaps now you begin to see that any inventory editor will have the risk of allowing you to add debug items that are not meant for gameplay.
That's like complaining that using a debug cheat code crashes your game. Simple answer is: Don't use it, then.
Kinda beyond the point. There's nothing that should be left over that's accessible by any "simple" means that should crash MC, but I shan't argue with you. I was just bringing the crash to Zip's attention really.
Found the problem HanFox. There are three arrays that look the same and one that doesn't.
If you try to place the one that's the silver block, boom.
If you use the three that look the same, works fine.
I think that's just a behind-the-scenes block that we shouldn't be using
I know. The actual arrays are in 189.
I just want to know why that block is there at all. It almost looks like a test to put the new arrays in the same ID as the other advanced machines.
Ultimately, I don't like the ability to crash my Minecraft even if it is by accident, because once a buggy block is placed you need to remove the mod or edit the world offline to fix it.
What's with the 188:3 HV Solar Array?
If you cheat it in and place it it crashes MC (yes, yes, cheating bad, but things need poking...).
Attached is a bukkit port. I think this should work, but I believe muCKk may have tweaked the wrench item in bukkit, so it may disable some of his custom code...
Seems to work, cpw. Cheers. 
Just need to get permission to put it on MC Port Central now 
Quotejava.lang.RuntimeException: IndustrialCraft 2: MinecraftForge Too Old, need at least 1.2.2
You need to update Mineforge.
Are you getting an error? Check the modloader.txt file in your server folder.
The only ModLoaderMP 1.0.1 is for bukkit... so are you using bukkit or the vanilla server?
If you're not using bukkit you need the ModLoaderMP for vanilla from here.
I've been troubleshooting add-on conflicts with this new version since it came out - all day yesterday and this morning. I'm kind of tired of doing it. Is anyone else having the issue, or is it just me?
Crashes for me, too on IC2 1.337b.
Screenshot of cmd prompt. Sorry if people prefer c/p 
