plowmanplow

You will get a much more direct response in the Technic IRC channel. #technic on SynIRC.

Your BiblioCraft mod is quite out of date. Your Biomes O' Plenty mod is fatally out of date and has a Windows version number " (1)" in the file name. Get the latest 1.7.10 version and remove the Windows version numbers from any mod file names. Your Extra Utilities mod is fatally out of date. MCHeli is not a valid archive and is not installed correctly even if it was. Your ChickenBones mods are fatally out of date. You should be using the "latest" 1.7.10 versions. Your Tinkers' Construct mod is fatally out of date. Your Tinkers' Mechworks is fatally out of date. Waila is fatally out of date. Many of these suggestions should seem familiar. I have mentioned most of them to you before. Asking for help, getting my suggestions and then not following them isn't very productive.

A quick fix for your script may be to add the recursive flag (-r) to the rm command in your find statement. You can't "rm" a folder which contains files in Linux/Unix. Adding the recursive flag will make it walk through the folder and remove everything so you can achieve a complete removal. A more robust backup script would possibly archive the players/playerdata folder to a compressed archive to save a ton of space (and allow you to keep more if you wished). It might also instead use rsync to do hard linked backups which would provide the appearance of all full backups (for ease of use) but with deduplication at the file level in order to save significant space.

Copy.com public share links must have "?download=1" (without quotes) appended to the URL.

The crash report you sent me has vastly different mods from the download you provided, and from your current client pack. The first step in getting a server going is to get a properly built client pack working, which you have not done. I'll do the client pack analysis now, based on your current version: MCHeli is not properly installed. Always follow the mod authors instructions. You have multiple mods from illegitimate sources. This is always bad and commonly yields outdated or non-working mods. Always get your mods directly from the mod authors. Any mod named in the format of "ModName-Mod-1.7.10.jar" is likely not legitimate. You have multiple mods with "(1)" in the file name. This is bad and sometimes causes fatal issues. It is caused by downloading a file to a folder which already contains a file by that name. Fix the file names by removing the " (1)". You have mods which are out of sync. For instance, you have a RC version of Nether Ores but release versions of other TeamCoFH mods. This is bad. You have a fatally out of date version of Tinkers' Construct. If you intend to make a server for a pack, the client pack must contain a full set of config files which match what is on the server. This is explained in the link I initially provided.

The crash report you sent me has vastly different mods from the download you provided, and from your current client pack. The first step in getting a server going is to get a properly built client pack working, which you have not done. I'll do the client pack analysis now, based on your current version: MCHeli is not properly installed. Always follow the mod authors instructions. You have multiple mods from illegitimate sources. This is always bad and commonly yields outdated or non-working mods. Always get your mods directly from the mod authors. Any mod named in the format of "ModName-Mod-1.7.10.jar" is likely not legitimate. You have multiple mods with "(1)" in the file name. This is bad and sometimes causes fatal issues. It is caused by downloading a file to a folder which already contains a file by that name. Fix the file names by removing the " (1)". You have mods which are out of sync. For instance, you have a RC version of Nether Ores but release versions of other TeamCoFH mods. This is bad. You have a fatally out of date version of Tinkers' Construct. If you intend to make a server for a pack, the client pack must contain a full set of config files which match what is on the server. This is explained in the link I initially provided.

Decorative Simplicity

Decorative Simplicity

You have multiple mods from illegitimate sources. This is always bad and commonly yields outdated or non-working mods. Always get your mods directly from the mod authors. Any mod named in the format of "ModName-Mod-1.7.10.jar" is likely not legitimate. Your ProjectRed mods have no version number in the file name. Makes me suspicious they aren't from the approved sources. Your mods are not compatible with your selected version of Forge. You should be using at least the latest recommended Forge and all of the latest mod versions.

You have multiple mods from illegitimate sources. This is always bad and commonly yields outdated or non-working mods. Always get your mods directly from the mod authors. Any mod named in the format of "ModName-Mod-1.7.10.jar" is likely not legitimate. Your ProjectRed mods have no version number in the file name. Makes me suspicious they aren't from the approved sources. Your mods are not compatible with your selected version of Forge. You should be using at least the latest recommended Forge and all of the latest mod versions.

I'm not going to build a server pack for you. If you provide a download link for your existing server that isn't working I'll try to tell you how to fix it.

I'm not going to build a server pack for you. If you provide a download link for your existing server that isn't working I'll try to tell you how to fix it.

It is always better to provide the files in the modpack archive instead of letting them be deploaded (dependency loaded) dynamically.

Always provide the API URL or a link to the pack details page for the client even when requesting custom server assistance. This post about converting a pack to a server should help: http://forums.technicpack.net/topic/61989-server-of-fury-i-would-like-more-help/#comment-519381

You are correct concerning the config files. One commonly has multiple packs served through Solder and it is not uncommon to provide the same mod for multiple packs. If the config files are packaged with the mods it is difficult to have different configs for different packs which is commonly required. Put the MC version in the mod version number in Solder. For example, InventoryTweaks has a file version number of 1.59-156 as the latest 1.7.10 but 1.59-176 as the latest MC 1.8 version. Without the 1.7.10 or 1.8 in the version number it can get confusing when managing packs. Don't "bundle" mods unless there is a compelling reason to do so. For instance, Galacticraft will almost always be provided with all three mod files so bundling that might be fine. However, you might want to remove one or more of the Mekanism or ProjectRed mod files for particular packs.

Always provide the API URL or a link to your pack details page when requesting custom modpack assistance. This contains metadata crucial to a proper analysis. Your pack should not contain a /bin/modpack.json file. This will be overwritten by the contents of the modpack.jar every time the pack is launched. Edit the file inside the modpack.jar file if you need to alter it. Your modpack.jar file is not correct. The modpack.jar file is simply the correct version of the Forge universal binary JAR file renamed to modpack.jar.

The only real difference between the client and server is that the server doesn't use a /bin/ folder (that is specific to the Technic Launcher) and that all client only mods must be removed from the server. Otherwise everything is the same. I'll once again refer you to the original link I provided on turning a client pack into a server. There are plenty of details there.

bspkrsCore, ForgeMultipart (which should be updated), MrTJPCore all belong in /mods/1.7.10/.

You can provide the API URL or a link to your pack details page directly here. Only use a pastebin service for log data. I need the API URL or pack details page link, not a download link for the pack. The required folders should be named: bin, config, mods. You have capital letters for the first character of each folder name. You have a fatally old version of Forge for 1.7.10 as the modpack.jar in your pack. You should be using at least the recommended version of Forge. After you update your Forge version you will no longer need the Legacy Java Fixer mod.

bspkrsCore is a required dependency mod for TreeCapitator and should be in the /mods/1.7.10/ folder. ExtraTiC requires Tinkers' Construct to be in the pack. Modpacks should not be platform dependent as long as they are properly assembled.

You have the Forge/MC 1.8 version of Inventory Tweaks. You need this version: InventoryTweaks-1.59-dev-156.jar You are missing the "Base" ProjectRed mod.

Your ChickenBones mods are fatally out of date. Download the "latest" versions for 1.7.10. Address this and come back if you still have troubles.

You are using a severely outdated version of Forge/Cauldron which requires the Legacy Java Fixer to be in the /mods/ folder.

Make sure you are incrementing the pack version number any time you alter the modpack archive or the download URL. You have a duplicate enchantment ID: java.lang.IllegalArgumentException: Duplicate enchantment id! class noppes.npcs.enchants.EnchantDamage and class am2.enchantments.EnchantMagicResist Enchantment ID:100

Java 8 on a Forge 1.6.4_965 pack without Legacy Java Fixer throws a CME which doesn't look like that error. Please provide the API URL or a link to the pack details page when requesting custom modpack assistance.