Okay I put forge in and now it gives me a fatal error.
"There was a fatal error starting up minecraft and FML
Minecraft cannot launch in it;s current configuration
Please consult C:\users\***\appdata\roaming\.minecraft\ForgeModLoader-client-0.log for further information"
Fatal sounds like a lovely word to put in front of error, makes it seem a lot less crucial..."-.-
Okay i got it working and everything but what can i exactly do with EE3 because the items are alot more limited then from what i saw in EE2, no weapons or the cool tnt none of these are included in EE3 "yet" which means they are coming soon™?
Okay i got it working and everything but what can i exactly do with EE3 because the items are alot more limited then from what i saw in EE2, no weapons or the cool tnt none of these are included in EE3 "yet" which means they are coming soon™?
Yes coming soon tis a mod in building, lovingly crafted by Pahimar (meh gimmi a break it's NYE here and I started a lil early, happy new year to anyone that cares)
Okay i got it working and everything but what can i exactly do with EE3 because the items are alot more limited then from what i saw in EE2, no weapons or the cool tnt none of these are included in EE3 "yet" which means they are coming soon™?
I doubt they will come soon. Pahimar is rebuilding this mod from scratch and we are all waiting for just the second prerelease. Also everything that EE2 had should eventually back back on 3, minus red matter, since like Pahimar mentioned dark matter will become better than it was and this red matter will not be needed. Also condensers will be removed but since it will be replaced with something else, no harm done. The only things that will be removed without be replaced, will be collectors (seriously just make a quarry or a tree farm) and the destruction catalysts.
Hey Pahimar, i found a bit of a bug for this mod...
java.lang.NullPointerException at com.pahimar.ee3.core.handlers.WorldTransmutationHandler.onWorldTransmutationEvent(WorldTransmutationHandler.java:122) at net.minecraftforge.event.ASMEventHandler_121_WorldTransmutationHandler_onWorldTransmutationEvent_WorldTransmutationEvent.invoke(.dynamic) at net.minecraftforge.event.ASMEventHandler.invoke(ASMEventHandler.java:35) at net.minecraftforge.event.EventBus.post(EventBus.java:103) at com.pahimar.ee3.core.handlers.WorldTransmutationHandler.handleWorldTransmutation(WorldTransmutationHandler.java:92) at com.pahimar.ee3.network.packet.PacketRequestEvent.execute(PacketRequestEvent.java:100) at com.pahimar.ee3.network.PacketHandler.onPacketData(PacketHandler.java:41) at cpw.mods.fml.common.network.NetworkRegistry.handlePacket(NetworkRegistry.java:243) at cpw.mods.fml.common.network.NetworkRegistry.handleCustomPacket(NetworkRegistry.java:233) at cpw.mods.fml.common.network.FMLNetworkHandler.handlePacket250Packet(FMLNetworkHandler.java:71) at iv.a(NetServerHandler.java:1107) at di.a(SourceFile:59) at cf.b(MemoryConnection.java:80) at iv.d(NetServerHandler.java:136) at iw.b(NetworkListenThread.java:57) at bec.b(IntegratedServerListenThread.java:108) at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:702) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:598) at bdz.q(IntegratedServer.java:159) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497) at fy.run(SourceFile:849) --- END ERROR REPORT dcc9ea82 ----------
Im using all the mods from Direwolf20 pack, Latest version. wandering if this is helpful? or other people have same issue. This crashes my game every time a LAN player uses the Minum stone. *the weaker transmution Stone thing*
Hey Pahimar, i found a bit of a bug for this mod...
java.lang.NullPointerException at com.pahimar.ee3.core.handlers.WorldTransmutationHandler.onWorldTransmutationEvent(WorldTransmutationHandler.java:122) at net.minecraftforge.event.ASMEventHandler_121_WorldTransmutationHandler_onWorldTransmutationEvent_WorldTransmutationEvent.invoke(.dynamic) at net.minecraftforge.event.ASMEventHandler.invoke(ASMEventHandler.java:35) at net.minecraftforge.event.EventBus.post(EventBus.java:103) at com.pahimar.ee3.core.handlers.WorldTransmutationHandler.handleWorldTransmutation(WorldTransmutationHandler.java:92) at com.pahimar.ee3.network.packet.PacketRequestEvent.execute(PacketRequestEvent.java:100) at com.pahimar.ee3.network.PacketHandler.onPacketData(PacketHandler.java:41) at cpw.mods.fml.common.network.NetworkRegistry.handlePacket(NetworkRegistry.java:243) at cpw.mods.fml.common.network.NetworkRegistry.handleCustomPacket(NetworkRegistry.java:233) at cpw.mods.fml.common.network.FMLNetworkHandler.handlePacket250Packet(FMLNetworkHandler.java:71) at iv.a(NetServerHandler.java:1107) at di.a(SourceFile:59) at cf.b(MemoryConnection.java:80) at iv.d(NetServerHandler.java:136) at iw.b(NetworkListenThread.java:57) at bec.b(IntegratedServerListenThread.java:108) at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:702) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:598) at bdz.q(IntegratedServer.java:159) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497) at fy.run(SourceFile:849) --- END ERROR REPORT dcc9ea82 ----------
Im using all the mods from Direwolf20 pack, Latest version. wandering if this is helpful? or other people have same issue. This crashes my game every time a LAN player uses the Minum stone. *the weaker transmution Stone thing*
Try this : Delete the Direwolf20 folder in the FTB folder , back-up your world first , reinstall the mod pack . Good luck !
Ah, I forgot about those, good point, and treecapitator, I could run through a forest with my iron axe and come out with a diamond =p
Though you must realize that there are far easier ways to get diamonds with this mod and the others that most play with. While you could get some obsidian and then Iron from wood or stone it takes a decent bit to actually get to diamond. It seems OP at frist but compare it to the other methods to get diamonds and you wont even bother....I ended up only using the transmuting to get rid of junk wood and stone I had....not with the intent to get diamonds....I mean with mystcraft dense ores I have no need to make diamonds anymore.
Oh man, the sight of 1.4.7 makes me sad, regardless, I just downloaded and installed pre1f and still get these item conflicts, even though my EE3 item Ids are 10698-10703 in the config:
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10445 item slot already occupied by forestry.core.items.ItemLiquidContainer@38f79f92 while adding com.pahimar.ee3.item.ItemMiniumShard@90d4776
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10701 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemMiniumShard
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10444 item slot already occupied by forestry.core.items.ItemLiquidContainer@46ce989e while adding com.pahimar.ee3.item.ItemInertStone@2585d163
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10700 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemInertStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10446 item slot already occupied by forestry.core.items.ItemLiquidContainer@7475cdd3 while adding com.pahimar.ee3.item.ItemMiniumStone@621c1360
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10702 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemMiniumStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10447 item slot already occupied by forestry.core.items.ItemLiquidContainer@213c35f2 while adding com.pahimar.ee3.item.ItemPhilosopherStone@77f9b3e9
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10703 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemPhilosopherStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10443 item slot already occupied by forestry.core.items.ItemLiquidContainer@2a92c388 while adding com.pahimar.ee3.item.ItemAlchemyDust@9632b8e
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10699 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemAlchemyDust
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10442 item slot already occupied by forestry.core.items.ItemLiquidContainer@4dc07c72 while adding com.pahimar.ee3.item.ItemAlchemyBag@182a483f
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10698 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemAlchemyBag
Why are Forestry items 10442 - 10447 conflicting with EE3 when they aren't set to those numbers in the EE3 config?
Oh man, the sight of 1.4.7 makes me sad, regardless, I just downloaded and installed pre1f and still get these item conflicts, even though my EE3 item Ids are 10698-10703 in the config:
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10445 item slot already occupied by forestry.core.items.ItemLiquidContainer@38f79f92 while adding com.pahimar.ee3.item.ItemMiniumShard@90d4776
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10701 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemMiniumShard
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10444 item slot already occupied by forestry.core.items.ItemLiquidContainer@46ce989e while adding com.pahimar.ee3.item.ItemInertStone@2585d163
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10700 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemInertStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10446 item slot already occupied by forestry.core.items.ItemLiquidContainer@7475cdd3 while adding com.pahimar.ee3.item.ItemMiniumStone@621c1360
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10702 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemMiniumStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10447 item slot already occupied by forestry.core.items.ItemLiquidContainer@213c35f2 while adding com.pahimar.ee3.item.ItemPhilosopherStone@77f9b3e9
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10703 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemPhilosopherStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10443 item slot already occupied by forestry.core.items.ItemLiquidContainer@2a92c388 while adding com.pahimar.ee3.item.ItemAlchemyDust@9632b8e
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10699 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemAlchemyDust
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10442 item slot already occupied by forestry.core.items.ItemLiquidContainer@4dc07c72 while adding com.pahimar.ee3.item.ItemAlchemyBag@182a483f
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10698 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemAlchemyBag
Why are Forestry items 10442 - 10447 conflicting with EE3 when they aren't set to those numbers in the EE3 config?
Not sure, especially considering that the default EE3 item range starts at 27000. Try deleting your EE3.cfg file and restarting Minecraft.
No need to be sad with 1.4.7 as it's only a bug fix from Mojang. I have 97 mods running and I was able to switch to 1.4.7 with just a change to which Forge version I was using. At least I was able to start up and load my test world okay. Everything seems to be alright.
No need to be sad with 1.4.7 as it's only a bug fix from Mojang. I have 97 mods running and I was able to switch to 1.4.7 with just a change to which Forge version I was using. At least I was able to start up and load my test world okay. Everything seems to be alright.
Ditto. I got 69 mods updated to 1.4.7 seamlessly. The update only includes one obscure change to the base classes as far as I know so it's unlikely to break everything (or anything).
Not sure, especially considering that the default EE3 item range starts at 27000. Try deleting your EE3.cfg file and restarting Minecraft.
I forgot to mention I changed the default IDs.
I did what you suggested and there is no more conflicts with your default IDs. It irks me that I can't use the range I originally wanted to. Perhaps Forestry has some hidden/non configurable items or something. I'll investigate over there and see if I can come up with something. I appreciate your time Pahimar.
No need to be sad with 1.4.7 as it's only a bug fix from Mojang. I have 97 mods running and I was able to switch to 1.4.7 with just a change to which Forge version I was using. At least I was able to start up and load my test world okay. Everything seems to be alright.
SWEET! Good to hear. It seems whenever I'm about done setting up my configs for 90+ mods, a new version comes out.
"There was a fatal error starting up minecraft and FML
Minecraft cannot launch in it;s current configuration
Please consult C:\users\***\appdata\roaming\.minecraft\ForgeModLoader-client-0.log for further information"
Fatal sounds like a lovely word to put in front of error, makes it seem a lot less crucial..."-.-
Ah i found the problem..I think**
But seriously, that was better than what I can do.
eeeeeee . .eeeeeee . . . 333333
e_____e . .e_____e . . .3______3
e__eeee . .e__eeee . . . .333__3
e__e . . . . .e__e . . . . . .3____3
e__eeee . .e__eeee . . . .333__3
e_____e . .e_____e . . .3______3
e__eeee . .e__eeee . . . 333333
e__e . . . . .e__e
e__eeee . .e__eeee
e_____e . .e_____e
eeeeeee . .eeeeeee
Edit: It looks alot (but still worse than yours) better in the editing format than in the actual thread format.
Yes coming soon tis a mod in building, lovingly crafted by Pahimar (meh gimmi a break it's NYE here and I started a lil early, happy new year to anyone that cares)
I doubt they will come soon. Pahimar is rebuilding this mod from scratch and we are all waiting for just the second prerelease. Also everything that EE2 had should eventually back back on 3, minus red matter, since like Pahimar mentioned dark matter will become better than it was and this red matter will not be needed. Also condensers will be removed but since it will be replaced with something else, no harm done. The only things that will be removed without be replaced, will be collectors (seriously just make a quarry or a tree farm) and the destruction catalysts.
Download EE2 and minecraft 1.2.5, and you're set.
Lol damn, and I thought you would point out a way to make EE2 work on 1.4.6 =p
java.lang.NullPointerException
at com.pahimar.ee3.core.handlers.WorldTransmutationHandler.onWorldTransmutationEvent(WorldTransmutationHandler.java:122)
at net.minecraftforge.event.ASMEventHandler_121_WorldTransmutationHandler_onWorldTransmutationEvent_WorldTransmutationEvent.invoke(.dynamic)
at net.minecraftforge.event.ASMEventHandler.invoke(ASMEventHandler.java:35)
at net.minecraftforge.event.EventBus.post(EventBus.java:103)
at com.pahimar.ee3.core.handlers.WorldTransmutationHandler.handleWorldTransmutation(WorldTransmutationHandler.java:92)
at com.pahimar.ee3.network.packet.PacketRequestEvent.execute(PacketRequestEvent.java:100)
at com.pahimar.ee3.network.PacketHandler.onPacketData(PacketHandler.java:41)
at cpw.mods.fml.common.network.NetworkRegistry.handlePacket(NetworkRegistry.java:243)
at cpw.mods.fml.common.network.NetworkRegistry.handleCustomPacket(NetworkRegistry.java:233)
at cpw.mods.fml.common.network.FMLNetworkHandler.handlePacket250Packet(FMLNetworkHandler.java:71)
at iv.a(NetServerHandler.java:1107)
at di.a(SourceFile:59)
at cf.b(MemoryConnection.java:80)
at iv.d(NetServerHandler.java:136)
at iw.b(NetworkListenThread.java:57)
at bec.b(IntegratedServerListenThread.java:108)
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:702)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:598)
at bdz.q(IntegratedServer.java:159)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
at fy.run(SourceFile:849)
--- END ERROR REPORT dcc9ea82 ----------
Im using all the mods from Direwolf20 pack, Latest version.
wandering if this is helpful? or other people have same issue.
This crashes my game every time a LAN player uses the Minum stone. *the weaker transmution Stone thing*
I play almost every game, so if you would like to add me Steam my name is dragonhippie on that too XD
Try this : Delete the Direwolf20 folder in the FTB folder , back-up your world first , reinstall the mod pack . Good luck !
Though you must realize that there are far easier ways to get diamonds with this mod and the others that most play with. While you could get some obsidian and then Iron from wood or stone it takes a decent bit to actually get to diamond. It seems OP at frist but compare it to the other methods to get diamonds and you wont even bother....I ended up only using the transmuting to get rid of junk wood and stone I had....not with the intent to get diamonds....I mean with mystcraft dense ores I have no need to make diamonds anymore.
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10701 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemMiniumShard
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10444 item slot already occupied by forestry.core.items.ItemLiquidContainer@46ce989e while adding com.pahimar.ee3.item.ItemInertStone@2585d163
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10700 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemInertStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10446 item slot already occupied by forestry.core.items.ItemLiquidContainer@7475cdd3 while adding com.pahimar.ee3.item.ItemMiniumStone@621c1360
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10702 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemMiniumStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10447 item slot already occupied by forestry.core.items.ItemLiquidContainer@213c35f2 while adding com.pahimar.ee3.item.ItemPhilosopherStone@77f9b3e9
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10703 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemPhilosopherStone
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10443 item slot already occupied by forestry.core.items.ItemLiquidContainer@2a92c388 while adding com.pahimar.ee3.item.ItemAlchemyDust@9632b8e
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10699 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemAlchemyDust
2012-12-31 13:30:11 [INFO] [STDOUT] CONFLICT @ 10442 item slot already occupied by forestry.core.items.ItemLiquidContainer@4dc07c72 while adding com.pahimar.ee3.item.ItemAlchemyBag@182a483f
2012-12-31 13:30:11 [INFO] [ForgeModLoader] [ItemTracker] The mod EE3 is overwriting existing item at 10698 (forestry.core.items.ItemLiquidContainer from Forestry) with com.pahimar.ee3.item.ItemAlchemyBag
Not sure, especially considering that the default EE3 item range starts at 27000. Try deleting your EE3.cfg file and restarting Minecraft.
No need to be sad with 1.4.7 as it's only a bug fix from Mojang. I have 97 mods running and I was able to switch to 1.4.7 with just a change to which Forge version I was using. At least I was able to start up and load my test world okay. Everything seems to be alright.
Ditto. I got 69 mods updated to 1.4.7 seamlessly. The update only includes one obscure change to the base classes as far as I know so it's unlikely to break everything (or anything).
I forgot to mention I changed the default IDs.
I did what you suggested and there is no more conflicts with your default IDs. It irks me that I can't use the range I originally wanted to. Perhaps Forestry has some hidden/non configurable items or something. I'll investigate over there and see if I can come up with something. I appreciate your time Pahimar.
SWEET! Good to hear. It seems whenever I'm about done setting up my configs for 90+ mods, a new version comes out.