plowmanplow

Please post a reply here only after the pack is finished uploading and the pack settings are correct so I'll know to check it out.

Your modpack is not configured properly and does not provide a URL to add into the Launcher. Follow the link you provided and take note of the giant red warning box.

Please note that one must append "?download=1" (without quotes) to a copy.com link to correctly make it a direct link.

Awfully hard to debug a pack I cannot download. The download URL in your pack settings points to a file that does not exist.

The problem is that Forestry has updated to the new Buildcraft API and Binnie has not. Until BinneMods get updated you will have to leave it out.

Forge Multipart goes in your mods<MCVERSION> folder, where <MCVERSION> is the version number of MC you are using. For 1.6.4 it would be mods1.6.4. Delete all your current Forge Multipart JAR files and download the latest version for 1.6.4 from here: http://files.minecraftforge.net/ForgeMultipart//index_legacy.html

Always provide the API URL for your custom modpack when requesting assistance. Errors in the pack settings can cause problems and the only way to diagnose them is by having the full API URL. The link you provided is not a direct link. If you click on a link and it takes you to a new page with a link/button to download the pack, it won't work in the launcher. You will need to change the "www" in the link you provided to "dl". Your Pack: Your modpack.jar file is messed up in every possible way. It is named incorrectly (must be all lower case modpack.jar), it is in RAR format instead of ZIP format, the contents are in a subfolder, etc. The modpack.jar file is simply the correct Forge universal binary JAR file renamed to modpack.jar. Nothing more. Your "Mods" folder should be named "mods" (lower case). Your OptiFine mod is out of date. Many of your mods have odd names and are missing version numbers. The implication is that you did not get them from the author's preferred distribution channels. See this post: Fix these issues and come back if you still have troubles.

I have occasionally had this happen. Always comes back after that and I have been able to proceed with creating/editing packs.

Not sure what to tell you. The Cauldron installers for "1.6.4-1.965.21.204" and "1.6.4-1.965.21.205" work fine for me as of 11:50am EST 20141201. If you suspect it is a library issue, re-run the installer into a new folder. Try starting the server in that new folder with no mods or plugins. If it starts fine the issue is not with Cauldron.

Provide the API URL for your custom modpack so that we may provide assistance.

Those indicate that the server has mods which the client does not, or that there is a configuration mismatch between the client and server. Please provide the API URL for your custom modpack.

If this is only for custom modpacks please provide crash reports and/or FML logs (in a pastebin or spoiler tag). If this is for all packs, including the ones maintained by the Technic group, the issue belongs in the respective Trackers (located at the top of this page).

This: { "minecraftArguments": "--username ${auth_player_name} --session ${auth_session} --version ${version_name} --gameDir ${game_directory} --assetsDir ${game_assets} --tweakClass cpw.mods.fml.common.launcher.FMLTweaker", would become: { "minecraftArguments": "--username ${auth_player_name} --session ${auth_session} --version ${version_name} --gameDir ${game_directory} --assetsDir ${game_assets} --tweakClass cpw.mods.fml.common.launcher.FMLTweaker -Dfml.ignoreInvalidMinecraftCertificates=true", Please use a pastebin or spoiler tag for long copy/paste content.

Getting Mods: Building your pack: Making your server:

You have NetherOres installed but are missing the CoFH dependency libraries CoFHCore and ThermalFoundation. Your pack settings are configured to be MC 1.8. You need to change that to MC 1.7.10. Your modpack archive has an extension of ".jar". This should be ".zip".

That link does not work for me. Page not found. Is the file shared publicly?

Please provide your API URL. Why are you appending the filename to the copy.com link? Copy.com public share links look like this: https://copy.com/HtyKLw3KnuMYxqbH and you make that direct by appending "?download=1" (without quotes).

If you have neither the time to play, or the 5 minutes it takes to set up a server... I guess I don't get the purpose here. Not trying to be confrontational, just curious.

If you have enough RAM in your desktop you could easily host it there.

A 10-20 slot server running a custom modpack is not "small". 2-3 slot would be small. I think you underestimate the time and effort involved.

Is this some custom modpack? If so, you might want to follow up with the pack creator.

iChunUtil for 1.6.4 is version 2.4.0, not 3.0.0 The version of Golem World you included is for Forge/MC 1.7+, not 1.6.4. The author doesn't seem to be making the 1.6.4 version readily available. I don't have time to search for it myself. You have Magic Bees mod but not the (big) Forestry mod on which it depends. You have Binnie Mods but not the (big) Forestry mod on which it depends. You have ICBM mod but not the required dependency mod Universal Electricity. You have Thermal Expansion mod but not the required dependency mod CoFHCore. Cube Bots mod is for Forge/MC 1.5.2, not 1.6.4 and has no newer versions. You have block ID conflicts between CFM and other mods. You have a large number of item ID conflicts which need to be resolved. You have included no config files in your modpack. This is always bad, and as is the case for your pack, fatal.

Yes. You would need to implement the Solder API which will increase your limit up to 10 packs. This is non-trivial and assistance will be very sparse.

@Pegabyte: Please start a new thread in Platform Pagoda. Include a link to your custom modpack API URL and a link to your crash report. Also, list any client only mods you have removed from the collection used on the client when assembling your server.

Your modpack archive is different, but you have not incremented the version number in your pack settings page. Unless the version number increments/changes the client (after a restart) will never be notified that a new version is available and prompt you for an update. Your modpack archive is missing the contents of the mods1.7.10 folder. While these files should be downloaded automatically (usually), it is still better to include your selected versions in the modpack. In the event that the automated service has problems the pack will not work properly if they aren't included.