Minecraft Forums

I'm having some issues: Two mods seem to be having issues with each other. The two mods in question are the Bioshock Mod and the Artifacts Mod. Here's the crash report. Please help!!!

---- Minecraft Crash Report ----
// I let you down. Sorry

Time: 7/7/14 11:53 PM
Description: Initializing game

java.lang.IllegalArgumentException: ID is already registered: 3
at net.minecraft.entity.EntityList.func_75618_a(EntityList.java:93)
at cpw.mods.fml.common.registry.EntityRegistry.registerGlobalEntityID(EntityRegistry.java:199)
at com.sigurd4.Bioshock.BioshockMod.registerEntity(BioshockMod.java:54)
at com.sigurd4.Bioshock.BioshockMod.preInit(BioshockMod.java:502)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:513)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:208)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:118)
at cpw.mods.fml.common.Loader.initializeMods(Loader.java:690)
at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:288)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:527)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:815)
at net.minecraft.client.main.Main.main(SourceFile:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

Change the ID in the config. If there is no possible option, harrass the mod developer to finish their mod properly.

FYI, 1.7.x doesn't have ID conflicts anymore - so maybe they won't care.

Ah you're right, GameRegistry just has registerItem and registerBlock - nothing about Biomes and etc. But hey Block/Item ID's were always the most painful though so it's still amazeballs

I think you're right, I find it hard to believe though that they're using static entity ID's instead of using EntityRegistry.findGlobalUniqueEntityId().... they are seriously dodgy mod coders if so, even ModLoader had this functionality.

It's okay! I managed to fix it through the Artifact's Config file. Turns out it was the Golem from Artifacts was conflicting with some other entity with the Bioshock mod. Changed the Golem ID to a number that wasn't in use! Easy!

Thanks for the help guys!!!

There you go

Whenever you see something about "ID is already registered" or something similar, check your configs.

You should also search your FML log files for the text "conflict" - because it happens very often that there can be a block or item conflict but the game won't crash, you will just find later on that when you craft something the result becomes completely different to what it should be.

Here I am coming along behind the curve in 2015 having just tried to install Animal Bikes with Artifacts in 1.7.10. Turns out right at the beginning of Artifacts there was a Golem set to ID 4 that conflicted. At least I was able to change that number manually. The Animal Bikes mod doesn't even offer users the option of changing any ID's in their config file. It's touch and go right now because I have absolutely no information about Animal Bikes in terms of used ID's. The game is working, but I'm hoping I won't have an issue further along as a result of the new value I've assigned.