Jump to content
  • 0

Crashing after logo


Lazyhoneybadger

Question

Launcher Version: 1.0.1.3

Operating System: W7

Java Version: 64

Antivirus Program:

Description of Problem:

Crashing after logo. New to tekkit very curious to problem

Error Messages:

--- BEGIN ERROR REPORT 93b6e61a --------

Generated 9/21/12 3:14 PM

Minecraft: Minecraft 1.2.5

OS: Windows 7 (amd64) version 6.1

Java: 1.7.0_04, Oracle Corporation

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

LWJGL: 2.4.2

OpenGL: ATI Radeon HD 5900 Series version 4.2.11762 Compatibility Profile Context, ATI Technologies Inc.

java.lang.IllegalArgumentException: Slot 188 is already occupied by ic2.advancedmachines.BlockAdvancedMachines@465db614 when adding ic2.advancedmachines.BlockAdvancedMachines@325cff23

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

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

at ic2.advancedmachines.BlockAdvancedMachines.<init>(BlockAdvancedMachines.java:16)

at mod_IC2AdvancedMachines.load(mod_IC2AdvancedMachines.java:190)

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 19cd663a ----------

Error Log:




Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

One of your ic2 config files is malformed. The easiest way to solve this is to delete your %AppData%\.techniclauncher folder and make it redownload with the launcher. This will delete your saved worlds as well, so back them up if you have any you care about.

Shouldn't ID resolver fix the issue if it was working as intended?

Link to comment
Share on other sites

  • 0

Yes, but I haven't the foggiest idea how to properly debug that. As far as I'm aware it's enabled by default, at least on my most recent tekkit reinstall the logs were full of messages from it.

That is what I meant. It might be an issue with ID resolver not correctly identifying open ID's or something like that. The reason I asked is because if that is the case, there could be a slew of other errors due to the fact that the devs expected ID resolver to fix the ID's for them and thus there are some more conflicts.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...