plowmanplow

As I mentioned previously, this is what happens when you have item ID conflicts. You must fix those.

If you start a pack and it just shows up as vanilla then you do not have the proper modpack.jar file in your bin folder inside your modpack archive.

Your binmodpack.jar file is Forge build #935. You also have a ton of extraneous stuff in the bin folder. The only thing that should be in the bin folder is modpack.jar which is just the Forge universal binary jar download renamed to modpack.jar. The latest 1.6.4 version is Build #965. You do not have Tropicraft installed correctly. Follow the author's installation instructions. You do not have Weather mod installed correctly. However, Tropicraft includes weather mod so just remove the tornadoes zip file. You do not have Assissin'sCraft mod installed correctly. You do not have Tinker's Construct installed correctly. The JAR file goes in the mods folder. You have not included any config files in your modpack. This is always bad and often fatal. Once you have the pack working locally you will have a fully populated config folder. Include this in your pack. Make these changes and come back here if you are still having difficulties.

Look in your ForgeModLoader Client log for the word "CONFLICT". It will indicate a couple mods that are conflicting for the same ID. Chance the ID in the config file for one of those mods.

Provided you have console access to the Linux VPS just follow the instructions for a normal Solder install.

Pretty much all of those errors can be attributed to the mods being in a heavy development stage/beta at the moment. Not much you can do about that.

That error is related to the FoodPlus mod. Try updating to the latest stable version and see if that helps. (2.8PRE4 as of this post)

You have included REIMinimap for Forge/MC 1.6.2. Get the 1.6.4 version. You have included an old version of IC2 with known problems. If you are going to include IC2 I recommend looking at this post: You have included MutantCreatures mod but not the AnimationAPI mod it requires. Make sure you only get your mods from the author's preferred distribution channels so that you can also get the proper installation instructions. Your Iguana Tweaks mod for TConstruct is not compatible with the version of TConstruct you have. You need to use the experimental version. You have NEI but none of the addons/plugins additions. You probably want these. You have NEI but it is a RAR format archive. 1) All archive files intended for use by the platform must be in ZIP format. 2) The author does not distribute RAR files. See the third bullet point. Your CodeChickenCore is a RAR format archive. See previous bullet point. You need to manually update ForgeMultipart to Build #250. I don't use the OreSpawn mod but I find it hard to believe that it just doesn't work at all. However, I have had a number of packs lately that it just doesn't work in. It will crash the game with an exception in entity packets (Packet24). I'm not going to go through the entire pack to find out what the conflict is. I'll leave that up to you. If you want to use OreSpawn you'll likely need to ask some questions in the MCF thread. The IDFix mod often does "bad things". Use IDFixMinus instead. With IDFix in place Forge was throwing a very ambiguous exception. With IDFixMinus it was able to resolve most (all?) of the conflicts properly.

The file named "_4_l-= Insomnia _c_l[Ragecraft II] _4_l=-.DIM0.points" in modsrei_minimap is causing the launcher unzip process to fail. Really, you shouldn't be including the rei_minimap folder at all but you MUST delete at least that file.

You have included the Forge installer as your modpack.jar. This needs to be the Forge universal binary download renamed to modpack.jar. You have a few item ID conflicts between MineFantasy and Immibis' RedLogic.

Config files get generated the first time the mod is injected into Forge. You will have a fully populated config folder after you finish testing your pack locally. This is what you should be including in your modpack archive.

Dropbox file not found.

You don't mention if this is with a custom pack or one of the built in Technic packs. If it is a Technic pack then this post belongs in the appropriate Tracker. If the default packs work but a particular custom pack does not then you'll need to contact the pack author. Are you able to run Minecraft with Mojang's launcher?

All your top level folders (bin, config, mods, etc.) are in a subfolder inside the archive. They should all be a the top level. Your modpack.jar is named "modpack.jar.jar". Make sure you turn on visible file extensions to prevent this problem. Your pack settings, Forge version and mod versions are all messed up. You have your pack set to MC 1.7.5, your Forge version in the pack is 1.7.2-1060 (not even the latest recommended) and a mishmash of 1.7.2 and 1.6.4 mods. Pick a platform and make your modpack for that ONE platform/version.

How much memory does the physical machine have which is running this server? (looking at the rest of the pack now) It is typically bad form to include a texture pack (especially a large one) in your monolithic modpack archive. It bloats the pack and must be downloaded every time you update. Your Galacticraft is exceedingly old and should be updated. You currently have Mekanism 5 and IC2 in your pack. Make sure you NEVER use Universal Cable to carry EU. That version of Mek has a known corruption bug if you use Universal Cable to carry EU. You have ID conflicts all over the place. Fix all of those and then come back if you still have issues.

If you can connect locally, but remote people cannot then it is a port/access/connection issue. Use this: http://www.canyouseeme.org/ to test your open port.

It says right in your log what the problem is: 2014-05-18 11:37:03 [SEVERE] Encountered an unexpected exception OutOfMemoryError java.lang.OutOfMemoryError: PermGen space Increase the permgen allocation of your server process.

Not trying to be confrontational, but are you even looking at your crash report? Caused by: java.lang.IllegalArgumentException: Slot 4059 is already occupied by mods.morepistons.common.block.BlockMorePistonsSuper@69aee733 when adding gcewing.sg.SGControllerBlock

I could be mistaken, but I was sure that dropping the Optifine zip into the mods folder didn't work until later versions of Forge. If I start with a standard (reset) TekkitLite and put Optifine in my mods folder it does not register. If I put it in the modpack.jar it works as expected. You say it does work with TekkitLite. What Optifine file are you using?

You might have better luck in the Art Art Slap Slap forum.

Yes. You will need to seek help in the Tracker for problems with built-in packs and the Launcher.

Your crash report tells you exactly what the problem is: Caused by: java.lang.IllegalArgumentException: Slot 4057 is already occupied by mods.morepistons.common.block.BlockMorePistonsSuper@5821836d when adding gcewing.sg.SGBaseBlock@3b964f You have a block ID conflict between MorePistons mod and SGCraft. On a side note, there is no need to keep bumping. I know there aren't a lot of other folks currently assisting in Platform Pagoda (many thanks to those that do), but I do have a life outside of modpack support and I get back here as quickly and as often as I can.

The GregTech configuration goes crazy because GT is highly invasive and overwrites/overloads a MASSIVE amount of stuff in other mods. Personally I would never play a pack with GT in it (for lots of reasons), but different strokes for different folks. You are still including extraneous stuff from the bin folder in your pack. It is a violation of Mojang's EULA to include minecraft.jar in your modpack and it needlessly bloats your pack. The ONLY thing that should be in your bin folder is modpack.jar. Your modpack.jar is still WAY bigger than it should be. Not sure why that is but it should probably be checked. You should update ForgeMultipart to B250. You still have the LiteLoader Installer in your mods folder. That does not belong and should be removed. You have MMMPS but not the Addons mod. You probably want that. MMMPS is kind if gimpy without it. You have not added anything to microblocks.cfg. With all of the extra mods you have it is highly recommended to check all the blocks you wish to be cuttable/microblockable and include them in this file if they are not detected by default. You have not included Immibis Microblocks. IC2 cables are not compatible with Forge microblocks. If you wish to be able to microblock IC2 cable you will need to include this mod. You have done no tuning of the configs to manage ore spawning. Ore spawning is currently on in every mod that can do so. This may result in a much higher amount of ore than you want, and they will be of all different types/IDs.

Always interesting to see other folks' processes. I would make a couple suggestions concerning config files: I would be a bit more clear about the why and how of including config files. This is the biggest challenge I have when helping other people with their packs and it would be great to see more emphasis on that. It would be helpful to have at least something about ID conflicts in Pre-1.7 packs. You could mention something about searching the ForgeModLoader client log for the word CONFLICT and the need to resolve those.

That error means that you have a client only mod in your server. After looking through your list I would guess "Blood Particles" and "Battle Music", but without a link to your pack I can't say for certain. Always include a link to your pack when asking for help even if it is "private".