Downloading custom modpack error

[emesquita]

I've created a custom modpack and uploaded it to dropbox but I just can't download it in the technic launcher. Here's the log: http://pastebin.com/L1bA3VFz

Edited July 2, 2014 by emesquita

[plowmanplow]

You are getting an unknown host exception for dropbox.com which is odd. However, you also have your URL set incorrectly for downloading your modpack. The URL must be a direct download. If you use the URL and it takes you to a page which presents you with a download button it is not a direct URL. You need to append ?dl=1 to the URL, like this:

https://www.dropbox.com/s/u6hgbvqbvypcvki/modpcak.rar?dl=1

[emesquita]

Well, it worked but after a while, it gave me the same error. Here's the new log: http://pastebin.com/ZaQcaVxU

[plowmanplow]

• Your modpack.jar file is in RAR format. All archive files intended for use in the platform MUST be in ZIP format only.
• Your modpack.jar contents is inside a subfolder. The modpack.jar file is simply the Forge universal binary JAR file for your chosen version renamed to modpack.jar. Don't extract it, don't mess with it, don't do anything but rename it unless you REALLY know what you are doing.
• Not sure where PowerCrystalsCore-1.1.8-10.jar came from. Pretty sure the last released version was 1.1.8-9. Might want to look into that.
• You need to upgrade to 4.3.7.32 of ProjectRed.
• You have ArmorStatusHUD installed but not the dependency mod bspkrsCore.
• You have Chisel installed but not the dependency mod AutoUtils.
• You have CompactUtils installed but not the dependency mod Aroma1997Core.
• You have RotaryCraft installed but not the dependency mod DragonAPI.
• You have Modular Force Field Systems installed but not the dependency mod CalclaviaCore.
• You have (an outdated version of) Modular Powersuits but not the dependency mod Numina.
• You have Portal Gun installed but not the dependency mod iChunUtil.
• You have ThermalExpansion installed but not the dependency mod CoFHCore.
• You have ThaumicTinkerer installed but not the dependency mod ThaumCraft. Thaumic Tinkerer "enhances" the large mod that is ThaumCraft. It is useless without ThaumCraft.
• You have More Food installed but not the dependency mod ClashsoftLib.
• You have Opis installed but not the dependency mod MobiusCore.
• You have Immibis Microblocks installed but not the dependency library Immibis Core.
• You have a completely ancient version of Immibis Microblocks installed. However, the file does not have the same name as the files downloaded from the author's website. The implication is that you didn't get the mod from the author. This is always "bad".
• The default config files generated by the mods have a staggering number of block ID conflicts. You need to work through all these to fix them because the pack will never start unless you do.
• You have not included any config files with your modpack. Config files are generated the first time each mod is injected into Forge/MC. The config folder and all of its contents MUST be included in your modpack after all conflicts have been resolved.
• Without getting the pack to start (see previous bullet point) it is impossible to say, but I suspect there are numerous item ID conflicts in the default config files. After resolving all the block ID conflicts you will need to inspect the ForgeModLoader client log to identify item ID conflicts and resolve any which can be resolved.

It is clear that you have never tried to test or debug this pack locally before assembling your modpack. It is also clear that you are either not getting the mods directly from the author's preferred distribution channels (don't copy mods from other packs) or have failed to read any of the author's installation instructions. This is "bad". Always follow author's instructions. Always get mods directly from the mod authors preferred distribution channels.

 

The "correct" way to create a pack, especially one this big, is to start with ONLY forge in your modpack (binmodpack.jar) and make sure that works as expected in the launcher. Then methodically add in mods singly, or in logical groups (mod and dependency, multi-part mods like ProjectRed, etc.), so you can test things as you go and identify individual problems before you have a large laundry list of problems like you see above.

 

Make all of these corrections and come back here if you are still having trouble.

[emesquita]

I didn't understand the second step. Can you explain it better?

[plowmanplow]

Be more specific. The "second step"? The second step of what? The second bullet point? The second paragraph? Please state precisely which part you do not understand. Is that the only part you don't understand?

Edited July 3, 2014 by plowmanplow

[emesquita]

The second bullet point.

[plowmanplow]

It is safe for you to interpret that bullet point as "Download Forge and rename it to modpack.jar".

[emesquita]

It is already like that. I mean, I renamed it and put it on "bin"

Edited July 3, 2014 by emesquita

[plowmanplow]

Since you have yet to provide a link to your Technic pack page or API URL I can only assume you haven't updated your modpack yet and are referring to the version I did my previous analysis on.

 

I have already said it a couple times so I am not sure how to be more explicit. Do these steps EXACTLY as I state here and your modpack.jar should be fine. Your current version is completely messed up, as previously mentioned:

1. Download the Latest Forge universal binary JAR file from here: http://files.minecraftforge.net/
2. Rename the file you downloaded in Step #1 to "modpack.jar".
3. Place the file you renamed in Step #2 in your bin folder.

[emesquita]

Do I need to get the "universal" or the "installer"? I'm trying to do this exacly how it should be...

[plowmanplow]

Heh, had I wanted you to get the installer I would have suggested getting the "installer" instead of specifically stating (multiple times) to get the "universal" binary.

[emesquita]

sorry. I'm greedy, I can't pay much attention to this... I'll do my best.

[plowmanplow]

sorry. I'm greedy, I can't pay much attention to this... I'll do my best.

 

Not really sure how to respond to this. Your pack is reasonably large and completely jacked up. I am fairly experienced at this and it would probably take me a couple hours to get everything fixed, conflicts resolved, and balanced. You have your work cut out for you.

[emesquita]

Leave it to me. Just tell me what I need to do and I'll fix it.

[plowmanplow]

Not sure if you are saying you need additional information or not. I'm fairly sure I've left pretty specific details on everything that needs fixed.

[emesquita]

t

Edited July 4, 2014 by emesquita

[emesquita]

Forget the last post, I wasn't suppose to do that. I did every thing you told me, but now, it doesn't launch: http://pastebin.com/scmqSLFB

[plowmanplow]

Post a link to your Technic pack page or API URL. Should have asked for that a long time ago.

[emesquita]

here it is http://www.technicpack.net/api/modpack/a-guerra-de-justinos

[plowmanplow]

• You are building a 1.6.4 pack but have included Forge for 1.7.2. Get the latest/last 1.6.4 version (Build #965).
• You still have PowerCrystalsCore-1.1.8-10.jar.
• Your bspkrsCore mod has an odd name and is an old version. The implication here is that you did not get that mod from the author's site/threads.
• Your Calclavia mods are out of date and mismatched. To install MFFS go here and follow the instructions: calclavia.com/download/?name=Modular%20Force%20Field%20System&r=http%3A%2F%2Fcalclavia.com%2Fjenkins%2Fjobs%2FModular%20Force%20Field%20System%2Fbuilds%2F91%2Farchive%2Foutput%2FModular-Force-Field-System-3.6.3.91-core.jar
• You still have the same long list of block ID conflicts. This is because you are not including any config files in your pack! Your pack WILL NOT work without a full compliment of config files in which the block and item ID conflicts have been resolved.

You are closer. Keep at it.

[emesquita]

I can't get bspkrsCore from the author. I just can't find it... I mean, forget it, I just found it

 

Naturally where can I find the mods directly from the author?

Edited July 5, 2014 by emesquita

[plowmanplow]

Getting Mods:

[emesquita]

Ok every thing is ready. Now, I just have to fix the ID conflicts. How to do that? 

[plowmanplow]

Which ID conflicts? The block ID or item ID conflicts? After you get all the other problems fixed and start the pack it should generate an IDConflicts.txt file and warn you about it. Open that file. It references which mods are conflicting on which blocks. Just change one of their configs.

 

For item ID conflicts, you have to examine your FML client log for the word "CONFLICT" (without quotes) and fix them the same way as block IDs by changing the config of one of the mods.