plowmanplow

You have one or more client-only mods in your server mods folder. After a quick glance I see the following obviously client-only mods: ArmorStatusHUD StatusEffectHUD NEIAddons (will probably work if left in, but provides nothing so better if removed) Zan's Minimap There may be more, but I can't know for certain without your pack. Always provide a link to your Technic pack page or API URL when requesting help.

I'm not trying to pick on you, but you are paying your host for a service which they should be supporting you for. Your pack works perfectly fine locally so this is specific to how your host manages things. We can be of little assistance.

Again, you'll need to check with your host to find out where the custom server jars need to be located in order for them to be detected by the interface.

I'm not familiar with the interface/setup of Multicraft environment. I believe you just have to have a specific folder in your directory structure with server jars inside which can be selected in the interface... but not 100% sure. Your host should be providing that info. If they are not then they aren't doing what you are paying them for.

Keep in mind that the server doesn't use a bin folder at all. Your host should give you options of using a particular server binary/type when setting up the server. You would need Forge for 1.6.4 or Cauldron/MCPC+ for 1.6.4 if you intend to use a modded server/client.

Providing the crash log is not going to help since it clearly states that you do indeed have a conflict with microblock registration. Please (always) provide a link to your Technic pack page and/or API URL.

Client: Your MMMPS recipe files are in the wrong location. They belong in configmachinemuserecipes, not in the mods folder. Server: I was able to create a server with your pack without removing any mods at all using both basic Forge and also using the latest version of Cauldron for 1.6.4 (for Bukkit plugins). You are going to need to be more specific with what is not working for you.

That archive contains a folder named "libraries" which needs to be in your top level server folder.

This thread belongs in the Platform Pagoda forum. I hope an admin will move it. Your modpack is not assembled correctly. It should contain three folders: bin, config, mods. The bin folder should ONLY contain the file modpack.jar. This file is simply the Forge universal binary JAR file (not the installer) which has been renamed to "modpack.jar". You should not be using the Forge Mod Loader (FML) installer in any way. If you intend to use LiteLoader for a 1.6.4 modpack the installation procedure is more complex than just dropping a mod in a folder. The config folder should contain all the config files for each of your mods. These files get created when the mod first gets loaded. Once you have finished testing the pack locally (you aren't doing that but should be) your local config folder will be full of config files. Include this folder and its contents in your pack. The mods folder contains all your mods. The mods you currently have in the bin folder should (mostly) be in the mods folder. You have a mishmash of 1.6.4 and 1.7.2 mods. This will not work. You need to decide on a version of Forge/MC you intend to use and build your pack for that version. You have the Tropicraft jar file in your mods folder but not the rest of the installation package. There are five other mods that comprise a working installation of Tropicraft. The implication is that you have either not followed the mod author's instructions or not gotten your mod directly from the author. Either is "bad". Read this:

@mw3_bean: You almost certainly do not have the "same problem". Also, don't hijack someone else's thread. Start a new one and provide error logs, crash reports, FML logs or something to detail your issue. Also, provide a link to your Technic pack page and/or API URL.

You are missing one or more required libraries. You can get them here: https://copy.com/qLsTvZfUUkkb

There is in Platform Pagoda. However, both the free Dropbox and copy.com services work just fine for direct-link file hosting. Details will be in that thread.

It looks like you might have a block in the Forge microblocks.cgf file that is being also auto detected and thus throwing an error.

Just make sure you resolve all those item ID conflicts, ESPECIALLY if you intend to make a server. The item ID conflicts will render significant portions of effected mods unusable. Glad it's working now.

The file named "modpack" in the bin folder should be named "modpack.jar". Optifine works poorly if at all in heavily modded 1.7.2 packs. You'll need to remove that. Fix those and come back if you still have problems.

You need to use the Tracker for the Launcher when requesting help for Technic's packs or the launcher.

You still have IronChests for 1.7.2 as PBlock96 already mentioned.

Make sure you aren't editing the version.json file in your bin folder. You need to be changing the one INSIDE the modpack.jar file. As for where to add, it depends on what you are adding. If you are increasing PermSize then yes, it would go in minecraftArguments. If you are adding a library dependency (for LiteLoader in 1.6) then it would go in the libraries section.

You MUST run the Cauldron installer, not just swap out the Cauldron jar file. The versions of some of the mods in the current Voltz beta are not compatible with the latest Cauldron.

Hmmm. I tested the server setup you provided and it works fine. I can connect with the Hexxit 1.0.10 client. Essentials commands work. WorldEdit works fine. Don't quite know what else to say.

It will be in your client modpack folder for your pack after you try to run it.

I guess we'll need your complete server folder to make any real diagnosis since what I gave you works perfectly fine on my system.

This collection of MCPC+, libraries and plugins works fine for me in 1.5.2: https://copy.com/lG2Yf2WxuXeC

That log is cut off and has no useful information. You have a potion ID conflict RotaryCraft and RandomThings at ID #35. Change the RotaryCraft "Freeze Potion ID" to 37. You still have a staggering number of item ID conflicts which need to be resolved. Check your ForgeModLoader client log for the word CONFLICT after you fix the potion ID.

Uninstall all Java. Download and install latest Java 7 JRE for 64bit.