plowmanplow

​No, using OP's pack, one can construct a nether portal in the overworld and successfully enter the nether. One just gets dumped back into the nether when trying to use a nether portal in the nether after traveling there originally from the overworld.

Not exactly. Every "mod" archive gets downloaded to the modpack's cache directory. Inside that you will find the ZIP files for every mod you add to your pack from within Solder. The general rule of thumb is: Only put one mod in each Solder "mod" archive. Exceptions for things like Galacticraft or ProjectRed Base and MrTJPCore which will always be together and matching makes sense. Do not include config files with your mods in their archive files. Put all the configs in their own Solder "mod". Include both the mod version number and the MC version number in the name of the Solder "mod" archive.

You need to change the end of the download URL from "?dl=0" to "?dl=1". Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. You have Forge #1399 but have included mods which won't work correctly past Forge #1354. Examples: AE2, CodeChickenCore, Extra Utilities, IC2, Tinker's Construct.

Your /bin/modpack.jar is named "modpack.jar.jar". Google "windows explorer always show file extensions" to learn how to fix this and prevent it in the future. You have a very recent version of Forge (#1401) but old mod versions which require Forge < #1355. Biomes O' Plenty, Blood Magic, etc. Many of your mods are in the format "ModName-Mod-1.7.10.jar". This almost always indicates that the mod has been downloaded from an illegitimate source. Get your mods directly from the authors. Many other of your mods are missing the version numbers in the name. If you are removing the version number you need to re-download the mods and leave the file names intact. If you are downloading mods with no version number in the name, 9+ times out of 10 you didn't get it from the author.

Many folks use Sphax: http://bdcraft.net/

That is a link to the pack download. We can start with that but will be unable to properly diagnose problems without the API URL or pack details page.

As is often the case, that is a click-bait website which is providing download links for things which are not what they say they are. The texture pack available there is for MC <= 1.5.2.

The symbol means nothing. That is just an indication of which program will be used to open that type of file. As long as you configure 7zip to create a ".zip" file in ZIP format you should be fine.

It looks like you have ZIP archive files associated with the WinRar application. This is fine. Notice that the file extension is ".zip".

​I think you are missing something fundamental here. YOU change the version number when YOU change the modpack archive or link in any way.

You could also try adding the Extended Potions mod which increases the max potion count to 4096 (by default). Rename the mod to be "zExtendedPotions-MC1.7.10-1.1.jar" (or whatever version is available). Might help, might not. Worth a shot.

There are very few options for textures available for mods. You will need to assemble it yourself from the base texture pack (vanilla MC) and any mod textures you can find. Sphax ( http://bdcraft.net/ ) has a lot, but is by no means exhaustive.

Excellent! If by the "server file" you mean an archive of all of the files and folders to create a server, then yes, you do. You can provide a link to that archive file in your pack settings.

Create a new thread. Your issue is quite clearly something completely different (just from a cursory glance at the crash reports).

Nobody cares if your pack is public or private. If you want custom modpack assistance you must provide the API URL or a link to the pack details page. Without that we would be guessing on many aspects of the modpack and it's not worth our time to do that. If you want a modpack in the platform, you have to create a custom modpack in the correct format. This post may help you: http://forums.technicpack.net/topic/103596-still-looking-for-help-building-custom-modpack/#comment-571785

Transferring the modpack to me won't really help either of us. The pack version (from your settings page) is still 1.0 yet I know you have changed the modpack archive. Every time you change your modpack archive in any way you MUST update/change/increment the pack version number in order for the platform to recognize there is an update available. Your download archive is in 7zip (.7z) format. This will not work. As previously mentioned, use 7zip to create a ZIP format archive. As for the actual contents of your pack, I'm not going to do any more debugging/diagnosis than I already have. Make sure you fix the modpack.jar/Forge issue I mentioned above. Other than that the pack is just too large for me to work with. One does not start off by trying to make a modpack that reports 300 mods. Start small and work your way up.

This post does belong in Platform Pagoda. Hopefully a kind admin will move it. That being said, this is one of the best formatted custom modpack assistance posts I've seen. A video showing exactly what's going on, a link to your pack, a text explanaiton with supporting evidence. Unfortunately, I haven't found any references to this problem. It sounds vaguely familiar, but I just don't remember where I saw it before. That being said, the mods in your pack are mostly very old. The likely culprit is some odd incompatibility between mods which updating could likely resolve.

What specific modpack. What specific version of Forge on the server.

What modpack is this for? What server are you using? (Cauldron/Forge and what version) Does it kick you, or does the client crash?

Your pack version number (which probably shouldn't be "Click For Info") hasn't changed. Your download archive is no longer available so I can't test anything.

Please provide the API URL or a link to the pack details page for your modpack.

Please provide the API URL or a link to the pack details page.

You would DOWNLOAD the FORGE UNIVERSAL BINARY JAR and RENAME IT TO modpack.jar. I don't know how to be more clear than that. I would recommend a specific version of Forge and provide a link, but you have mods which require different versions of Forge so I can't do that. (which will end up being a major issue for you, but nobody is going to help you resolve conflicts/versions for 200 mods at once)

This should get you started: http://forums.technicpack.net/topic/61989-server-of-fury-i-would-like-more-help/#comment-519381

I don't know about other programs, but I know that 7zip will allow you to specify the archive format when creating an archive. As I mentioned before, "The modpack.jar file is simply the correct version of the Forge universal binary JAR file renamed to modpack.jar." You don't "put anything" into the modpack.jar. You just download the Forge universal binary JAR file and rename it. That's it.