plowmanplow

(When correctly installed) The modpack.jar is the Forge universal binary JAR file renamed to modpack.jar. Download the Forge universal binary for your version and rename it to modpack.jar.

Always provide the API URL or pack details page when requesting custom modpack assistance. This is your details page (for my reference): http://www.technicpack.net/modpack/craftified.616564 BattleTowers mod is not installed correctly. Open the ZIP archive and follow the author's instructions. You have Waila but not NEI on which it depends.

If you are running out of Permanent Generation space (PermSize) you might want to update to Java 8. Probably should anyway, and that will eliminate the need altogether. Once you update you can remove the PermSize and MaxPermSize parameters from your launch script. I'll set up a local test server with your pack to make sure things are working as expected. I'll get back with you.

If it says you have CustomLanPorts, then you probably do, even if you are missing it. You will need to make a server ZIP for us to continue. Zip up your /config/, /coremods/, /mods/ folders and provide a download link.

Ah. That is the server's FML log? Can we assume that your client is now working fine? Client You have the bspkrsCore mod in both the /mods/ and /mods/1.7.10/ folders. Remove the copy in /mods/ Client Only Mods: (must be removed on the server) Armor Status HUD JourneyMap (or get the server version) MobAmputation MobDismemberment NearbyMobFinder OptiFine Waila Harvestability Waila Plugins

You have provided no real information. Please provide: The API URL or pack details page for your custom modpack. The console output in a pastebin service (like http://pastebin.com ), not pasted into the thread here.

BackTools is a client only mod.

Please provide the FML log associated with that crash report.

This thread belongs in the Platform Pagoda forum. Hopefully a kind admin will move it. Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. In your case, it is this: http://api.technicpack.net/modpack/yaopack Why did you start a new thread for the same modpack? Your Flan's mod packs are in a subfolder. The Flan pack archives should be directly in the /Flan/ folder, not in /Flan/Flan/. Your modpack settings are configured to use MC 1.7.9. This must be changed to 1.7.10 in order to function properly.

Forge for MC 1.7.10 works fine with Java 8 when used with builds >= #1230. The legacy java fixer should not be included in 1.7.10 modpacks.

The file "fml-1.7.10-7.10.84.997-universal.jar" is not required and should be removed from your /bin/ folder. The legacyjavafixer is not required and should be removed. Many of your mods seem to be from illegitimate sources. Almost no mod authors name their mods in the format of "Mod-Name-1.7.10.jar". Any mods with names in that format should be updated with the latest/correct/matching versions directly from the mod authors. You have at least one file with "(1)" in the file name. This is an indication that a duplicate file was downloaded to the same folder. The file name should be fixed to remove this addition. NEI and Thaumcraft are out of date and should be updated. Address these issues and come back if you are still having performance issues.

CoFHLib is intended for use only by mod developers and should not be in your pack or server. There is some conflict between MineFactoryReloaded (or CoFHCore) and Thaumcraft. Since I know that your version of Thaum and MFR work fine together there must be one of the other mods which extend Thaumcraft causing problems. You will need to methodically add mods starting with a blank/empty pack in order to isolate the offending mod.

Your /bin/modpack.jar file is incorrect. The modpack.jar file is the Forge universal binary JAR file renamed to modpack.jar. You have a number of mods with (1), (2), etc. in the file names. This is caused by downloading a file with an existing name to a folder. All the file names need to be fixed by removing the extra space, parenthesis and numbers. Failing to do so can cause issues with mods. You should update to the latest AE2rv2. You have an "installer" for the MC Heli mod in your /mods/ folder. The mod is not distributed this way implying that you obtained that from an illegitimate source. You have duplicate mods in your /mods/ folder: Resonant Engine, Thermal Expansion You have no mods which require Resonant Engine and all 4 of those files should be removed.

Kind of hard to test something I can't see. Make sure you update the pack version number when you change the modpack archive.

If you examine the filenames of your mods you will notice that some of them contain a single digit number enclosed by parenthesis (i.e. (1)). This is bad and should be eliminated.

AE2rv2 is Applied Energistics 2 revision 2. The latest versions can be found here: http://ae2.ae-mod.info/Downloads/ Any mod which has a name in the format of "Mod-Name-1.7.10.jar" is most likely from an illegitimate source. Almost no mod authors use that naming convention. You should know the correct location where the mod author of every mod in your pack provides legitimate downloads before including them.

It is generally considered bad form to include a resource pack in the modpack archive. It needlessly bloats the pack size, many folks cannot use them, and including the options.txt file overwrites client settings.

You should never need to allocate more than 3G to the Launcher in all but the most rare/insane circumstances. Allocating more RAM is usually detrimental to overall performance. OreSpawn is conflicting with another mod causing that crash. They are aware of the issue and seem to have no interest in tracking down the cause to resolve the issue. Removing OreSpawn (or the other unknown mod with which it is conflicting) is your only recourse.

Your modpack.jar file is incorrect. You have used the Forge installer JAR. The modpack.jar is the Forge universal binary JAR file renamed to modpack.jar. You should be using AE2rv2 beta (latest). Many of your mods are from illegitimate sources. This post may help: Your Mekanism version is ancient and incompatible with other mods in the pack. It needs to be updated to the most recent build.

MFR: PEBKAC error. As for the rest, the server wasn't staying up long enough for me to test anything. Once you have it stable, I might be able to take another look later this evening.

This thread belongs in Platform Pagoda. Hopefully a kind admin will move it. Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. This is your API URL: http://api.technicpack.net/modpack/k-craftplus The contents of your modpack archive is simply a JAR file. The archive needs to be created as a ZIP file with the top level folder containing the bin, config and mods folders. Your /bin/ folder is named "Bin". It must be in all lower case. Remove the "(?)" (where ? is any integer digit) from the mod filenames. This often causes issues. Many of your mods are from illegitimate sources. This is indicated by mods with names in the format of "Mod-Name-1.7.10.jar". Almost no authors name their mods in that format. This post on getting mods may help you: forums.technicpack.net/topic/62513-new-to-technic-what-now/?do=findComment&comment=508175 Your ThaumCraft mod is extremely out of date. You have the BiblioWoods mod for Biomes O' Plenty, but not the required parent mod BiblioCraft: http://www.bibliocraftmod.com/ Address these issues and come back here if you are still having problems.

You are getting the (?) because you are downloading files which have the same name as existing files to the same folder. Either download them to a new/empty folder or remove the existing files before downloading new ones. Some mods will not work if they have filenames with the (?) numbers in them. This is likely the source of your issue with Galacticraft as well. Remove all your Micdoodle/GC mods and re-download them.

@Noobsloth: Please provide links directly to the mod, not to a third party forum: http://files.minecraftforge.net/LegacyJavaFixer/legacyjavafixer-1.0.jar

This likely belongs in Platform Pagoda. Hopefully a kind admin will move it. Always provide the API URL or a link to your pack details page when requesting custom modpack assistance.