Is it possible for so many people to be incapable of such a simple task, or are they simply to lazy to edit a simple document?
Perhaps that the best solution is that the dev make the correction at the source, then there is no problem....
With the actual configuration ALL user who play BC and IC have to make the change...
I have the same problem (conflict between BC and IC), there is my logs :
2012-12-01 22:03:55 [INFO] [STDOUT] CONFLICT @ 3808 item slot already occupied by ic2.common.ItemBlockRare@270f1c25 while adding buildcraft.core.ItemBuildCraft@5100d52b
2012-12-01 22:03:55 [INFO] [STDOUT] CONFLICT @ 3807 item slot already occupied by ic2.common.ItemBlockRare@445ea9d2 while adding buildcraft.energy.ItemBucketOil@22df3d0f
2012-12-01 22:03:55 [INFO] [STDOUT] CONFLICT @ 3810 item slot already occupied by ic2.common.ItemBlockRare@6e21b5ab while adding buildcraft.core.ItemBuildCraft@671e2609
2012-12-01 22:03:56 [INFO] [STDOUT] CONFLICT @ 3813 item slot already occupied by ic2.common.ItemBlockRare@290d1875 while adding buildcraft.core.ItemBuildCraft@1ac0be61
2012-12-01 22:03:56 [INFO] [STDOUT] CONFLICT @ 3814 item slot already occupied by ic2.common.ItemMachine2@d65f546 while adding buildcraft.core.ItemBuildCraft@20c9cd89
2012-12-01 22:03:56 [INFO] [STDOUT] CONFLICT @ 3815 item slot already occupied by ic2.common.ItemMachine@20d4ee30 while adding buildcraft.core.ItemBuildCraft@7b61a226
2012-12-01 22:03:56 [INFO] [STDOUT] CONFLICT @ 3816 item slot already occupied by ic2.common.ItemElectricBlock@46dcac12 while adding buildcraft.core.ItemBuildCraft@41a4f616
2012-12-01 22:03:56 [INFO] [STDOUT] CONFLICT @ 3811 item slot already occupied by ic2.common.ItemBlockRare@7d5296f3 while adding buildcraft.transport.ItemGate@39346bcc
Oh damn thx !
Sorry !
Thx a lot !
Sorry for the noise, but I am searching the client file for minecraft 1.2.5, version 1.1.11.
Do you have some link where I cand find this file ?
Thx a lot.
Sich
yep I understand this, not a problem.
The most important thing is to know that the job is in progress.
We just have to wait.
Thanks for your answer.
Sich
ok, but the 1.2.5 version is at least planned ?
I don't need any ETA, but just if the work is in progress...
Thanks
