Multiplayer Config not Working

Issue #37 resolved
Former user created an issue

In singleplayer, version 1.4.1.5 (for MC 1.4.2) works like a charm. But when I create a server, there's an error involving slot 4000 being already used by Xie's Mod. In singleplayer, I simply changed the ID with ID Resolver. But in multiplayer I CAN'T FIND WHERE TO CHANGE THE ID! >:C

Here's the error:

---- Minecraft Crash Report ---- // Hi. I'm Minecraft, and I'm a crashaholic.

Time: 02/11/12 15:36 Description: Exception in server tick loop

java.lang.IllegalArgumentException: Slot 4000 is already occupied by xie.mods.xm.blocks.XieBlockLeaves@37f7466f when adding binnie.extrabees.gen.BlockExtraBeeHive@4b313e1d at alf.<init>(Block.java:292) at alf.<init>(Block.java:325) at binnie.extrabees.gen.BlockExtraBeeHive.<init>(BlockExtraBeeHive.java:21) at binnie.extrabees.core.ExtraBeeCore.setupBlocks(ExtraBeeCore.java:164) at binnie.extrabees.core.ExtraBeePlugin.doInit(ExtraBeePlugin.java:51) at forestry.core.ForestryCore.postInit(ForestryCore.java:160) at forestry.Forestry.postInit(Forestry.java:41) 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:440) at sun.reflect.GeneratedMethodAccessor2.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:69) at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45) at com.google.common.eventbus.EventBus.dispatch(EventBus.java:317) at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:300) at com.google.common.eventbus.EventBus.post(EventBus.java:268) at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:140) 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:69) at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45) at com.google.common.eventbus.EventBus.dispatch(EventBus.java:317) at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:300) at com.google.common.eventbus.EventBus.post(EventBus.java:268) at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:83) at cpw.mods.fml.common.Loader.initializeMods(Loader.java:654) at cpw.mods.fml.server.FMLServerHandler.finishServerLoading(FMLServerHandler.java:88) at cpw.mods.fml.common.FMLCommonHandler.onServerStarted(FMLCommonHandler.java:344) at hg.c(DedicatedServer.java:110) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:454) at fp.run(SourceFile:818)

Relevant Details: - Minecraft Version: 1.4.2 - Operating System: Windows 7 (amd64) version 6.1 - Java Version: 1.7.0, Oracle Corporation - Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation - Memory: 1262209728 bytes (1203 MB) / 1572339712 bytes (1499 MB) up to 1572339712 bytes (1499 MB) - JVM Flags: 2 total; -Xmx1536M -Xms1536M - AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used - FML: ~ERROR~ NullPointerException: null - Is Modded: Definitely; 'forge,fml' - Profiler Position: N/A (disabled) - Type: Dedicated Server

Comments (3)

  1. AstockyTeam

    That's a very simple problem.. java.lang.IllegalArgumentException: Slot 4000 is already occupied by xie.mods.xm.blocks.XieBlockLeaves@37f7466f when adding binnie.extrabees.gen.BlockExtraBeeHive@4b313e1d at alf.<init>(Block.java:292) If you go into the configs and change the block ID's for either Xie's mod or Extra bees this will be fixed. It's not a bug

  2. Log in to comment