Tekkit Crash on Startup

[Unh0ly_Tigg]

Title: Tekkit Crash on Startup

Version: 3.1.2

OS: Windows 7 Home Premium 64 bit

Java Version: Java 7 update 5

Description of Problem:

For some reason, in the Nuclear Control Mod, then adding the blocks to the game, it instiated the nuclearcontrol.BlockNuclearControlMain block class twice causing it to try and load that block into the id (Slot 192) multiple times, causing this error before it even got to the main menu.

Error Messages:

java.lang.IllegalArgumentException: Slot 192 is already occupied by nuclearcontrol.BlockNuclearControlMain@5901fffa when adding nuclearcontrol.BlockNuclearControlMain@124ca3bd

Error Log:

--- BEGIN ERROR REPORT 635eb6f2 --------

Generated 8/17/12 2:13 AM

 

Minecraft: Minecraft 1.2.5

OS: Windows 7 (amd64) version 6.1

Java: 1.7.0_05, Oracle Corporation

VM: Java HotSpot 64-Bit Server VM (mixed mode), Oracle Corporation

LWJGL: 2.4.2

OpenGL: Mobile Intel® 4 Series Express Chipset Family version 2.1.0 - Build 8.15.10.2302, Intel

 

java.lang.IllegalArgumentException: Slot 192 is already occupied by nuclearcontrol.BlockNuclearControlMain@5901fffa when adding nuclearcontrol.BlockNuclearControlMain@124ca3bd

at pb.<init>(Block.java:251)

at pb.<init>(Block.java:284)

at agy.<init>(BlockContainer.java:13)

at nuclearcontrol.BlockNuclearControlMain.<init>(BlockNuclearControlMain.java:99)

at nuclearcontrol.IC2NuclearControl.initBlocks(IC2NuclearControl.java:193)

at mod_IC2NuclearControl.load(mod_IC2NuclearControl.java:99)

at cpw.mods.fml.common.modloader.ModLoaderModContainer.init(ModLoaderModContainer.java:356)

at cpw.mods.fml.common.Loader.modInit(Loader.java:273)

at cpw.mods.fml.common.Loader.initializeMods(Loader.java:628)

at cpw.mods.fml.client.FMLClientHandler.onLoadComplete(FMLClientHandler.java:223)

at net.minecraft.client.Minecraft.a(Minecraft.java:429)

at net.minecraft.client.Minecraft.run(Minecraft.java:738)

at java.lang.Thread.run(Unknown Source)

--- END ERROR REPORT 166d905c ----------

I just tried clearing my tekkit folder and redownloading the pack 3-4 times and the same issue just keeps popping up. I did set the option to "Always use recommended builds"