plowmanplow

Your modpack.jar file is in 7z archive format. All archive files intended for use by the platform must be in ZIP archive format. You modpack.jar has all the files inside a subfolder in the archive. Everthing should start at the top level of the archive. That being said, you shouldn't be messing with the modpack.jar file at all. Just download the Forge universal binary build #965 and rename it to modpack.jar. You have Galacticraft installed but are missing GalacticraftPlanets. Also, it is an old version of the mod. Get the latest version of all 3 files for Galacticraft. Update your Mekanism to the latest build. You need the iChunUtil mod which Morph and Hats require. Once you get the pack functioning locally and have working config files you need to include the whole config folder in your modpack. You are fortunate that you have so few mods installed as these mods don't generate their config files with any conflicts.

This is the version of your pack that was working for me. https://copy.com/YazKYhiVYTor

Odd. Wasn't even aware they had an application on the PC. I'll have to look into that. I just use the web interface.

Your download URL must be a direct link. Mediafire is a poor choice for that. The public/free service I use is copy.com, but there are others that work as well. If you don't have a copy.com account and want to create one, using this link ( https://copy.com?r=cZHpBn ) will give both of us 5 extra gigs of storage.

It does look like it is erroring out while trying to extract some of the millenaire stuff. I re-downloaded the mod, replaced the millenaire folders in mods, re-zipped the pack and it now works. Give that a shot. I don't know if it is the platform or Java that is being super picky about certain characters in file names but this may be the source of the problem.

Hmm, "how" to which question? There were a few from me.

Not really. The pool of 1.7.2 mods to pull from is so shallow at this point (although it is filling up a bit) that you've definitely hit the high points.

That is because you made your download URL a RAR archive instead of a ZIP archive. Any archives intended to be used in the platform must be in ZIP format only.

Just put that "Chocolate" folder in the same location as bin, config and mods. And please refrain from personally messaging me just to prod me into checking the thread. I check back as often as I can only now I have two separate personal message threads here and two in my email to delete. I'm happy to help but the out-of-band distractions are just that.

Well, not quite You still have the same, old version of Forge. Update to 965. You have not properly installed ChocolateQuest (Better Dungeons) Making these changes allowed me to start the pack. However, there are ID conflicts between DivineRPG and SoManySwords, BetterDungeons and BetterFurnaces.

This is a case of the latest, bleeding edge version of Forge not always being the best option. You are using Forge build #1057. IC2 Experimental 2.1.453 for 1.7.2 requires a minimum Forge build of #1053. Using #1053 with your pack works fine (well, it starts and lets me create a SSP world of type BOP). There must be something that has changed from Forge #1053 to #1057 which one of the mods is complaining about. Edit: Also, I cannot recommend adding Waila highly enough. It is wonderful to use (imo) and great when debugging things in-game while building/debugging a pack.

The "crash log" is often very good at delivering the Java/class hierarchy related to a particular crash. However, it can fall short when looking for the context in which the crash happened. This is where the ForgeModLoader-client log comes into its own. In this case the FML client log pointed the finger right at BiomesOPlenty: 2014-04-10 07:43:56 [SEVERE] [ForgeModLoader] The following problems were captured during this phase 2014-04-10 07:43:56 [SEVERE] [ForgeModLoader] Caught exception from BiomesOPlenty java.lang.NoClassDefFoundError: thermalexpansion/api/crafting/CraftingHelpers Turns out that you were using a very old version of BOP which was likely compiled against an old ThermalExpansion API. Updating to the latest version of BOP fixes this problem.

@CoreGig: Don't hijack. @MrPikachu: Most of the packs you referenced in that list are actually broken. Try this one: http://www.technicpack.net/modpack/details/barebonespack.271497 That is a super basic pack I maintain so people can test their own packs or start a new one. It only has Forge installed.

So, when attempting to start a world, either new or old on all modpacks, both platform and custom, your client crashes back to the launcher? Sounds like a platform problem and you would be better served posting a bug report with client log in the proper location.

It could also be a conflict of some sort. What modpack are you adding this to? Is this the only mod you have added to that pack? Can you provide a link to your full ForgeModLoader log?

You have a very old version of Forge. Update to the latest 1.6.4 build (965). You have an old/incompatible version of IC2 installed. If you intend to include IC2 I recommend looking here: >industrial craft tekkit 1.6.4 - Tekkit Discussion - Technic Forums You have not included configs for all but one mod. This is "bad" and often fatal for a modpack.

It seems that either through a mistake or intent MCPC+ is not currently retrieving its libraries properly. Supposedly this link has them: http://www.mediafire.com/download/n28pp7r4kt0e1bd/MCPCPlus_Libraries.zip

Where on earth are you getting these JAR files from? MCPC+ comes from here: http://ci.md-5.net/job/MCPC-Plus-164/ and you want build #251 (as of this posting). Also, you don't need a "bin" folder at all in the server. As for the end of stream errors, Mojang seems to be having trouble with their authentication services today.

If you are working from a 1.2.8d or 1.2.8e and have added no other mods, you simply have to drop Tinkers' Construct mod into the mods folder and it works fine.

If you don't include at least the pack URL (what you would paste into the launcher) it is much harder to know for certain where the problem lies. Without being able to examine the download URL it is impossible to know exactly what you might have in your pack (lots of folks put in extraneous/incorrect stuff). Without log files it is impossible to have the slightest clue what the problem might be. Anecdotal statements and vague descriptions are not helpful. Just the facts, ma'am.

How about that. I hadn't notice yet that the current TekkitMain doesn't have the mod that provides the feature which allows you to show which chunks around you are force loaded with the F6 key (default bind). You can still use "/chunkloaders" to see which chunks are loaded. As for F9, it will basically show you exact chunk borders in different ways depending on how you cycle through the views by continuing to click it.

Check using F6 to make sure the chunks that are at all ends of the system are force loaded. After that, check using F9 that your machines/etc. at your quarry are in the chunks which the quarry is force loading.

When it comes to synchronization of config files as long as the client and server have the same IDs for everything the client should be able to connect. If the config options are different the server will take precedence. However, if it is something to do with how energy is used or recipes work and there are differences between client and server the client may see the incorrect data (like how much energy it takes in to make something with IC2 machines, etc.)

You have the incorrect version of ChickenShed. You have the 1.5+ version and you need the 1.6.4+ version. You have the Atomic Science API installed. This is unneeded and should be removed. You have two different versions of Atomic Science installed. You have two different versions of BuildCraft installed. You have two different versions of CodeChickenCore installed. You have two different versions of Dimensional Anchors installed. You have two different versions of Galacticraft installed. You have two different versions of immibis core installed. You have two different versions of Mystcraft installed. You have two different versions of Not Enough Items installed. You have two different versions of Project Red installed. You have the Resonant Induction API installed. This is unneeded and should be removed. You have the Universal Electricity API installed. This is unneeded and should be removed. You have two different versions of Universal Electricity installed. You have a number of mods that are old versions with known bugs and instabilities.

Not to my knowledge, no.