mryourmumiscool Posted June 12, 2014 Share Posted June 12, 2014 (edited) Edited June 12, 2014 by mryourmumiscool Link to comment Share on other sites More sharing options...
Moderators Munaus Posted June 12, 2014 Moderators Share Posted June 12, 2014 I would recommend posting the link to your pack Link to comment Share on other sites More sharing options...
mryourmumiscool Posted June 12, 2014 Author Share Posted June 12, 2014 I would recommend posting the link to your pack Done. Link to comment Share on other sites More sharing options...
Moderators Munaus Posted June 12, 2014 Moderators Share Posted June 12, 2014 Spamming your topic in other sections is a bad idea. Do it again and I'll give warning points Link to comment Share on other sites More sharing options...
mryourmumiscool Posted June 12, 2014 Author Share Posted June 12, 2014 Spamming your topic in other sections is a bad idea. Do it again and I'll give warning points Sorry about that, im new to this Dont really go on forums Link to comment Share on other sites More sharing options...
Discord Moderator plowmanplow Posted June 12, 2014 Discord Moderator Share Posted June 12, 2014 You should not be distributing minecraft.jar. Remove it from your bin folder. Forge/MC 1.6.4 does not use a coremods folder in any way. All mods belong in the mods folder. No exceptions. It looks like you have extracted some mods into your mods folder. Don't do that. You have the Mekanism Development Kit in your mods folder. This is unnecessary and should be removed. Your ProjectRed is very out of date and has known crash/bug issues. You have the UE API in your mods folder. This is unnecessary and should be removed. If you are going to include IndustrialCraft I recommend looking at this thread. You'll want IC2Fixes at a minimum: You have a few item ID conflicts. Check your ForgeModLoader client log. As for the crash, I see that all the time with folks adding OreSpawn (the net.minecraft.network.packet.Packet24MobSpawn crash). This is specifically related to a conflict between mods for mob spawning. Since you have mostly standard mods I would focus on the less common ones: MCHeli, Defense/Emasher, RivalRebels, etc. I would start by making sure all the mods are at the most recent versions and or dev builds when doing final testing. Link to comment Share on other sites More sharing options...
mryourmumiscool Posted June 12, 2014 Author Share Posted June 12, 2014 You should not be distributing minecraft.jar. Remove it from your bin folder. Forge/MC 1.6.4 does not use a coremods folder in any way. All mods belong in the mods folder. No exceptions. It looks like you have extracted some mods into your mods folder. Don't do that. You have the Mekanism Development Kit in your mods folder. This is unnecessary and should be removed. Your ProjectRed is very out of date and has known crash/bug issues. You have the UE API in your mods folder. This is unnecessary and should be removed. If you are going to include IndustrialCraft I recommend looking at this thread. You'll want IC2Fixes at a minimum: You have a few item ID conflicts. Check your ForgeModLoader client log. As for the crash, I see that all the time with folks adding OreSpawn (the net.minecraft.network.packet.Packet24MobSpawn crash). This is specifically related to a conflict between mods for mob spawning. Since you have mostly standard mods I would focus on the less common ones: MCHeli, Defense/Emasher, RivalRebels, etc. I would start by making sure all the mods are at the most recent versions and or dev builds when doing final testing. Thank you sooo much! I know there are a few ID conflicts with ICBM. I researched it and they are (for some reason) supposed to be like that. But thank you for the info! Much appreciated! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now