plowmanplow

Caused by: net.technicpack.rest.RestfulAPIException: Error in response: Modpack does not exist This claims your pack doesn't exist.

Copy.com works fine, you just have to correctly modify the link. Copy.com public share URLs must have "?download=1" (without quotes) appended to them in order to get a direct link.

You are launching the minecraft_server.jar instead of using the launch script provided with the server to start Forge.

Ahh, if you have 8G then setting the Launcher to close isn't an issue. Launcher Options (top right) -> Java Settings (2nd tab) -> Memory (set to 2GB)

That's not going to be enough to launch a pack of that size. You'll need to allocate 2G. I also highly recommend setting your Launcher to close after starting a pack and keep as few other things running as possible. You only have 4G of RAM total and between the custom modpack and Windows there won't be a lot left over.

Scratch that. I missed this the first time through: [b#283] 2015/03/16 12:44:40 [iNFO] java.lang.OutOfMemoryError How much memory are you allocating in the Launcher?

Looks like your graphics card or drivers don't like one of the mods in your pack. Are you certain your video drivers are up to date?

You should be using the Forge universal binary JAR file. As for your pack, I am able to add it to my launcher and start the pack. If you are not able to do so please provide your logs (crash-report, FML logs, etc.) in a pastebin service and put the link here.

You have changed your modpack archive but have not changed/incremented the pack version number. The Launcher is not notified that a new version of the pack is available unless the pack version number changes.

<sigh>

Your pack settings are providing a download location which does not work. You seem to have changed the modpack archive download but not the pack version number. The version number must be changed/incremented every time the modpack archive is changed in any way.

I'm certain I did not click Submit more than once.

Your pack settings indicate a 1.7.10 modpack but you have included the 1.6.4 version of Forge. You should not be including the /journeymap/ folder in your pack. This will overwrite local player options when the pack updates. You should be using the latest beta of AE2rv2. You should not be including the IC2 API in your pack. Millenaire mod is not installed correctly. Open the ZIP and follow the author's instructions.

What that does is change the load order of the mods inside Forge. AM2 has some code to detect existing enchantment IDs and not overwrite them. If Forge loads AM2 last it tries its best to make sure it doesn't conflict with anything else.

java.lang.IllegalArgumentException: Duplicate enchantment id! class noppes.npcs.enchants.EnchantDamage and class am2.enchantments.EnchantMagicResist Enchantment ID:100 Duplicate enchantment ID for #100. Renaming the AM2 mod to start with "zz_" (without quotes) is an easy remedy.

The copy.com link seems to be invalid.

We will need your API URL or a link to your pack details page in order to provide additional assistance.

I already responded to your other thread. Starting multiple threads for the same issue is distracting and unhelpful.

For a modpack to be recognized by the Launcher it must contain a "modpack.jar" file in the /bin/ folder. That modpack.jar file is the correct version of the Forge universal binary JAR file renamed to modpack.jar.

CoFHLib is for mod developers and should never be in a modpack or server. Nearly every mod in your pack is out of date. Some of those versions have known critical issues. You have OpenBlocks mod but not the dependency mod OpenModsLib. You have two of the three mods for GalactiCraft. You are missing MicdoodleCore. Address these issues and come back here if you are still having issues.

Your /bin/modpack.jar is the wrong file. The modpack.jar should be the correct version of the Forge universal binary JAR file renamed to modpack.jar. You should be using AE2rv2beta10 Buildcraft is out of date Your CoFH mods are out of date Your ChickenBones mods are out of date

Updated to 1.8 #1337 "Latest" The Launcher no longer requires Forge for 1.8 to have an edited version.json file in order to function properly.

By and large, we are here to help others fix and debug their packs, not to create packs for them. This is even more true in instances where folks wish to create servers for their packs. If one cannot take it upon themselves to get a pack running, operating a server will likely be an exercise in frustration. Read this thread on making a pack: and come back here if you get stuck. Once that is resolved, read this thread on making a server: We'll teach you how to fish. Passing out free fish isn't really our thing.

Believe it or not, allocating more RAM to the server (or client, for that matter) than one needs is usually a bad idea. All the unnecessary RAM can cause the garbage collector to work harder that it should at times resulting in funky lag spikes and odd behavior. It's usually a good idea to start low and work your way up as needed. By hard-terminate, I just mean hang/crash/improper shutdown. Basically, instances where the internal server logic processes hung and the data on persistent storage (i.e. hard drive) can become inconsistent.

Always provide a link to the API URL or pack details page when requesting custom modpack assistance. You have provided no information which would allow us to assist you.