plowmanplow

Please provide what was asked for, not what you "think" we want. The API URL or a link to the pack details page (where the API URL is easily found) is a hard requirement for proper diagnostics. That is why it was requested. You have Mariculture, but not the required dependency Enchiridion 1.1. The version of Waila you have requires a newer version of NEI. Address these issues and come back if you still have troubles.

The discriminator right now is the change to the Fluid API which happened with Forge #1355. Any mods which deal with fluids will need to match the version of Forge. This can obviously be problematic. As for Cauldron, there is a nicely working version for Forge #1381. All of the "new" versions (including #1388 and #1403) have known major issues in some ways and will cause problems for you if you run up against them (duplicate tile entities, incompatibility with Opis, etc.)

Can you provide some context or details for this question? What do you mean?

I wasn't just making a mild suggestion. We require your API URL or a link to your pack details page in order to provide the proper assistance. Is this your pack? http://www.technicpack.net/modpack/awesome8factory.655815 The contents of your modpack are in a subfolder. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. The BuildCraft mod file you have in your /mods/ folder is not from a legitimate source. Get the latest version from the mod's website, not from a content stealing scraping site. Assuming that's your pack, the pack settings indicate Forge/MC 1.6.4, but the pack contains Forge and a mod for 1.7.10. This needs to be fixed.

If the client is closing back to the Launcher it should be producing a crash report. Put that in a pastebin (like http://pastebin.com ) and provide the link here. You should never need to allocate more than 3G in the Launcher. Setting it higher is typically counterproductive, and setting it higher than half your physical RAM should never be done.

You have the Titan Content Pack (Flan's) but not the required dependency Mecha Parts Pack. This will cause the game to crash when any Titans are accessed in the vehicle builder. It is generally considered bad form to distribute the client config files (/options.txt, /optionsof.txt) with the pack. This will overwrite all the client settings every time the pack is updated and can be quiet frustrating for users. You need to update OptiFine in order to be compatible with the newest Forge. The LiteLoader mods (*.litemod) belong in the /mods/ folder. FastCraft really needs to be updated. That being said, Try building the pack without any of the "performance optimizers" (FastCraft, BetterFPS, OptiFine, CoFHTweaks, etc.) and then adding in what you truly need at the end. Tossing in every one you can find (as it seems you have done) is usually a very bad idea as they often have duplicate and conflicting implementations. FPSPlus is not installed properly, and you probably don't want it anyway. Do you really need NoMoreRecipeConflict mod? Your version is out of date, but if you don't need it to fix a specific issue it should probably be removed. Also, you might be better served by something like MineTweaker which is much less invasive. Your BattleTowers version is old (1.4.9 vs. the latest which is 1.5.2). You have many mods that are doing WorldGen structures and such. One or more of them are conflicting or causing issues. You need to remove them until the pack allows you to create a SSP world and then add them back in individually (latest versions) until you can find the specific conflict. Address these issues and come back if you still have troubles.

Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. This is likely caused by a version mismatch between your selected version of Forge and your included mods. Without the pack link we can only guess.

You need this specific version: http://files.minecraftforge.net/maven/net/minecraftforge/forge/1.6.4-9.11.1.1345/forge-1.6.4-9.11.1.1345-universal.jar

Forge: http://files.minecraftforge.net/

Use MCEdit to remove the MFR conveyor belt at the specified location.

Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. The download URL you provided doesn't work.

You need to remove "(1)" from the file names of your mods. This sometimes causes issues. Your version of Forge doesn't match up with the versions of some of your mods. I recommend updating to the latest Forge and updating all your mods to their latest versions as well. There was a fundamental change to Forge in #1355 and most of your mods are made for earlier versions of Forge but your AE2 is for newer Forge.

If you are using a current build of Forge, you need to be using the IC2 builds from here: http://ic2api.player.to:8080/job/IC2_experimental/ Also, please provide the API URL or the pack details page link for your modpack.

Why are you trying to make a 1.7.2 modpack? There hasn't been any development on 1.7.2 in a long time and it had poor adoption by modders even when it was active. Forge for 1.7.10 is likely a better choice. You have mods for both 1.7.2 and 1.7.10 in your /mods/ folder. This won't work. 1.7.10 mods don't work in 1.7.2.

You have a very old version of Forge for 1.7.10 (#1230). You might consider updating to a newer version, but make sure the mods you are using match the version of Forge. Considering the rest of your mods I feel it is wise to update to the latest Forge. Forge for 1.7.10 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder. CodeChickenLib, bspkrsCore, ForgeMultipart and liteloader belong in the /mods/1.7.10/ folder. You have two different versions of Applied Energistics in the /mods/ folder. Remove the oldest one. You need to update your version of Mystcraft. Your version of Logistics Pipes does not match your version of BuildCraft. Get the latest LP and make sure you update Forge. Your version of ProjectRed is out of date and needs updated. You have two versions of ProjectRed-Base. Remove them all and update. PowerCrystalsCore is for 1.6.4 and should be removed. MFR for 1.7.10 does not require it. Address these issues and come back if you still have troubles.

This belongs in Platform Pagoda. Hopefully a nice forum admin will move it for you. ​Oooooor, you could just fix it by updating to Forge 9.11.1.1345. (the 1.6.4 version which includes the legacy Java fix)

Would have sworn I didn't double post.

That's just it. I don't need your server build. I can turn your client modpack into a server in about 30 seconds. Just provide the API URL and we can continue.

Copy.com public share URLs must be appended with "?download=1" (without quotes) in order to work properly in the platform (your download URL). Forge for MC 1.7.10 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder. The version of Tinker's Construct you have included is not compatible with the version of Forge you have included (your modpack.jar file). You need to update your Forge version.

That's a nice play-by-play you are providing, but until you provide the API URL or a link to your pack details page you'll be doing this alone.

Yes. There was fundamental change to Forge in the way it handles fluids in #1355. Not all mods have updated to that new API and thus will have problems in >=#1355 if they deal with fluids.

You have the Modern Warfare Content pack, but are missing the Simple Parts Content Pack which is a required dependency. You have MoCreatures but are missing the dependency mod Custom Mob Spawner. You have included Forge #1291 but included many mods with versions that require at least #1355 and some which require the latest, latest version of Forge. You need to audit all your mods to make sure you are using compatible versions with your selected version of Forge. (Yes, this is a royal PITA, but it's the world we live in right now)

Don't post log date directly into the thread. Use a pastebin service. Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. That looks like you might have a mismatch between one or more mods and your selected version of Forge. Without the pack to work with I can't be more specific.

And, as usual, always provide the API URL or a link to the pack details page for the modpack in question.

The contents of the /libraries/ folder from where you installed Forge.