plowmanplow

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

The current versions of Calclavia's mods do not work together. This is a common problem with his mods. You will need to follow up with the mod author, possibly in their IRC channel, in order to find which versions of the mods should be used together.

Something is gravely wrong: Minecraft Version: 1.4.7 CoFHCore [CoFH Core] (CoFHCore-[1.7.10]3.0.0B6-32.jar) Unloaded All your mods are for 1.7.10, and it looks like your pack settings are for MC 1.7.10, and the version of Forge in your pack (/bin/modpack.jar) is for 1.7.10. However, the crash report states it is launching Forge for 1.4.7. You must have the wrong version of Forge which you are using to start your server.

Your /bin/modpack.jar file is actually named "modpack.jar.jar". This is likely not obvious to you because you aren't always displaying file extensions. Google for "windows explorer always show file extensions".

@ChatFawkes: Unfortunately, that's still an issue with 1.7.10. Too many mod authors are still indexing things based on IGN instead of UUID. (Thaumcraft, Blood Magic, Baubles, etc.), although not nearly as much as an issue as it would be in <= 1.6.4.

Please provide the API URL (the link you paste into the Launcher).

I was able to add your 1.7.10 pack to my Launcher and successfully start. I assume you have fixed your issues?

I know this may sound like I'm trolling, but my recommendation would be to start with 1.7.10, not 1.6.4. So many of the 1.6.4 mods aren't being updated anymore.

For Forge/MC <= 1.6.4: Modify the version.json file inside the modpack.jar to include the correct references to download LiteLoader at run time. My BareBonesPack includes a 1.6.4 version with this already completed ( 1.6.4 LL): http://www.technicpack.net/modpack/barebonespack.271497 For Forge/MC >= 1.7.2: The LiteLoader JAR file (the mod, not the installer) is simply placed into the /mods/1.7.2 or /mods/1.7.10 folder. That's it.

Indeed. There is a world of difference between textures for Vanilla, and textures for modded MC. The Sphax pack for 1.7.10 has just over 800 texture files (not including CTM). The resource pack for one of my 1.7.10 packs has over 18000 texture files and is noticeably incomplete. There is still plenty of variety in the base textures from the mods (except for IC2... <shudder>), but with the sheer number of texture files you can start to see why fully developed texture sets for mods are not common.

Even typing the URL in manually yields a "download has moved or deleted" message from Dropbox.

That is a crash report from some other modpack which is for Forge/MC 1.7.10, not your 1.6.4 modpack you posted the link to in your original post. Additionally, you still haven't updated the modpack archive download or the version number.

I would definitely second this assessment. The challenge with very low resolution texture packs is that there just isn't enough pixel data available to provide the detail. Resizing just a 64x texture set down to 16x entails disposing of 94% of the data. Higher resolution texture packs typically pursue a theme (as in Sphax) or some artistic direction (as in Soartex). This is possible because there is a much larger canvas on which to express the details required to convey the theme or direction. Without that larger canvas everything just starts to run together, and that's if the textures are crafted specifically for 16x. Resizing from higher resolutions to 16x is so lossy that whatever impression the larger textures were attempting to convey is completely lost. For example: Take a look at this album: http://imgur.com/a/PTcw4 . These images are: Sphax 512x texture for Thermal Expansion Igneous Extruder Sphax 64x texture for Thermal Expansion Igneous Extruder Sphax 16x texture for Thermal Expansion Igneous Extruder Original texture from the mod's internal assets Notice that at 16x the Sphax theme (pentagons) is lost completely and that the texture does not look clean at all. Obviously it tends to be an "eye of the beholder" thing, but I feel that the default textures look better than the 16x Sphax version.

Yes, I'm quite sure: You have many "installers" for mods instead of the actual mod files. Nearly no authors distribute their mods that way. They are just JAR files you drop into the /mods/ folder. If you are seeing installers you are getting the mods from some shady, likely risky, content-stealing website. The mods which are JAR files are named with just "1.7.10" in the file name instead of the mod version number and named as the original mod author named them. Same issue as the first bullet point. The mods which are named correctly are ancient (i.e. buildcraft-5.0.7.jar when the current version is 6.3.4, and ProjectRed).

%appdata%.technicmodpacksssm-164crash-reports

Forge for 1.8 does not include the libraries required to operate in the Launcher inside its version.json file. Those need to be added before it will work in a Technic custom modpack. You can either read up on the details and do it yourself: Or you can use my BareBonesPack ( http://technicpack.net/modpack/barebonespack.271497 ) which has the Forge 1.8 versions pre-configured to work in the Launcher.

This belongs in Platform Pagoda. Hopefully an admin will move it. Read this post on getting mods: Pretty much all your mods are "bad". They all need replaced with the actual mods from the mod author's preferred distribution channels.

The Tracker for the Launcher is the best place for questions like this: http://forums.technicpack.net/tracker/project-1-technic-launcher/

Dude. This is the fourth thread you started for the exact same issue. Two of those were after I told you what you would need to provide in order for us to help you. Are you just trolling?

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.

Please provide the API URL or modpack page link.

You haven't updated your modpack download or the pack version number. Assuming the only thing you changed was to add the legacy java fixer, I am unable to reproduce your issue. The pack works fine for me in SSP. Please provide your most recent crash report in a pastebin (such as http://pastebin.com )

Please don't post in multiple places for the same issue. As I mentioned in your other post, you'll need to provide crash reports and any relevant logs (in a pastebin service like http://pastebin.com) .

The Tracker for the Launcher is the appropriate place for these kinds of issues: http://forums.technicpack.net/tracker/project-1-technic-launcher/

Problems with Technic provided modpacks belong in the appropriate tracker. The link is available at the top of this page.