plowmanplow

And when you respond to Manaus, if you include the API URL or a link to your pack details page someone will actually assist you.

A couple observations: Above, you have a link like so: http://markofthephoenix.playat.ch/CliendMods/mods/modpacl/modpack-11.zip Notice that it says "modpacl/modpack-11.zip". Is that just a typo, or is the folder name actually "modpacl" and the zip file named "modpack-11.zip". I ask because the folder name should be exactly the same as the mod slug, and the filename should be named "slug-versionnumber.zip". Anything other than that will screw up Solder being able to identify things. Also, I am unable to actually link to that file. The ZIP files should be able to be hit with a direct URL. Are you able to get to the files through the browser by typing in a direct URL? If so, what do you have to type in. If not, you have either a web server or Solder configuration issue.

It would be helpful to see the actual crash-report instead of the full FML log. From what I can see in the log you provided it seems as though something is crashing related to that client and the "Mojang" splash screen. You might try creating a build without BetterTitleScreen for that client and see if it fixes things. On a side note, the pool of folks doing support is pretty shallow. The majority of requests here are addressed by one person who isn't always at his PC. If you need more immediate assistance you might try out the #technic IRC channel on SynIRC.

The correct way to make dropbox links direct is: If you have this: https://www.dropbox.com/s/cu1dlul3g9vkih8/ModPack.zip?dl=0 Make it look like this: https://dl.dropbox.com/s/cu1dlul3g9vkih8/ModPack.zip

Dynamic Lights is a client only mod and must be removed on a server. Some of your mods are from illegitimate sources (i.e. not from the authors). You are using IDFix. This is always "bad". You should "fix" your conflicts and remove IDFix from the server and client: http://forums.technicpack.net/topic/64178-hexxit-modification/#comment-519633

As I mentioned before, that crash data isn't very useful. Your crash-report and ForgeModLoader-client-0.log files are what we need. Put them into a pastebin or download service. Don't paste them here or attach them to your post (attachments don't work). Which specific version of AM2 are you using? What exact things have you added to BTeam?

So, the full folder path to one of your mods is: /home/Solder/CliendMods/modpack/modpack-11.zip ?

Always provide the API URL or the link to the pack details page when requesting custom modpack assistance. We will be unable to proceed until that is provided.

What URL is required to hit the ZIP files for your mods? I see "ClientMods" in that URL, but are they actually in a folder by that name? What is the full directory path to the Solder public folder? What is the full directory path to the mods folder? What are the settings for paths/URLs in your solder.php config file?

Just so others see this: Set "cleanuptime" in ChickenChunks.cfg to zero when using Cauldron.

Both copy.com and dropbox work fine. (with the appropriate URL changes) copy.com: add "?download=1" to any public share URL dropbox: replace "www" in the URL with "dl" and remove the trailing "?" including everything after it.

Your modpack download URLs are missing the "http://" at the beginning. Double check your solder settings files. Your settings and the actual folder path where the mods exist seem to be different. Again, this is a settings issue.

Once you alter one of Technic's modpacks you have a custom modpack and the tread would belong in Platform Pagoda. Hopefully a kind admin will move this thread. You have cut off the useful portions of the crash. We will need links (don't paste the contents here) to your most recent crash report and your most recent ForgeModLoader-client-0.log file.

<shakes magic 8-ball> Mmmm, I suspect it is caused by your maternal grandmother being left handed. All snarkyness aside, we'll need more information in order to assist you. Please provide detailed information about the errors or messages you are receiving. Always provide the API URL or a link to your pack details page on the platform when requesting custom modpack assistance.

So, the slug on the platform (Technic's site) must exactly match the slug in your personal Solder installation in order to link the pack. Technic's slug is "testing-server". What is the slug in your Solder installation? You can test/set this in the pack's settings page in your Solder. I ask this because that slug does not seem to be available in your Solder setup. For example. I have a modpack named JCLite with a slug of "jclite". The link for that pack into my Solder setup looks like this: http://solder.circlecraft.info/api/modpack/jclite

Calling yourself "not smart" and asking for "smart" people to help is specious and unhelpful. Please always use a pastebin service to provide log data instead of putting it directly into the thread here. Always provide the API URL or the a link to your pack details page when requesting custom modpack assistance. It looks like you are attempting to start a server with REI's Minimap in the /mods/ folder. REI's Minimap is a client only mod and must not be on the server. There could potentially be more issues, but without a full crash report (in a pastebin) and a link to your client pack we are unable to offer more assistance.

Your modpack download is not a valid archive file. The ZIP header looks broken. What program are you using to create the ZIP archive? Try recreating it. Make sure you are incrementing the pack version number any time you change your modpack download.

Are you using Forge or Cauldron as your server?

What is your Solder API URL? What is the slug of the modpack you are testing with?

If you simply want to change the location where players spawn (world spawn) you can edit the map's level.dat file with NBTExplorer and change SpawnX, SpawnY and SpawnZ to whatever you want. This must be done with the server stopped.

Congratulations on a well formed support request, especially for your first post. Hats off. You are using an absolutely ancient version of Forge along with many of your mods being very old with known critical issues. An update would not be a bad idea. You have a version of qCraft which is incompatible with 1.7.10. Any attempt to use its blocks will hard-crash the world requiring an MCEdit to fix. There is a port up to 1.7.10 here: https://github.com/OpenCraft/qCraft/releases All that being said, I am able to add your pack to the Launcher and start an SSP world successfully. We would need a clean Launcher log file (close Launcher, remove all launcher logs, restart launcher) of you trying to add the pack in order to provide more assistance.

If you actually run the installer JAR, you get an "extract" option.

Hmm, a few problems here: Never "necropost" unless absolutely necessary (i.e. never). You almost surely do not have the same issue. Start your own thread and provide the required information: API URL link or a link to your pack details page, a clear and concise description of the problem

Your 1.5.2 modpack requires Java <= 1.7. This is a hard requirement with no alternative options.

Sounds like you are starting the minecraft_server JAR file instead of the Forge server JAR. You should have a batch file to start the server that looks similar to the one in this post: http://forums.technicpack.net/topic/61989-server-of-fury-i-would-like-more-help/#comment-519381