plowmanplow

If you change this: https://www.dropbox.com/s/ssqsv9tgyavtrg1/Modpack.zip?dl=1 to this: https://dl.dropboxusercontent.com/s/ssqsv9tgyavtrg1/Modpack.zip I assure you it will work just fine.

As JaariAtmc indicated, your modpack location (download URL) has changed and no longer works. Also, DropBox links should be changed in this manner: Change "www" to "dl" Change "dropbox" to "dropboxusercontent" Remove "?dl=1" or "?dl=0" from the trailing end of the URL

Your pack metadata indicates that you are on version 1.0. This is often an indicator that you aren't incrementing the pack version number when you change the pack data/metadata. Always increment the pack version number any time you change the contents of your modpack archive, the location (URL) of that archive, or any data specific to the pack on your pack settings pages.

As stated in the last thread you started: Custom server support requests belong in Server Op Swap Shop. Hopefully a forum mod will move this. Always provide the API URL or a link to the Platform Pack Page when requesting custom modpack assistance (even for a server). Making a server basically means: 1) Do This. 2) Switch to Thermos.

You have multiple mods from illegitimate sources. Any mod named in the format of "ModName-Mod-1.7.10.jar" or "Mod-Name-1.7.10.jar" is almost surely from a sketchy content stealing site.

You can safely remove the Morph mod from the server and none of its features will be available even if the clients have it installed.

It's complaining about: [1.7.10]WorldStateCheckpoints-client-1.7.10.r03.jar NEIAddons should be removed.

Waila (but not any Waila plugins/addons) and Wawla have server-side components and should be on the server if the client pack has them.

Custom server support requests belong in Server Op Swap Shop. Hopefully a forum mod will move this. Always provide the API URL or a link to the Platform Pack Page when requesting custom modpack assistance (even for a server). Making a server basically means: 1) Do This. 2) Switch to Thermos.

Custom modpack support requests belong in Platform Pagoda. Hopefully a forum mod will move this. Always provide the API URL or Platform Pack Page link for your custom modpack.

No. The launcher doesn't care what the actual stored ZIP file name is. It will name the file "slug-version.zip" in your /cache/ folder. There are weapons packs that are extracted into folders inside the /Flan/ folder. That folder should only contain weapons pack archives. All mods should be downloaded from their respective authors' approved distribution channels (i.e. Curse, GitHub, MineCraftForum, their website, etc.). Any mod named in the format of "ModName-Mod-1.7.10.jar" is highly suspect. WECUI is the World Edit Client User Interface. It is a LiteLoader mod and gives you visual in-game selection boundaries. Very handy.

Copy.com links must have "?download=1" appended to them. Keep in mind that copy.com is closing in May. The /bin/ folder in your modpack should only contain the file "modpack.jar". Your /bin/modpack.jar is an absolutely ancient version of Forge. You should be using the latest version for 1.7.10. Your pack should not contain the /cache/ or /coremods/ folders, nor their contents. The weapons pack files in the /Flan/ folder should not be extracted. Damage Indicators and Rei's Minimap mods are not from legitimate sources. If you are using WorldEdit you should also have LiteLoader and the WECUI Litemod.

DropBox links should be changed thusly: Change the "www" to "dl". Change the "dropbox" to "dropboxusercontent". Remove the "?dl=0" or "?dl=1" completely. That being said, it is failing on unzip by the Launcher because one of your files likely has an odd (non-ansi-standar) character in a file name. Looking through it a couple times I wasn't able to catch it, but I only spent about 5 minutes. Good luck.

Any time I see a "1.0" version I always remind folks to always increment their pack version number any time the pack data or metadata is altered. You should be using a development environment (like my BareBonesPack) to build your pack. Dumping hundreds of mods in a folder and trying to start it up is a path to heartache and sorrow. the file "MDK-1.7.10-8.1.9.265.zip" in your /mods/ folder is the Mekanism development kit and is only used by mod developers. It should be removed. We will need a clean Launcher log. Delete .technic logs, open the Launcher, try to install the pack, let it fail, close the Launcher, pastebin the Launcher log.

I'm aware that it's possible, but I've never bothered to figure out how (no interest).

The listed files (forcedchunks.dat) are corrupt and will need to be removed.

This is why mods have config files. Check the AM2 configs. You should be able to use this post to see how to make that change to a proper value. That post is about block/item ID conflicts, but the same process applies to Enchantment IDs.

ChickenBones' Mods

When posting the log for a pack, please provide the pack's fml-client-latest.log and not the launcher log (which you provided). [B#347] [17:23:03][SEVERE][noppes.npcs.enchants.EnchantInterface:49] java.lang.IllegalArgumentException: Duplicate enchantment id! class noppes.npcs.enchants.EnchantDamage and class am2.enchantments.EnchantMagicResist Enchantment ID:100 You have an enchantment ID conflict for ID 100 between CustomNPCs and Ars Magica 2.

Yes, they should safely regenerate. You might have to visit any chunks with chunk loaders in order for them to re-register since you'll be removing the forcechunks.dat files.

You have a few mods which really don't belong on the server, even if it will start with them present: JourneyMap, NotEnoughKeys, NEIAddons, NEIIntegration, TiCTooltips, WailaHarvestability. [19:39:42] [Server thread/WARN] [FML]: Unable to read forced chunk data at D:\Downloads\minecraft\custompacks\Ravius\Ravius Server\.\world\DIM-112\forcedchunks.dat - it will be ignored java.io.IOException: Root tag must be a named compound tag One or more of your forcedchunks.dat files are corrupt (I removed that one and it dies on DIM-110 after which I deleted them all). java.lang.RuntimeException: java.io.IOException: Root tag must be a named compound tag at elec332.core.server.ServerHelper.fromFile(ServerHelper.java:308) ~[ServerHelper.class:?] at elec332.core.server.ServerHelper$EventHandler.onWorldLoad(ServerHelper.java:204) ~[ServerHelper$EventHandler.class:?] The data file "world/elec332/generalData.dat" is corrupt. Seems like it's safe to just remove it as the mod will regenerate the file if it is missing.

I agree that it would be good to get some input from the Technic folks, but this may also be something that HostGator is specifically doing to prevent hot-linking or blocking something that the Platform is doing/using. I'll mention that you have old packs that are still working.

There must be either something wonky with the way the platform queries the URL for validation, or where that query is originating from which is causing this issue. My own URLs work from my commercial host, and I was able to successfully test using a free account from Weebly. Every test I can perform says that your URL is perfectly valid.

I have revived the question in IRC. All I can do is hope for a response.

You need to keep the "http://" at the beginning of the URL.