plowmanplow

Your pack version number is currently 1.0. This implies that you aren't incrementing it when you update your pack data or metadata. Your /bin/modpack.jar is named "modpack.jar.jar". Google "windows explorer always show file extensions" to learn how to prevent this. The Forge JAR does not belong in /mods/ and should be removed.

mods\CodeChickenCore-1.9-2.0.1.53-universal.jar You have included CodeChickenCore for Forge/MC 1.9 instead of the one for 1.7.10. Get the latest CodeChickenCore for 1.7.10 and you should be fine.

As @JaariAtmc mentioned, your modpack version is still at 1.0. Since you have changed your pack data this will need to be incremented. Always increment your pack version number any time you alter your pack data or metadata. Your Damage Indicators mod is not from a legitimate source (pretty sure I've mentioned this to you before). If you are turning this into a server make sure you do not attempt to use one of the Cauldron derivatives. The Lord of the Rings mod does not work well with anything but Forge (it has a fatal issue when generating structures), and the LotR team specifically declines to support anything but Forge.

You have somehow included part of my domain's URL in your modpack location URL: https://www.circlecraft.info/platform/dl.dropboxusercontent.com/s/90izyb1j70k5g1u/Massive%20Dig.zip Your URL should begin with "https://dl.dropboxusercontent"

You need to allocate more memory to the Launcher in the Launcher Options. Never allocate more than half your physical RAM or 4G, whichever is smaller.

Personally, I find Thermos more to my liking, but to each their own. Also, necropost.

Sorry, man. That stuff is just so amazingly outdated, and was EXTREMELY non-standard even when it was current. I don't think I'm going to be able to help you as long as metaworlds is in the pack.

Work through this methodically. Go through the process of making a server again and simply copy over your current world to this newly created server. See if this fixes the issue. If it does then your old one just got corrupted somehow. If it doesn't then you have some more fundamental issue with the modpack.

I'm working on a list for hosting. https://www.circlecraft.info/hosts/

Try this instead: Making a server You can replace Forge with Thermos if you wish.

The URL in your pack setting is currently formatted correctly.

In this context, "trailing" means "at the end" or "the last thing in the line". Example: The small ducks were trailing their mother across the pond. When downloading mods, it is critical that they are downloaded from the locations provided by the authors. For example, this is the location maintained by the author for the Damage Indicators mod. This and this are the locations where the Journeymap author maintains the downloads. When in doubt, check where NotEnoughMods links to for the mod you are looking for.

That is coming from the mod "Waila". You can open the options for Waila using the 0/Insert key on the number pad.

Close, but not quite. Please note: Remove any trailing "?dl=0" or "?dl=1" (including the question mark) Your pack version number is still at 1.0. Any time you alter the pack data or metadata, you must increment the pack version number. You pack should contain only three folders: bin, config, and mods. The bin folder (as your does) should only contain the file "modpack.jar". You have not obtained legitimate versions of either JourneyMap or DamageIndicators. TreeCapitator mod belongs in the /mods/ folder. bspkrsCore is where it should be in the /mods/1.7.10/ folder.

Your pack settings are not configured correctly. This is the URL currently configured for your pack (not even sure how you got the platform to accept it) https://www.dropbox.com/s/5myvkcg28rfg6iu/NewModpack.zip?dl=0https://www.dropbox.com/s/jtc84phgdjz872g/ic2modpack.zip?dl=0https://www.dropbox.com/s/batu8sfk35fe5if/okej.zip?dl=0 As you can see, that is completely incorrect. After selecting the proper public URL for your pack (not three of them concatenated together) please follow these directions: Dropbox public URLs should be altered in this fashion: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1" (including the question mark). After you fix the location URL and update your pack (including the pack version number) please respond here and I will take a look at the pack contents.

A combination of TekkitCustomizer and PermissionsEX/ModifyWorld works for me.

MediaFire is not a valid file host for the platform. The links change over time and do not properly resolve to direct links. I'm attempting to collect information on valid hosts here. The contents of your modpack are in a subfolder. The three required folders for your pack (bin, config, mods) must be at the top level of the folder structure inside your modpack archive. Your pack has no config files. This is always bad. One should build and debug a pack in a test environment (such as the BareBonesPack) so that you can adjust the configs before assembling your pack. Some of the mods in /mods/ belong in /mods/1.7.10/: ForgeMultipart, ForgeRelocation, ForgeRelocationFMP, MrTJPCore. Additionally, you have two different versions of ForgeMultipart. One is in /mods/ and one in /mods/1.7.10/.

Always provide the API URL or a link to the platform pack page. This allows us to analyze the metadata associated with your pack as well as the pack contents. Make sure you are incrementing the pack version number any time you alter the pack data or metadata. The contents of your pack are in a subfolder inside the archive. The top level folders (for your pack they are bin, config, Flan, mods) must be at the top level of the folder structure inside the modpack archive. You should probably be using Forge #1614 for your modpack.jar. The Modern Warfare Flan's pack requires you to have Simple Parts Pack (the dependencies for a pack are listed at the top of their page). Your TConstruct mod is quite out of date. This goes for OptiFine and ProjectRed as well.

There is often a large gap between what one "can" do and what one "should" do. In this case, yes, it is functional to simply change the "dl=0" to "dl=1". However, just because this works does not make it "correct". My guidance on how to alter the link is the proper and only procedure to make the URL truly direct. This means that with the method I described the web server/host will respond with an HTTP/1.1 200 OK. If you only change the value of the "dl" parameter, the web server will respond with a HTTP/1.1 302 which will redirect the client to the URL which I suggested should be used in the first place. Please do not spread misinformation.

Your modpack URL does not work with the Launcher. You will need a direct URL. You can try using the URL provided by the "Download" button when you follow the URL you currently are using with your pack. Your modpack is not valid. You need a /bin/ folder with the "modpack.jar" file which is the Forge universal binary JAR file for your version of MC renamed to "modpack.jar". Your JourneyMap and Damage Indicators mods are not from legitimate sources. The bspkrsCore mod belongs in /mods/1.7.10/ not /mods/. This would also hold true for the server installation.

Legends even ships with (or it did once if it doesn't now) KCauldron. Yive's Mirror is probably where you want to start.

I do not. Unfortunately I won't have time to run anything to ground until at least Sunday or Monday. If you haven't figured it out by then, and still want to, ping me and I'll see what I can find.

No, you can't use the 1.6.4 libraries with 1.7.2. As for your options? If you truly cannot find them then you are likely out of luck. There is positively no reason to require the use of an installer short of laziness or an attempt to line their pockets with click-revenue. The fact that the mod hasn't been touched in years would suggest some combination of the former and a complete lack of interest in long term support.

I would normally do a full analysis... but 1.7.2 with a forced old version of Forge? Meh, can't be bothered. Your log file probably says something like: [main/FATAL] [Metaworlds/]: Libraries for metaworlds missing! Might want to fix that.

Always provide the API URL or a link to the pack's platform page when requesting custom modpack assistance. WIthout this we will be unable to provide a comprehensive analysis. Dropbox public links should be altered in the following manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1" (including the question mark). You should not be altering the names of your mod JAR files in any way except in extremely uncommon, specific circumstances. Yes, this means you should re-download every single mod in your pack to correct this issue. You should not be including the /mods/Voxelmods/ folder in your modpack archive. This will overwrite client settings each time the pack is updated. The error message you included does not provide sufficient information. Please close the Launcher, remove any existing Launcher log files, start the Launcher and try to install the pack. Close the Launcher if it fails and provide the Launcher log in a Pastebin Service Bear in mind that your pack is extremely large and will likely not function on machines with less than 8G of RAM with 3-4G allocated in the Launcher.