plowmanplow

Such things may not be discussed/shared on these forums. Google is your friend.

Shall we guess or use a ouija board? Please provide the link to your modpack page so that we may properly assist you.

As to why here system is crashing where others aren't, it could be related to a variety of differences between systems. Amount of system RAM, RAM allocation in the Launcher, Java version, OS issues, etc. The crash report is the only way to start narrowing this down.

You changed your modpack archive but did not increment your pack version in the settings page. The Launcher does not get notified of an update to the pack unless that version number changes. Your modpack.jar file is still completely messed up. I don't know how to be more specific than restate what I previously explained. Download the Forge universal binary JAR and rename it. DO NOT MESS WITH IT IN ANY WAY OTHER THAN TO SIMPLY RENAME IT.

That is where you put the URL to the direct file download for your modpack archive.

There are things like IDFixMinus which helps to resolve conflicts and is intended to be used and then removed. However, none of the solutions are perfect. There is no substitite for searching through the ForgeModLoader-client-0.log file for CONFLICT and resolving things. It's not that hard and only takes a few minutes.

Just make sure you are using 7Zip to create a ZIP format archive instead of a 7Zip (7z) format archive. Google for this if you can't figure out how to do it through their interface. The modpack.jar issue is clearly explained in my previous post. Step 1) Download the Forge universal binary JAR. Step 2) Rename it to modpack.jar.

Your PermSize options are messed up: -XX:PermSize=3096m -XX:MaxPermSize=4000m You should not be allocating 3-4G of RAM to permanent generation space. Your Better Dungeons mod is not installed correctly. Open the ZIP file and follow the instructions. The Warp Mod is not installed correctly. The ZIP file just contains a JAR file. I think the Moden Weapons Pack has a conflict of some sort with either another mod, or SMP in general. It is throwning an error related to data persistence when placing vehicles from that pack. I removed that pack and added FC Pack addon and was able to place vehicles from that. Might need to take the issue up with the Flan's group.

The download URL is configured correctly with the proper suffix attached to the URL to make it a direct link. Your modpack archive is in 7Zip (7z) format. All archive files intended for use in the platform must be in ZIP format only. Your /bin/modpack.jar is named "Modpack_.jar", is in the wrong archive format (see bullet #2), and does not have the correct contents. The modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. Don't mess with it in any other way that to just rename it. You should not include the /mods/VoxelMods/ folder in your modpack archive. This will overwrite local client settings when the pack updates. Steve's Addons mod requires Steve's Factory Manager mod. The VoxelMenu LiteLoader mod is crashing. You might need to remove that or do more research.

@BCTLFTW: Are you referring to the API URL? This is the URL which uniquely identifies the modpack for the Launcher and allows you to add the pack to your Launcher. Or, are you referring to to modpack archive URL which goes into your pack settings? This is the URL to the actual modpack ZIP file.

If there is any way to get a crash report from her client you should be able to narrow down what's causing the problem. Without that it is almost impossible to guess.

@TheCowCrafter: The "dl=0" you refer to sounds similar to what one must add to DropBox links, "?dl=1". However, without the link in question we can only guess. Please provide a link to your Technic pack page so that we may properly diagnose the issue.

Your modpack archive should not include the /bin/minecraft.jar file. This is not needed and is a violation of Mojang's EULA. You should not include the /mods/VoxelMods/ folder in your modpack archive. This will overwrite client's local settings when the pack updates. It is seldom a good idea to change the names of the mod files distributed by authors. Your CodeChickenCore mod has an extra "(3)" in the file name. That error log shows errors when attempting to extract/open all your TeamCoFH mods. Please re-download all their mods. Make sure you are incrementing the pack version number any time you change your modpack archive.

Without logs, all we can do is guess. Please provide a ForgeModLoader-server-0.log from a fresh restart with the plugin in place. Do this in a pastebin or file service, don't paste it here.

Not trying to be obvious, but your don't have TekkitCustomizer listed. Check your logs to make sure that the TekkitCustomizer plugin is loading, and that it is finding its config file.

Solder and/or your web server is not properly configured. The links for downloading the mods don't work: Your link: http://yu-shan.net:8080/index.php/mod/view/ftp.yu-shan.net/minecraft/mods/minecraft-forge/minecraft-forge-10.13.2.1277.zip This should be a direct link to your mod files. For instance, here's one of mine: http://solder.circlecraft.info/mods/extra-cells/extra-cells-1.7.10-2.2.25b45.zip Make sure the settings in your config/solder.php file are correct, and that your mods folder is directly exposed in your web server config.

Something is messed up with the way you are assembling the pack. I extracted your modpack archive, and just re-zipped it and it worked fine after that.

You should probably be using AE2rv2 instead of AE2rv1. Nearly all your mods are named simply <modname>-1.7.10. Almost no mod authors provide their mods with names without version numbers. The implication is that you aren't getting the mods from their respective mod authors. This is always bad. Your versions of OpenBlocks and OpenModsLib do not match (see previous bullet point). Update the latest matching versions. Gravity Science mod requires Grim3212 Core mod. Get both from the author's website. You have an ancient version of MFFS and are missing the required dependency library Resonant Engine. You have (and amazingly ancient version of) Tinker's Construct mod but not the dependency mod Mantle. MCHeli is not installed properly.

For monolithic archive hosting (one big ZIP file) copy.com works very well.

Your modpack archive has two folders named "/config/AppliedEnergistics2/". You should delete the one that does not have the extracells config file. Some of your mods are very out of date (CoFH mods, Waila, etc.)

You are using a version of MCPC+ with a known fatal bug. You will need to udpate that.

Any time you change the contents of your modpack archive you must increment the pack version number in your settings page for the Launcher ot be notified of the change.

Does Solder and the platform even support FTP as the mod source? I know that HTTP is the "blessed" method. What is your Solder API URL? (so that we may test it externally and verify that it looks as it should) What is the API URL for one of your modpacks?

The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive, not in a subfolder as yours are. I would highly recommend using a newer version of Forge, at least >= #1272. Your CustomNPCs mod is out of date.

No, you'll want to hit up IRC. There's no "official" support for Solder so no Tracker for that. I did notice that when using your personal URL it is exceedingly slow. Something on the order of 1 megabit. Might want to look into that.