Regular minecraft launches instead of custom modpack

[Phrosst]

I created a modpack but I can't download it. Its uploaded on Dropbox. I have reinstalled the launcher and I have the recommended java version, java 7 update 51. I have followed the steps from this page, '?do=embed' frameborder='0' data-embedContent>>, and didnt fix it.

 

I can download other mods but not the one I put together.

 

Update: I downloaded my modpack from dropbox, codpied and pasted the link into the modpack location field and its was not a valid link.

 

Update: I fixed the download problem and I can download my pack, however when I click play with my pack selected regular minecraft launches instead. I also followed the guide that is stickied in this forum section.

 

heres  the mod pack page: http://www.technicpack.net/api/modpack/modpack-by-phrosst

 

and here is the modpack it self: https://dl.dropboxusercontent.com/u/273184883/Modpack.zip

 

Thanks for the replies.

Edited March 4, 2014 by Phrosst

[Yoshi41023]

I had this problem in the past.

 

You wanna go on dropbox, click the modpack thing, select Share Link, right click (NOT LEFT CLICK) the download link and select Copy Link Address.

 

Go to the Modpack Edit page, for the Modpack Location you will paste what you have copied.

[plowmanplow]

In order to receive help you will need to post up the link to your Technic pack page.

[Phrosst]

OP updated

[plowmanplow]

• You have everything in your pack archive inside a subfolder called "Modpack". All the contents (bin, config, mods, etc.) need to be at the top level of the archive, not in a subfolder.
• It looks like you are trying to assemble a 1.6.4 pack, but are using the 1.4.7 version of Forge (6.6.2.534 to be specific). You will need the most recent 1.6.4 version of forge as your modpack.jar file (1.6.4_9.11.1.965). Also, I'm not sure where you got that modpack.jar, but it is not the base Forge universal. This may be intentional, but if it was not you might want to start from scratch when moving over to the latest 1.6.4 Forge.
• You have some mods in the "coremods" folder. Forge for 1.6.4 does not use a coremods folder. Everything goes into "mods".
• I do not think you have Millenaire installed correctly.
• You have ProjectZuluComplete and ProjectZuluCore. If you have Complete I don't think you need Core, although I could be wrong.
• You have mismatched versions of mods. As I mentioned previously, you seem to be assembling a 1.6.4 pack but you have included the Forge/MC 1.5.1 version of BetterDungeons/Chocolate Quest. It is vitally important that you use the correct version of the mod with the matching version of Forge/MC. In this case, the latest 1.6.4 version of the mod is 2.08.
• And last, but not least, you aren't including any config files with your pack. With a very small number of mods you can sometimes get away with this but it is still easy to run into conflicts. If you ever want to use this on a server then you MUST include configs because some mods will try to auto-assign IDs and you can't know that you have the same config as the server unless you include them in your pack archive.

Making these changes allowed me to start your pack successfully with all of the mods you were trying to use except for Millenaire since I'm not messing with that.

Edited March 4, 2014 by plowmanplow

[Phrosst]

Thanks