My Modpack Loads As Vanilla

[lewislovesgames]

I hid the modpack for testing so I'll give the API link instead: http://www.technicpack.net/api/modpack/engineers-toolkit       Github Link: https://github.com/lewislovesgames/Engineers-Toolkit

 

I'm using the beta technic launcher but I used the non beta aswell and it boots up as Vanilla Minecraft.

 

I used forge universal as my modpack jar file. Is this correct?

Edited November 14, 2014 by lewislovesgames

[plowmanplow]

• The contents of your modpack archive are in a subfolder. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive.
• You are using the correct version of Forge as your modpack.jar file.
• You are using some woefully outdated mod versions in your pack. All your CoFH mods and ProjectRed stand out as examples.
• You have the 1.6.2 version of Buildcraft. You need to be using the latest version of Buildcraft for Forge/MC 1.6.4 (1.6.4-4.2.2)
• Some of your mods (ChickenChunks for example) are named oddly. The implication is that you did not get them from the mod author's preferred distribution channels.
• You have no config files in your modpack archive. This is bad and often fatal for Forge/MC <=1.6.4.

This post on getting mods may help you:

 

This post on using my BareBonesPack to build your modpack has information about config files: