plowmanplow

From an administrative perspective, maintaining more than a few packs as monolithic ZIP archives would be a total pain in the butt. The whole point of using Solder is to make it easier to administer, and easier for users to keep up with since changes are differential instead of full copies. Add to that the ability to keep old versions around in case things go unexpectedly pear shaped after an update and you have very compelling reasons to adopt Solder. Setting it up takes 5-10 minutes for someone who knows what they are doing. Obviously it will take a bit longer for someone who doesn't do this sort of thing often, but the reward is well worth it, especially considering that the bulk of the setup and configuration only has to be done once.

A little information about running as the root user. I'll toss out an analogy since I love them so much. Imagine you have a front door of a large building and that building is full of other doors, behind which may be other doors and possibly lots of goodies for you to heist. You find a way to get in the front door only to realize that every other door is barred shut with massive, difficult to pick locks and huge metal frames and wire mesh in all the walls. You might be able to clean out the lobby, but the rest of the doors are challenging and by the time you get through them someone may be tapping on your shoulder with an AK-47. Now, imagine you get through that same door only now there is a giant button in the lobby that is labeled "Press here to unlock all other doors in the building and disable all security systems". This building is a lot easier to pilfer. The second scenario is what you are dealing with when you run what should be a user space service as root. Security vulnerabilities are invariably found in everything from the underlying software (Kernel, Java, etc.) to the service itself. If you find a way to execute some arbitrary code by exploiting a vulnerability through the service, that code is executed with the same privileges as the service. If the privilege level is that of a user, and you have locked the system down well (isolation, patches, multi-level security, etc.) then they only get the goods from that small subset of the server. If the service is running as root then the code can do anything the root user can do... which is anything at all. Now, this doesn't take into consideration things like SELinux Contexts and such, but I'd be willing to wager $20 that there isn't a MC server in existence running in an environment like that.

The modpack settings are set to be a 1.7.2 modpack. The mods are 1.7.2 mods. The version of Forge you have is Forge/MC 1.5.2. Get the 1.7.2 version of Forge.

Dropbox and copy.com are two great choices for modpack hosting.

I don't know about "wtp", but for the rest of them the 1.7.2 version is the correct one to use for 1.7.10.

Please provide the API URL for your modpack. It looks like either the version of Forge in your pack doesn't match the pack settings, or your pack settings are incorrect.

Your download link is private (and may not be direct). I'm not sure if anyone has gotten Google Drive to work with the platform for downloading modpacks.

512M of RAM is not enough for most modpacks. You will need to increase that to at least 1G and likely higher. Never go beyond 50% of the total RAM in your PC.

Manuas: My apologies. I'll do that in the future. Thank you for your patience.

This post probably belongs in Platform Pagoda. Make sure you have the latest Java 7 (not 8) 64bit for your OS. Having 64bit Java is the only way to set more than 1G of allocated RAM in the client. Once you have 64bit Java 7 installed you can increase your memory allocation. Don't go above 3G or 50% of your system RAM, whichever is lowest.

The contents of your modpack archive ZIP file is another ZIP archive. No need to zip things up twice as it won't work that way.

From your crash report: cpw.mods.fml.common.LoaderException: thaumicenergistics.ThaumicEnergistics$IncorrectAEVersion: Thaumic Energistics is unable to load. Your version of Applied Energistics is incompatible. Please use version rv1-beta-30 or equivalent. Your have two mods which are not in sync with each other. Also, the download URL for your pack doesn't work (broken link). The link should look like this: https://copy.com/DUHnFluUIvu4?download=1 However, yours looks like this: https://copy.com/web/users/user-13510751/copy/modpack.zip?download=1

Those are a feature of EE2 which were not implemented in the version of EE3 included in TekkitLite.

It looks like you have the 1.6.4 version of OpenMods mods. You'll need the (beta) 1.7.10 versions: http://openmods.info:8080/

You have duplicate Chisel mod files in your mods folder. MCHeli mod is not installed correctly. You have OpenBlocks mod but not the dependency mod OpenModsLib. You have no config files in your modpack. This is always bad and often fatal. This post explains a bit about configs: Fix these issues and come back if you are still having difficulties.

This post probably belongs in Platform Pagoda or Server Op Swap Shop. Are you certain you have ChocolateQuest/BetterDungeons installed correctly? The error above indicates that you may be missing part or all of the contents of the top level Chocolate folder.

That list does not contain the hashes for 1.5.2.

If you follow this process: everything should work fine. Just make sure you remove the client only mods, but that is the exact process I used to make the server that worked on my system.

Expected MD5: 6499480480a063b69149d96e298efa16 Calculated MD5: 17f49b095c2fb0bd610987995caf85ab The assumption here is that you have changed that ZIP file after adding it to Solder and Solder has the wrong MD5. You can go to that mod and version in your Solder interface and tell it to rehash. Not sure if you will need to create a new build to get the client to realize there is an update, but since that would be the only thing you are changing it wouldn't be a big deal for downloads and such.

Your client pack's bin folder should not contain the minecraft.jar file. Client Only Mods: Dynamic Lights ReiMinimap TiCTooltips Removing the client only mods allowed me to start a server and connect with your client.

You really need to update your Java to the latest Java 7 64bit. Forge/MC >= 1.6.x does not use a coremods folder in any way. All mods go in or below the mods folder. I don't see anything else that stands out as being obviously wrong but you are right, total hang. I would recommend taking out mods in logical groups until it starts and start diagnosing from there.

Your bin folder has too much in it. The bin folder should only contain the modpack.jar file. Your mods made by ChickenBones are still out of date. Where are you obtaining his mods from? This is his site: http://chickenbones.net/Pages/links.html (select 1.6.4) The version of Modular Powersuits (and Numina) you have isn't compatible with other mods. Get this version (MMMPS and Numina): http://build.technicpack.net/job/ModularPowersuits/118/ After that I was able to start your pack.

You definitely want to be running the absolute latest of all versions of ChickenBones' mods for 1.7.10.

This error means that one of your mods is either client only or is improperly using the APIs so that the client-only code in a mod is not properly SMP aware: cpw.mods.fml.common.LoaderException: java.lang.NoClassDefFoundError: net/minecraft/client/Minecraft Having access to your latest forge log would probably help as well.

Making someone an OP: from the server console, just type "op playername". If you are an OP already, you can type "/op playername" in game. Increasing the memory allocated to the server is done from within the batch file you use to launch the server. There are two parameters (-Xmx and -Xms) you should see indicating an amount of memory (something like -Xmx1024m). Change them as required.