looks like mod is not properly installed
Should i reinstall the mod?
looks like mod is not properly installed
Should i reinstall the mod?
Should i reinstall the mod?
Probably the best soloution
I have a block ID conflict between nuclear control and imbibes red logic mod. Tried simply changing the block ID in the nuclear control config into 4096, which is not working? Any other "easy" solution for my problem?!
thanks a lot!
Matthias
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at mods.immibis.cobaltite.ModBase$1.register(ModBase.java:143)
at mods.immibis.core.impl.IDAllocator.allocate(IDAllocator.java:129)
at mods.immibis.core.ImmibisCore.init(ImmibisCore.java:103)
at mods.immibis.core.ICNonCoreMod.init(ICNonCoreMod.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:545)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
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:194)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
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:105)
at cpw.mods.fml.common.Loader.initializeMods(Loader.java:696)
at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:249)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:508)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:807)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at mods.immibis.cobaltite.ModBase$1.register(ModBase.java:139)
... 39 more
Caused by: java.lang.IllegalArgumentException: Slot 4095 is already occupied by shedar.mods.ic2.nuclearcontrol.BlockNuclearControlMain@4168c350 when adding mods.immibis.redlogic.lamps.BlockLampCube$On@44eedabc
at net.minecraft.block.Block.<init>(Block.java:349)
at mods.immibis.redlogic.lamps.BlockLampCube.<init>(BlockLampCube.java:56)
at mods.immibis.redlogic.lamps.BlockLampCube$On.<init>(BlockLampCube.java:187)
... 44 more
Change ID to 4094.
If that doesn't work, to 4093, then to 4092 and so on.
1.6.4 spam console
15:03:19 [WARNING] EnergyNet.addTileEntity: shedar.mods.ic2.nuclearcontrol.tilee
ntities.TileEntityRemoteThermo@2eece5d0 (shedar.mods.ic2.nuclearcontrol.tileenti
ties.TileEntityRemoteThermo@2eece5d0) is conflicting with shedar.mods.ic2.nuclea
rcontrol.tileentities.TileEntityRemoteThermo@36c01888 using the same position (a
lready added, prev. te not removed, overlapping), aborting
1.6.4 spam console
15:03:19 [WARNING] EnergyNet.addTileEntity: shedar.mods.ic2.nuclearcontrol.tilee
ntities.TileEntityRemoteThermo@2eece5d0 (shedar.mods.ic2.nuclearcontrol.tileenti
ties.TileEntityRemoteThermo@2eece5d0) is conflicting with shedar.mods.ic2.nuclea
rcontrol.tileentities.TileEntityRemoteThermo@36c01888 using the same position (a
lready added, prev. te not removed, overlapping), aborting
Please specify version of Nuclear Control and ic2 build number.
Is this for 1.6.4?
If so you need to update the page because it is confusing.
Thanks.
Is this for 1.6.4?
If so you need to update the page because it is confusing.
Thanks.
Almost all 1.6.2 mods are available for 1.6.4, the only ones that have problems are those with special worldgen structures.
The title shows the version of the mod, and not the version of Minecraft it is built for.
Shedar, do the latest Reactor API changes in IC2 experimental (build 288 and 295) affect Nuclear Control in any way?
I expect so, since it calls the reactor API to look at the insides I think. Probably will break
Well, it didn't crash when I started them together just now as a quick test.
Shedar, do the latest Reactor API changes in IC2 experimental (build 288 and 295) affect Nuclear Control in any way?
I don't know, haven't seen changes yet. Let me know if reactor sensors broken.
I moved up to build 295, and the reactors are whacky. There has been an update to the reactor UI, which I guess is working.
Nuclear Control is now reporting strange and different data on the advanced information panels. I think some of the components are bugged, so maybe that is part of the problem. My reactor is using a quad uranium fuel rod and thick neutron reflectors, and I don't believe either component is showing the proper wear.
Either way, I don't think nuclear control is working as intended with this new build of IC2 experimental. The reported temperature, and output seems incorrect.
My other panels are working correctly, that are linked to an MFE and an MFSU.
Please note that as part of the changes, lifetime of both uranium and MOX fuel was doubled - from 10k and 5k seconds respectively to 20k/10k. That may be the reason you're not seeing the wear levels you expect.
@ Shedar: https://dl.dropboxusercontent.…0/2013-11-05_21.18.54.png (Build #296)
- Sensor kit works properly
- Heat display is correct
- Info panel reports mB/t instead of EU/t
There is no more Railcraft steam mode option in the IC2 config
The reactor will gain coolant input/output capabilities/needs at a later point in time
- Info panel reports 0:00:00 for MOX fuel time remaining
This was already present in older builds of IC2 experimental
Runtime for MOX fuel is equal to the old runtime of uranium (10k seconds)
- Uranium reports its usual 2 hours 46 minutes for time remaining, but only ticks down once per 2 seconds
This is because uranium lifetime was doubled to 20k seconds
v.1.6.2d
- MOX fuel support
- better detection of fuel duration
- support of steam output reactors disabled
Should work with ic2 experimental build #295+ as well as with earlier experimental builds (if you want MOX time tracking)
Please let me know if this build works properly. If all okay then I'll add it to the first post.
Looking good. Launched into my test world without a hitch, info panel shows exactly what it needs to, all runtimes are correct. Many thanks!
v.1.6.2d
- MOX fuel support
- better detection of fuel duration
- support of steam output reactors disabled
Should work with ic2 experimental build #295+ as well as with earlier experimental builds (if you want MOX time tracking)
Please let me know if this build works properly. If all okay then I'll add it to the first post.
Thank you sir.
Can anyone explain how the range trigger should work? Just wanted to switch a reactor on/off on distance with it...