plowmanplow

You might consider updating Forge to the latest 1.7.10 version. NEI should probably be updated to the latest version. Make sure you are incrementing the pack version number every time you change your modpack archive.

yes, provided you copy the folder I listed (and its contents) you should be golden.

bspkrsCore belongs in /mods/1.7.10/ You have AM2 for an older version of Forge/MC. 1.4.0.008 is the current 1.7.10 version. You should be using the latest version of the AE2rv2 Beta. You only have one of the three mods that make up Galacticraft. You need GalacticraftCore, GalacticraftPlanets and MicdoodleCore. You should remove any "(1)" strings from your file names (or parenthesis with any other numerical digits in them). They can cause issues with some mods. You have the LiteLoader installer in your /mods/ folder. The actual LiteLoader mod JAR (not the installer) belongs in the /mods/1.7.10/ folder. Your TeamCoFH mods don't match. Get the latest version of all your chosen TeamCoFH mods from their website. Your Not Enough Items mod is from an illegitimate source. Get the latest version from the author's website. This applies to any of your mods named in the format of "ModName-Mod-1.7.10.jar". You have the Thaumic Exploration for 1.7.2 instead of the required 1.7.10 version. Your Thaumic Tinkerer mod is ancient and not compatible with the current version of Thaumcraft. It should be updated. You have a 1.7.2 version of Twilight Forest. You need the latest 1.7.10 version. This is all simply from browsing the contents of the modpack archive. I made no attempt to start the pack since there are so many fatal issues. Address these and come back here if you have more difficulties.

You can copy the contents of the %APPDATA%\.technic\modpacks\ folder to your new PC in the same location and everything should be retained.

This thread belongs in Platform Pagoda. Hopefully a nice admin will move it. Always provide the API URL or a link to the pack details page. Searching for your pack and hoping we find the right version is quite inconvenient. Your API URL: http://api.technicpack.net/modpack/caloxeno-s-magic Your pack isn't working because you have zipped the entire .minecraft folder instead of the correct structure. It doesn't even look like you are using the Technic launcher to test your pack. I would recommend reading through this post for details on how to assemble the pack: http://forums.technicpack.net/topic/62318-minecraft-keeps-crashing/#comment-506458

This is your current download link: https://copy.com/rzY9QFuc36NaV0te?download=1 That link doesn't work because copy.com claims it doesn't exist. Try recreating the public share URL for that file.

Yes. We'll need the API URL or a link to the pack details page. Check your server console. It may (should) provide more information about which mods are being rejected for the client. Generally speaking, Forge doesn't really ever get that wrong so if it's complaining about them being mismatched, they are probably mismatched. There's no need to PM me with a duplicate of a forum post. I respond here as soon as I am able.

The pack seems well constructed and appears to work fine. We would need one of the crash reports from a client that is crashing on world creation in order to proceed.

Forge for MC >= 1.6 does not use a coremods folder in any way. All mods belong in or below the /mods/ folder.

Requests with details and relevant supporting documentation get quicker/more responses. Requests with no more info than "my stuff don't work" leave us no more recourse than to ask for more information (which most people simply ignore). Which modpack are you referring to? Provide the API URL or a link to the pack details page. What URL are you attempting to use in the modpack location field? Has it never worked, or has the behavior changed? Have you recently switched hosting providers for the modpack archive? Are you properly incrementing/changing the pack version number? Does your pack work properly in your local test environment? What kind of error messages are you receiving? Do the errors happen in the platform interface, or in the Launcher? See? There is so much information you could have provided but chose not to.

You have provided no useful information which would allow us to help you. Please be specific about what isn't working (provide logs in a pastebin service when possible). Always provide the API URL or pack details page for custom modpack assistance.

Since you have updated neither your modpack archive nor the pack version number I can only speculate, but it looks like a problem with ChickenChunks or ChickenBones mods in general. On a side note, you really shouldn't be allocating 13G to the Launcher. Allocating more than a pack needs is usually counterproductive for performance and should never be more than 4G or half your physical RAM, whichever is smaller (and 3G is enough for even large packs unless you are using texture packs).

​Please do not attempt to dilute this issue by misinterpreting what I was saying to the OP. Yes, many (most?) authors provide the MC version in the file name. However, they also provide specific mod versions and/or build versions in the file name as well. Also, each author has a slightly different naming convention they adhere to. For instance. The OP had this mod: Hats-Mod-1.7.10.jar However, the author names that mod like so: Hats-4.0.1.jar The point I was trying to make is that almost no mod authors use the specific format of "ModName-Mod-1.7.10.jar". 99%+ of the time a mod with that naming convention has been obtained from somewhere other than the distribution channel the mod author has provided. This makes it "illegitimate". The result is that the user has no assurance that: A) They are using the correct/newest version of the mod, and B ) That the mod file has not been altered in some negative way. Here are a couple resources about getting mods: Getting Mods: Stop Mod Reposts: http://stopmodreposts.org/

Clearly an issue with ZapApples. Something to do with how it is managing time of day. The mod is in Alpha status so not completely a surprise that it isn't stable. You will need to remove the mod until the issue is fixed.

Some of the older packs are no longer included by default. Just search for them by name in the Launcher and they can be installed.

Your pack settings indicate that the MC version is 1.8.1. Forge is only for MC 1.8 and requires that you have 1.8 selected in your pack settings.

Yes, I saw all that. I didn't try adding BuildCraft fake player to the GP config because I don't feel that is a viable solution.

Hmm... I thought I explained that: PEBKAC = Problem Exists Between Keyboard And Chair Now, what takes up the space between the keyboard and chair? Yep, you guessed it. The user.

You added "industrialcraft-2-2.2.695-experimental.jar" when you should have (as I mentioned) added the API file "industrialcraft-2-2.2.-experimental-api.jar".

Client Pack: The Forge universal JAR does not belong in the /mods/1.7.10/ folder and should be removed. Your AM2, LoTR, NEI, ProjectRed, ThaumicTinkerer, Tinker's Mechworks are quite out of date. Many of your mods are from illegitimate sources. Any mod with the filename name in the format of "ModName-Mod-1.7.10.jar" is highly suspect as almost no mod authors name their mods in that fashion. You need to update/replace every mod with that format of name. I'm stopping there until you get your client pack fixed.

Beefchicken: different pack = different problem. Please start a new thread.

Your download location URL is missing the "http://" from the front. As for not updating your mods. We will be unable to help you unless you update. There are multiple ways to resolve your issues, but not updating surely isn't one of them.

The fake player for MFR would be [CoFH], but MFR works fine out of the box. The problem your users were having is what we call a PEBKAC error (Problem Exists Between Keyboard And Chair). As for BC, yes, I just "/trust [buildCraft]". [buildCraft] is not opped.

Shall we guess what the problem could be? Always provide the API URL or a link to the pack details page when requesting custom modpack assistance.

You are correct.