plowmanplow

Unfortunately, yes. I am using the Solder API to provide 10 unique builds for a single pack that are all different instead of the "normal" incrementing modpack version numbers. This will make the launcher think you are "updating" a version when switching between Forge builds. This will clean out the mods folder.

Your Technic pack settings have the MC version set to 1.7.2 instead of 1.6.4.

You have included a version of Advanced Solar Panels for Forge/MC 1.6.2 and for the wrong version of IC2 Experimental. Get version 3.4.7 for IC2 Experimental from here: http://forum.industrial-craft.net/index.php?page=Thread&postID=27372 You have a large number of item ID conflicts in the default config files generated by the mods. You will need to resolve these and then include a full set of configs in the config folder in your modpack archive.

The way that a mod works internally with Forge and Minecraft is that Forge gets its classes injected into Minecraft providing an API on which the mods rely. The integration of mods into Forge requires an initialization process during which the configs get created (if the mod does that and a pox on the mods that dont!). So, yes, the config files get generated even if a mod fails that initialization process. However, since the integration of mods halts when there is a fatal error not ALL configs for all mods will get created until the pack successfully starts. This is why you need to be testing your pack locally, adding mods individually or in logical groups until you have a working local setup and THEN you build your modpack archive from there.

The config files get created when the mod launches for the first time. Once you have a working pack THEN include the whole config folder in your modpack archive.

I don't know where Resonant Induction is getting that value from, but just change the multipart.cfg.

You have included a version of Enchiridion for Forge/MC 1.7.2. Get the 1.6.4 version. You have not included a full, working set of config files with your modpack. Some packs can get away with this but larger packs, like yours, seldom do. In your case this is a fatal oversight. You have multiple block ID conflicts in the default configs which need to be resolved.

After launcher the client open up the file named "ForgeModLoader-client-0.log" in a decent text editor (Notepad++, Vim, etc.) and search for the word "CONFLICT" (without quotes). It will show you what ID (likely shifted up by 256 from the one listed in the config files) is conflicting and between which mods.

Provide links to your direct download and the Technic pack page and/or API URL.

As far as the launcher downloading modpacks is concerned there is no difference between a 1.6 pack and a 1.7 pack. There has to be something going on with your local machine. Try turning off antivirus, try resetting the pack, try using a different host (copy.com works great). See what happens.

There is a "Tracker" button at the top of the page here. Inside there is a bug tracker for the Launcher. That is the best/appropriate place for questions like this.

Heh, wasn't trying to overload you. If you have any questions about specific mods just ask.

I would highly recommend using MCPC+ as your server binary even if you don't intend on adding any Bukkit plugins. MCPC+ adds some optimizations for things like mob spawning and item entity aggregation which can be quite helpful. Download the latest MCPC+ to a folder we'll call SERVER: http://ci.md-5.net/job/MCPC-Plus-164/ Copy your config and mods folders to SERVER. Remove any client-only mods from the SERVER mods folder. Start server.

Yes. Half way through your post I literally said out loud, "this dude is going to have to contact his host and ask why his server is hanging."

RedLogic for 1.5.2 requires that immibis microblocks be installed. However, after doing so the default config values in immibis.cfg for RedLogic will have two fatal block ID conflicts. These should be easily resolved. Item of note: I believe you also have a number of item ID conflicts between MineFantasy and BuildCraft which really need to be resolved. Check your FML client log.

Uhh, you said "I'm also trying to make a mod pack and I don't know how to do that with a mod pack". That makes no sense.

I use pretty much this exact collection of mods plus about 70 more. Everything works flawlessly. Obviously this is only anecdotal but I see nothing in your client log or my client and server logs which would indicate a problem of any sort. What other information can you give us? Are you running the server on the same physical system as your local client? How much physical RAM does the server have, or your local PC if both on the same system? It looks like you are giving your client 1G of RAM. How much are you allocating to the server? What server binary are you using? MCPC+? Basic Forge? What is your view distance set to in the server.properties file? When the client seems to hang are you still able to type commands and receive output in the server console? Are there ever any errors/exceptions in the server.log or ForgModLoader server log file? Socket timeouts would be expected if you are getting kicked. Do you kind of follow the direction I'm headed here? Any other pertinent information would be helpful.

Your pack settings are set to Minecraft 1.7.5 but the latest version of Forge is for 1.7.2. You have no modpack download URL in your pack settings.

Hard to debug something I can't see Just put together what you have and we'll take a peek.

Without a link to your pack, the only think I could suggest would be to try updating to 55.4.1, the last 1.5.2 version.

This.

Without a link to your pack I can't say for certain (hint), but it has to be there.

Updated BareBonesPack to include Forge for 1.7.2 #1098

@Soft_Squishy: You can't be critical of folks who have offered you legitimate input or help without coming across as a bit pretentious. The mod you have referenced is not ready for "prime time" if the author can't get the whole bit depth independence thing figured out. "Next Update" sometimes means next week. Sometimes it ends up being "never". Good luck in your (solo) quest.

To my knowledge, no, there is nothing that will provide this functionality. It would be pretty straight forward with MCPC+ (as you already mentioned) and I can even think of a few ways that players could make their own choice using signs or command blocks, or some other gimmick.