plowmanplow

I didn't want you to think that no one is looking at this. I verified the process by which the platform attempts to validate a direct URL to a monolithic modpack archive. I implemented that process in a test environment and your " http://magfilms.co.uk/magpack/6.3.zip " link should be valid. I've been in communication with the web devs and they are looking into things on their end.

Your modpack.jar has the wrong contents. The modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar.

copy.com links must be appended with "?download=1" (without quotes) in order to make them direct. It looks like you have shared the folder containing the modpack archive instead of the actual file itself. The URL must point directly to the file or it won't work in the platform. ArmorStatusHUD requires bspkrsCore mod. Fix these issues and come back if you are still having troubles.

You changed your modpack archive, but did not change the pack version number. Every time you change your modpack archive you must also change/increment the pack version number or the Launcher will never be notified that an update is available. You now have two copies of CodeChickenCore, EnderStorage and NEI mods in your pack. This will crash on startup. Remove the older versions. You still haven't updated AE2. You removed CoFHCore. This is a required mod for all of the TeamCoFH mods. You should only have removed CoFHLib, not CoFHCore.

You should probably update to the latest AE2rv2 beta. Your BigReactors is very old with known issues. Update. Your ChickenBones mods (CodeChickenCore, ChickenChunks, Ender Storage, NEI) are mismatched and some are very old. Make sure you have the latest matching versions from the author's website. Factorization mod is very old with known issues. Update. CoFHLib is for developers only and should not be in a client modpack. You have OpenBlocks mod but not the dependency library OpenModsLib. Get the latest matching versions from the author's website. Most of your mods are out of date and have known issues. Update the latest versions. Fix these issues and come back if you still have problems.

Always provide the API URL or the Technic pack page link here when requesting assistance for a custom modpack. I have allocated 4Gb of ram. i am using Java 7 64 bit And then I see: [B#234] [12:27:22] [main/INFO]: Java is Java HotSpot™ 64-Bit Server VM, version 1.8.0_25, running on Windows 7 So, you are running Java 8, not Java 7. [B#234] Exception in thread "main" [12:27:24] [main/INFO]: [java.lang.Throwable$WrappedPrintStream:println:-1]: java.lang.NoClassDefFoundError: openmods/asm/VisitorHelper$TransformProvider This line indicates that you likely are missing a dependency library. It is impossible to know which until you provide one of the links I mentioned previously.

Always provide the API URL or the link to your Technic pack page when requesting custom modpack assistance. It allows us to troubleshoot the entire process instead of just one aspect (your download archive, for instance). Please do so.

In my experience, Cosmetic Armor a bit wonky: It tends to reset which is displayed between sessions and server restarts. Other people usually seem to see the base armor, not the cosmetic.

Just to make sure someone doesn't see this and think that copy.com doesn't work: copy.com works just fine as long as you create your URLs properly. Share the file and get a copy.com public URL. Append "?download=1" (without quotes) to the URL and you have a direct link that will work with the platform.

You need to add the legacyjavafixer-1.0.jar to your pack to make it compatible with Java 8.

Sure. You can't use any plugins, which makes protecting things (very) difficult if it's a public server, but it'll run fine.

Please provide the link to your modpack page.

A couple corrections: The Forge universal binary JAR file should be downloaded and renamed to "modpack.jar". Nothing more, nothing less. Don't extract it or modify it in any way. It belongs in the /bin/ folder. The required folders (/bin/, /config/, /mods/) must be at the top level of the folder structure inside the modpack archive. Do not put them in a subfolder.

That is likely just an issue with the construction of your modpack and it would be best if you posted a new thread in the Platform Pagoda forum. Make sure to include a link to your Technic Platform modpack page.

Or, you could use any of the free dynamic DNS services (like https://duckdns.org/ ) and never have to worry about it.

This post goes over the process I use for building and testing packs:

Always provide the link to your pack page. You have the mod HarvestCraftWaila-mc1.6.4-1.0.4.jar which is for Forge/MC 1.6.4. There is no 1.7.10 version of this mod so it will need to be removed.

Your pack page (for my convenience): http://www.technicpack.net/modpack/industacraft.568756 You should not be including the /mods/VoxelMods/ folder in your modpack archive. This will overwrite player's local settings when the pack updates. Your ChickenBones mods are woefully out of date. (CodeChickenCore, NEI) One or more of your mods (Reika's mods) are not compatible with the new BuildCraft 6.3. You will need to downgrade to BC 6.2.x until the other mods update their APIs.

The Mystcraft API is only for use by mod developers and should not be in your modpack. Your Mekanism build is very old and has known major issues. This should be updated to 6.0.5.46. Your CoFHCore has an odd file name and does not match the version of Thermal Expansion in the pack. The implication is that you did not get the mod from the author's preferred distribution channel. This is always bad. Get the latest 1.6.4 version (2.0.0.5). You are missing Universal Electricity mod which is required for the 1.6.4 version of MFFS, and your Calclavia Mods are out of date. You should updated them all to the latest 1.6.4 versions... The state of affairs with Calclavia's mods and ICBM (no longer maintained by Calclavia) is a hot mess. Some of Calclavia's domains no longer work and many of the links from his pages are nonfunctional. I do this all the time and it still took me 45 minutes to find working, matching versions of all of the Calclavia related mod which worked correctly together. In order to save you a lot of time, I have assembled a ZIP with all of the Calclavia related mods and a new full set of deconflicted config files. Remove your version of MFFS and Resonant Engine and use the files from my download. I also tossed in some NEI helper mods along with Waila. Feel free to remove them but they are super handy. Calclavia Mods for 1.6.4: https://copy.com/cjqfNUKCNyoR72AE?download=1 Give all that a shot and come back if you are still having troubles.

This post should get you going in the right direction:

I'm assuming that is someone else's pack. Feel free to use it, but it's a hot mess as far as assembly is concerned. I created a server with the pack by removing the client only mods and was able to connect just fine. This guide may help you repeat my success:

What The_Doctors_Life said. [19:32:33] [Client thread/ERROR]: Caught exception from ReactorCraft Reika.DragonAPI.Exception.IDConflictException: The mods were not installed correctly: CONFLICT: Potion IDs: biomesoplenty.common.potions.PotionParalysis@3de02302 @ 31 Check your IDs and change them if possible. You have a potion ID conflict. This post on resolving ID conflicts should help you. The method for resolving block/item ID conflicts is the same as with potions:

Your modpack.jar is titled "modpack.jar.jar". Google "windows file explorer always show extensions" to learn how to prevent this.

You need to change the suffix of the URL to be "dl=1" instead of "dl=0". The contents of your modpack archive 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 names of your mod files indicate that you are not getting them from the mod author's preferred distribution channels. This is always bad, often results in using outdated mods, and increases the risk of obtaining malware. This post on getting mods may help you:

No, those mods work fine together, and on a Mac.