plowmanplow

Download the latest 1.6.4 version of Forge Multipart yourself and include it in your pack in the mods1.6.4 folder: http://files.minecraftforge.net/ForgeMultipart/index_legacy.html

Please provide a link to your API URL when requesting help for a custom modpack. Since I haven't seen your pack yet, I created a simple pack and server with only Gany's Nether mod along with Forge and Immibis' microblocks mods. Using the default configs generated by the mods (no microblocks specified in configs) the client is able to connect to the server just fine with no conflicts or missing microblocks.

How are you adding LightLoader? What version of Forge/MC? What is the API URL for your custom pack? Those details will help us figure out what is going on. I have LiteLoader set up in 1.6.4 and it works fine so with additional information we can hopefully figure things out.

Ahh. Were it me and I was attempting to use someone's services (regardless if they were free or for-cost), and there was potentially a multi-week waiting period, I would seek alternatives.

Just because a client actually starts from the Launcher does not mean that it is "okay". There could be item ID conflicts (for packs <=1.6.4) or other mod interaction issues which need to be resolved. This resolution can only be accomplished when a full compliment of configs are included in the modpack archive. Including configs is not "optional" in the same way that fastening your seat belts in a care is "optional". Sure, the car will move without them fastened but it will yell at you and when something goes wrong you'll really wish you had taken the time to fasten them. Same goes for config files. My process for getting a working server for your pack: Place MCPC+ 1.5.2 JAR in new folder. We'll refer to that folder as SERVER. Copy coremods and mods folders from client pack download to SERVER. Launch client and copy out config folder from running client pack to SERVER. Removed Client-Only mods listed above, as well as BackTools. Started server. Connected with client.

I didn't see anything obvious on HapHost's site about anything having to wait 3 weeks. To what were you referring? As for free Solder hosting you may not get a lot of traction there. The Solder API requires some specific web server and storage space configurations as well as access to a SQL database. Those don't often come with free hosting solutions.

As was mentioned, fixing IDs manually is vastly preferred than attempting to use one of the automatic ID fixing mods as they either provide only a partial solution (often miss item ID conflits) or lose their minds when a large number of mods are present. Additionally, if you have an auto-fixing mod and add another mod to your pack you run a high risk of messing up any existing saved worlds you may have. This small guide to manually fixing ID conflicts may be of assistance:

No problem. As the only thing which required the removal of the downloads was the inclusion of capes in the mod, and they say they are actively working on a patch, we can only hope it won't take but a few days to resolve things.

I notice that you are using 32bit Java but have a video chipset of Intel HD 4000 (either built-in graphics on a desktop machine or a laptop). I would wager that any machine with the HD 4000 video is modern enough to be using a 64bit OS. Try updating your Java to Java 7 JRE 64bit (remove existing Java first). If that is successful increase the amount of memory allocated in the Launcher to 2G and see if the problem persists. If not, come back here and we will try additional troubleshooting.

The contents of your modpack are inside a subfolder. The primary folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. That's it. Looks like the rest should work. Give that a shot and come back if you are still having difficulties.

I don't "spam every thread". Although I am grateful when other folks contribute to problems and issues in Platform Pagoda and Server Op Swap Shop, since I know so little about so many different topics in this area, I am providing the vast majority of support in both subforums. The challenge comes when people don't follow the posting guidelines like OP here. His post belonged in the Tracker for the Launcher (after searching for similar issues of course). I am not a forum admin and so I try not to admonish folks too strongly (no back-seat moderating). I try to point them in the direction they need to go if they have made a mistake in posting while tacking on a little relevant/contextual information if I don't feel it is encouraging or enabling them in violating the posting guidelines. What it boils down to is: I do my best to give folks the information they need. Unfortunately, sometimes this is not the information they want, but that is their problem.

Always provide the full crash report either in a spoiler tag here or in a pastebin and link it here. Without that is is almost impossible to know for sure what is happening and we are simply guessing. As Vlandox mentioned, it seems like something is maybe having problems putting an item into a stuffed itemduct. The rest of the crash report would have relevant information about that.

Since you haven't provided any links (preferrably your API URL) it is impossible to say for sure, but it sounds like you have the contents of your modpack (bin, config, mods) inside a subfolder in your modpack archive. Make sure that the primary folders are at the top level of the folder structure in the modpack archive.

That link points to a file that does not exist. We have no idea what your problem is. Use your words primarily and only refer to pictures for specific purposes.

Directly from Skuli's post advertising the 3.1.2 beta of Voltz:

Client Pack: You have a file named "minecraftforge-universal-1.5.2-7.8.1.737.zip" in your bin folder. This should be removed. Your modpack.jar is oddly sized. I assume you added something to the Forge JAR? You have no config files. This is "bad", especially when intending to use the pack with a server. You have three different SmartMoving mods in your mods folder. Remove all but the one for Forge. Client Only Mods: coremodsCustomPortForge.jar coremodsNEIPlugins-1.0.9.3.jar modsBackTools modsSmartMoving modsVoxelMap

It would be wise to bring it up to both mods and to Forge/Lex.

When you say that you are having trouble, what do you mean exactly? Does the client error out when downloading the pack if you have a zipped mod in your pack? Does the Solder interface not let you add it? The thing is, Solder doesn't care at all what's in the ZIP files that are added to the API through the interface. All the client does is ask for a list of ZIP files to download, downloads them into the cache folder, then unzips them into the pack folder. It doesn't care if the contents of one of those zips is a JAR file or a ZIP file (or any other type of file for that matter).

Your binmodpack.jar file is messed up. The modpack.jar file is simply the Forge universal binary JAR file for your chosen version of MC renamed to be "modpack.jar". You have a number of woefully outdated mods: IndustrialCraft2, Project Red, bspkrsCore, etc. If you intend to include IC2 in your 1.6.4 pack I highly recommend reading this post: Fix those issues and come back here if you still have problems.

Always provide a link to the Technic Platform page or API URL for your pack when requesting assistance. It looks like you have a mismatched mod or mod version, but I'll need the pack to test further.

The Aether II team has removed their downloads for the mod to comply with the current Minecraft EULA. I can't test something I can't download.

The Technic Launcher uses the exact same system to authenticate accounts as the vanilla launcher (i.e. Mojang's authentication services). If you are still having troubles you are either not using the correct credentials or something is messed up in your client. In the latter case you should make a post in the Tracker for the Launcher.

That feature would require the use of the Solder API: https://github.com/TechnicPack/TechnicSolder The Solder API has essentially no support at all. If that page does not have all the information you need to get it working then you should probably not use it.

@jominer247: It has little to do with server resources and everything to do with keeping everything related to a single issue/pack together in one place. It is a PITA to bounce between three or four different threads to collect the information necessary to effectively diagnose issues. @Preeus: It is a good thing that this is your pack. Go ahead and update the mods, update the modpack download for your pack settings and come back here if you are still having issues.

@Ozurr: There seems to be a problem with Twilight Forest's initialization. The error you are seeing is common in a 1.6.4 pack when an ID is set outside the allowable range or there is a conflict of some sort. However, you have a 1.7.2 pack and that really shouldn't happen. Please provide a link to the Platform page or API URL of your modpack.