plowmanplow

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

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.

Automatic ID fixing mods do not belong in a finished modpack. They are intended to be used as a tool to help you resolve conflicts, but removed before distribution. Remove idfixminus-1.6.4-1.0.0.jar and manually resolve any remaining conflicts (both block and item).
You have the 1.7.10 version of Enchanting Plus. This won't work.

The Technic Launcher does not like the character "§" in filenames. Rename any files (specifically in the /shaderpacks/ folder) to remove that character.

You have two different versions of Not Enough Items installed. You've got the "new" CoFH mods, but haven't updated many other mods which rely on CoFHCore. Mods which you really need to update (not just because of CoFHCore):
AE2rv2 to beta-8 BigReactors Botania BuildCraft IC2 Nuclear Control Jabba PneumaticCraft RailCraft Tinker's Construct Thaumic Tinkerer (big time) Tinker's Mechworks Twilight Forest

The Launcher doesn't work well with archives containing files with funky names. Rename the files in your /shaderpacks/ folder containing the "§" character.

The "correct" way to install LiteLoader in 1.7.10 is to simply place the liteloader-1.7.10.jar into the /mods/1.7.10/ folder (the mod JAR, not the installer). For Solder, you would just create that folder structure just like any other mod.

java.lang.NoClassDefFoundError: reifnsk/minimap/ReiMinimap REI Minimap is a client-only mod and should not be on your server.

Ahh, yes. If you include the world save in your modpack archive it will most definitely "clobber" the local user's save and anything they have changed. There are a few ways you could distribute the world save in a non-destructive way:
Zip up the "starting" world into an archive in the /saves/ folder. Clients can extract that ZIP to the /saves/ folder the first time they want to start the world and then if you change the ZIP file later it won't overwrite their active save. This would be a close second to the last option if you don't want users to have to download extra files. Instruct users to change the folder name of the world save before they launch the pack for the first time. This is likely to cause issues/frustration for the "less informed" among your user-base. Distribute the world save as an additional download. This would be my first choice.

Yes, the user in question should update to the latest Java 8. This may require installing the Java 8 JDK instead of the JRE.

Your CoFHCore is out of date. Update to the most recent CoFH mods (that you are using): http://teamcofh.com/downloads/ Your IC2 mod is out of date and not from the author: http://ic2api.player.to:8080/job/IC2_experimental/ After fixing these issues I was able to launch your pack and start a SSP world (Java 8).

Did your Java update and switch to a 32bit version? That can happen and cause issues.

Copy.com direct links need to have "?download=1" (without quotes) appended to them to work properly in the platform. The legacyfixer-1.0.jar is only needed for Forge 1.7.10 < #1230. You can and should remove it. iChunUtil is the incorrect JAR file. You shouldn't be using the "deobf" (deobfuscated) version of the mod. As of this post, the site isn't working so I can't get the latest, correct version. Disabling it and Hats allows the pack to start after fixing Calclavia's mods. Have caution when including mods with "(1)" (caused by downloading a duplicate file to the same folder) in the name. Believe it or not, this sometimes causes issues. Why are you including Resonant Engine and Universal electricity? None of the mods you have installed require them. Also, Your Resonant Engine is amazingly old. The current version doesn't require Universal Electricity as a dependency.

You have included too many things in your modpack archive. Your modpack archive should only contain the folders: /bin/, /config/, /Flan/, /mods/. The extra, unneeded folders and files are bloating your pack by over 200M. Forge for 1.7.2 requires the use of Lexmanos' legacy java fixer. See this post: http://technicpack.net/article/attention-modpack-authors.105 Your Custom Music Discs mod is out of date. The current version for 1.7.2/1.7.10 is v1.6. http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1294939-custom-music-discs-v1-6 After correcting these issues I was able to start the pack.

Can you provide a pastebin for the relevant portions of your ForgeModLoader-server-0.log? Also, will the server start on a new world? You can test that by temporarily renaming your world folder and starting the server up.

I've had incompatibility issues when not using the "Latest" version of NEI. The platform doesn't seem to like this file and is failing during the extraction process (likely due to the non-standard characters): /mods/moarperipherals/lua/songs/Comptine D'un Autre Été.nbs Renaming the file to remove the special characters allow the pack to install properly.

Whatever program you are using to create those archive files needs to be configured to use ZIP format instead of RAR format. How? Depends on the program. Google is your friend.

The FML log (the latest.log in /logs/) probably has more specific information, but finding the versions of Calclavia's mods which work together can sometimes (often?) be an exercise in frustration because he does not ensure that the "current" version of his mods work with each other. You will need to follow up with him, or his support locations, to find out the correct versions to use.

So, the problem you are having is because Calclavia can't be bothered to make sure his mods work with each other. The current version of MFFS doesn't work with the current version of its dependency mod ResonantEngine. Neither do the the one-revision-back versions. You'll either need to remove those mods or contact the author to get a recommendation for which versions actually work together.

Since you are making a Forge/MC 1.6.4 modpack you need to include Lexmanos' legacy java fixer: http://t.co/9olGYnwZBi You should not include TConstruct_Library in your pack. That is only for developers. Your OptiFine is quite out of date and should be updated. You have not included any config files in your modpack archive. This is always bad and, for Forge/MC 1.6.4 packs, often fatal.

Indeed, it does. The list from your OP is a VERY long list of plugins. Time to start adding them one at a time until it stops working.

Something is "wrong" with your modpack archive ZIP file. What program are you using to create it? I simply extracted your archive and recreated it using WinZip, then copied over the file downloaded by the Launcher and the pack worked fine. This is the error being generated with your version of the modpack archive:
[B#245] 2015/01/23 07:37:29 [SEVERE] java.io.FileNotFoundException: C:UsersjuniorAppDataRoaming.technicmodpacksantagonistmods (Access is denied) [B#245] 2015/01/23 07:37:29 [SEVERE] at java.io.FileOutputStream.open(Native Method) [B#245] 2015/01/23 07:37:29 [SEVERE] at java.io.FileOutputStream.<init>(Unknown Source) [B#245] 2015/01/23 07:37:29 [SEVERE] at java.io.FileOutputStream.<init>(Unknown Source) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.utilslib.ZipUtils.unzipEntry(ZipUtils.java:95) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.utilslib.ZipUtils.unzipFile(ZipUtils.java:145) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.launchercore.install.tasks.UnzipFileTask.runTask(UnzipFileTask.java:58) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.launchercore.install.tasks.TaskGroup.runTask(TaskGroup.java:64) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.launchercore.install.InstallTasksQueue.runAllTasks(InstallTasksQueue.java:52) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.launchercore.install.ModpackInstaller.installPack(ModpackInstaller.java:41) [B#245] 2015/01/23 07:37:29 [SEVERE] at net.technicpack.launcher.launch.Installer$1.run(Installer.java:112) [B#245] 2015/01/23 07:37:29 [SEVERE] at java.lang.Thread.run(Unknown Source) The "access denied" error indicates something fundamentally wrong with the archive file.

You need to add Lexmano's Legacy Java Fixer to your /mods/ folder.

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

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