plowmanplow

Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. The helpful portions of the log have been removed. Always provide full logs and crash reports.

Always provide the API URL or a link to the client pack details page when requesting custom modpack assistance. Use a pastebin service because attachments don't work here.

The file extension is arbitrary. You could name your file "modpack.potato" and it would work fine as long as the compression algorithm was ZIP and not RAR. Whatever program you are using to compress the archive has options which allow you to set in which format the archive should be created.

Basically, you want someone else to pay for your fun? No one is going to do that. Asking for money for in-game advantages is one thing (and still shady), but to ask for others to fund your pet project from the start? Greedy McGreedster.

Always provide the API URL or a link to your pack details page when requesting custom modpack assistance (I did mention this to you before). Always provide log/crash data in a pastebin service and not directly in the thread.

@Shadowthekidr5: I never said to not start a thread. Neither in this thread or any other. The forum rules/guidelines do not state that either. Start a new thread as you will get no help in this one and you are distracting from the original poster. You almost certainly have a different issue, and even if you didn't you should start your own thread.

Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format only. (does this sound familiar?)

All the SMP mods in the client pack must also be on the server. All "client only" mods must be removed. This is explained quite clearly in one of my original responses to you in this thread. If there is something about that post you don't fully understand please ask specific questions and I will attempt to address them.

"I know it says it cant run media fire" If you know this, then why are you trying to use it when you are experiencing exactly what happens when you do? That's like saying "I know I can't run my gasoline engine on diesel fuel, but I'm going to try it anyway" and then being surprised when the car won't run. Use copy.com or DropBox. Your /bin/modpack.jar is in RAR format. All archive files intended to be used in the platform must be in ZIP format only. The contents of the file are also in a subfolder. You shouldn't be messing with the contents of the Forge JAR in any way. Simply download the Forge universal binary JAR file and rename it to modpack.jar. You have the MC 1.8 version of iChunUtil. You need the latest 4.x version of the mod to be compatible with 1.7.10. Address these issues and come back if you still have troubles.

@Shadowthekidr5: Don't hijack someone else's thread. If you have an issue start a new thread and provide as much detail as possible. Always provide the API URL or a link to the pack details page.

The RAM allocated in the Launcher should never be more than 4G or half your physical RAM, whichever is smaller. No packs require more than 4G and almost no packs require more than 3. Why do you have Flan's mod but no weapons packs? Biomes O' Plenty could stand to be updated. I think 4Space and More Planets are an "either/or" inclusion as they both add some of the same planets/worlds. Galacticraft needs updated. Optifine needs updated. Other than that, the pack looks fine and works for me. Please provide a clean Launcher log from where your pack does not work on your client in a pastebin service.

They say a watched pot never boils... In all seriousness, no, there's no way save removing mods.

By implementing Solder.

I don't see the NotEnoughItems in that crash report.

If that is the case, then you need to re-download the Forge universal binary JAR file, rename it to modpack.jar, and replace your existing file in /bin/.

The same location on the Wiki which provides the download links also mentions the beta/dev builds and provides a link: http://ci.tterrag.com/job/EnderIO/ Directly from your log file: java.lang.IllegalStateException: OpenModsLib not present, not yet loaded or too old (needs at least 0.7.1) You seem to have found an ancient version of OpenModsLib but have the most recent OpenBlocks. Current OpenModsLib is 0.7.3. You should be using the latest Chisel 2 release, not the ancient Chisel 1. Your Enhanced Portals is fatally out of date. 3.0.12 is current. Your Inventory Tweaks mod is from an illegitimate source. Your OptiFine is fatally out of date. Your Thaumic Exploration is very out of date. Where are you even finding these ancient versions of the mods? The download link for Thaumic Exploration 1.7.10 from the MCF forum has the latest build. You have Tinkers' Construct but not the required dependency mod Mantle (0.3.2). Your MalisisCore is fatally out of date and mismatched with MalisisDoors. Careful attention must be paid to the dates and versions of mods. My hope is that as I make suggestions (as I did earlier in this thread) you learn a few things about the proper assembly of a pack and can then turn a critical eye at the entire contents. By the third iteration of my analysis we shouldn't be at a point where I am having to enumerate every mod and version number which needs addressed. Attention to detail is critical in this and nearly every other technical endeavor you embark upon.

You added EnderCore, but did not update EnderIO. That won't work. Why did you update Galacticraft, but none of the other mods I mentioned? Attention to details, man.

Why is your modpack.jar so large? What have you added to it? The newest versions of Forge are fundamentally incompatible with older versions of many mods. You have many mods which require much a newer version of Forge. Audit all your mods and update them to their latest (Forge #1448+) compatible versions.

I would recommend using NEI Addons (release) and NEI Integration over NEI Plugins. I was under the impression Tinkers' worked with TeamCoFH Nether Ores now?

The contents of your modpack archive are in a subfolder. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. You have a mod (Baubles) with a Windows version number "(1)" in the file name. This should be removed. Mods that are checked for deploading, like Baubles, must have the exact filename provided by the mod author. Remove the " (1)" form that file name. bspkrsCore, Baubles, CodeChickenLib belong in the /mods/1.7.10/ folder, not /mods/. Your Iron Chests mod is from an illegitimate source. Always get your mods directly from the mod authors. Replace this mod with the correct version. You have OpenBlocks but not the required dependency mod OpenModsLib. You should be using the 2.3.x_beta builds of EnderIO (and EnderCore). Several of your mods are out of date, some fatally so. At a minimum: AE2rv2, CodeChickenCore, NEI, Galacticraft

it looks like you have wooden pipes on blocks which should be consuming power. Wooden Kinesis Pipes are only for "extracting" power from things like engines or energy storage blocks.

Please provide what has been requested of you. I need your API URL or a link to your pack details page in order to continue. That download URL does not work.

For the love of cheese, use a pastebin service (as I previously mentioned) to provide log/crash data. Don't pollute the thread with that crap. As for what's causing your issue, I'm a bit frustrated. I told you exactly what you needed to do in order to fix the 1.7 version of your pack (i.e. replace ICBM with the current alpha build). You then provide a crash report after adding five more mods, one of which is not required by any mods in your pack (Resonant Engine). You should be learning as you go, but it seems that you are simply kinda-sorta making the changes I recommend and randomly chucking more mods into the pack by the handful. I don't say these things to pick on you, but it seems as though you are not heeding my advice or learning from your mistakes. You should be building or changing the pack methodically. Make changes one at a time until you know exactly what is going to happen and are able to interpret the crash reports and logs.

As long as it's the same pack, the slug won't change. Changing the name is just cosmetic. You need to be using the latest alpha builds of ICBM.

Use the beta builds (current) of that mod.