Greetings. It seems I cannot get my modpack to load correctly.

[Mr.Goat]

Okay, you see, whenever I try to open up the modpack, it opens up vanilla. I really do not know what to do, and I have tried everything that seems useful. I really just want to create a modded server for me and my friends, and I don't know if I can because of the modpack not working correctly. If anyone could help I would be really greatful. Here is the dropbox link:

 

https://dl.dropboxusercontent.com/s/8y569fiotkosbny/Barebones.zip?dl=1&token_hash=AAGQi1_Kj-oOXyKFNZe9TqBU6iHl_rXPJzJY89kOnzwY6A

 

fyi, plowmanplow, I did use your idea for barebones(just the name)

[dwwojcik]

Changing "Buttz.jar" to "modpack.jar" should fix it.

Edited May 3, 2014 by dwwojcik

[plowmanplow]

Changing "Buttz.jar" to "modpack.jar" should fix it.

@dwwojcik: Turns out he has all the contents of what should be in the modpack.jar inside a subfolder in the archive.

 

@Mr.Goat:

• The "bin" folder just needs modpack.jar inside it. That modpack.jar file is just the Forge universal jar file renamed to "modpack.jar". No need to extract it and recreate the jar file. Just rename the file you download from Forge.
• It looks like you have a number of mods for Forge/MC 1.6.2 but are making a 1.6.4 pack. You need to get the 1.6.4 versions of those mods.
• You have included iChun's Hats mod but not the iChunUtil dependency library.
• It looks like you have extracted some of the mods into folders inside the "mods" folder. While this mostly "works", it is not the "proper" way to do things. Just leave the mod jar/zip files as they are in the mods folder.

[dwwojcik]

 

@dwwojcik: Turns out he has all the contents of what should be in the modpack.jar inside a subfolder in the archive.

Ahh, ok.

[plowmanplow]

Ahh, ok.

Always good to see more folks who know what they are doing (which I know you do) hop in with suggestions and help. Feels a little lonely in here sometimes, hehe.

[dwwojcik]

Yeah, I can imagine.

[Munaus]

Always good to see more folks who know what they are doing (which I know you do) hop in with suggestions and help. Feels a little lonely in here sometimes, hehe.

you should see the launcher subsection in the Tracker...

there's only one idiot doing that one... I'd wish there were more

[plowmanplow]

I might have to branch out. Only so many folks making packs.

[Mr.Goat]

Thank you all. I am going to try this. If it works thank you, if not I will be back.

[Mr.Goat]

Update: the pack did not work. I updated the mods and everything and it still didn't work

Probably just a stupid mistake on my part. Will make sure I did everything correctly.

[Mr.Goat]

uuuummmmm. The modpack now just tries to load, but then doesn't do anything

[Mr.Goat]

Now it says something about codechickencore. I have codechickencore installed

What do I do?

[plowmanplow]

• Forge/MC 1.6.4 does not use the coremods folder. All mods go into the mods folder.
• Flan's weapon packs go in a top level "Flan" folder, not inside the mods folder.
• The CodeChickenCore mods you had in the coremods folder has an odd name. The implication is that you have not downloaded that mod from the author's preferred distribution channels. Always get the mods from their source.
• You have the MoreExplosives mod which is for 1.6.2 and I find no 1.6.4 version available. This mod does not seem to work with 1.6.4.
• Your necromancy mod is for 1.6.2. Update to the 1.6.4 version.
• Some of your Flan's weapon packs are conflicting or overwriting item IDs.
• You have included no config files in your modpack. Always include the config folder with contents from your working modpack.

[Mr.Goat]

 

 

• You have included no config files in your modpack. Always include the config folder with contents from your working modpack.

I have seen this alot. what config files?

[plowmanplow]

After you have your pack working locally you will have a fully populated config folder. This config folder and its contents needs to be included in your final modpack archive ZIP which you publish.