My custom modpack is launching as vanilla.

[The Wadapan]

Hello. I've spent close to twelve or more hours making a custom modpack for a small group of friends to run on a server. We're running an Akliz server, and I created the modpack inside a blank Vanilla Minecraft .minecraft folder. Then I moved all the mod files, neccessary configs to prevent idconflicts, a new universal forge .jar (named modpack.jar) and stuff into a new archive with a couple of folders. I've spent forever trawling these forums to find a solution that actually worked, but it seemed everyone was making the same mistakes and their situations weren't the same as mine. So here I am, posting yet another of these topics. I've been following a mixture of these guides:

 

-

[NuclearBurrito]

When I tested it, the game told me that the right version of Forge was not installed (specifically, it said that the minimum version was 9.11.1.965). Did you use the right version of forge when you made the pack? If it loads on vanilla and not in the Technic pack, it doesn't make sense. If you have the right version of Forge, then I'll take another look, but try that first.

[The Wadapan]

Okay, I'll have a look at what I've done. I think the problem may be something to do with me using a different version of forge than in the client - I used the installer on the client to installl it, but just direct-downloaded the .jar for Tekkit.

 

EDIT 1: I've looked at the downloads and realised that yes, I was using the next-oldest version because I went to the legacy links. My bad. I downloaded the latest one, shoved it in my installed-via-the-launcher files to see if it would work, and it does. 

 

However, I was looking through the log after it failed to connect to my server, and I noticed that there were loads of errors. I think I'll just re-do the client-side pack from scratch, and see if that fixes it. Basically, it wouldn't connect to the server due to ID mismatches. All of them in the 20,000 to 21,000 range, if I remember correctly. Because there were so many I decided it must have been due to doing it all in Vanilla Minecraft's client at the start. I'll move the .jars and .zips again and see if that works.

 

Oh, and about the .zips... Forge seems to have trouble recognising them as mods. It does, but in the log it doesn't seem to like them. However, the mod instructions say just to drag them in and not extract them or anything.

Edited December 7, 2014 by The Wadapan

[plowmanplow]

Errors in the logs, especially when the pack starts and works as expected, are not always an issue. Some mods have files in them that Forge does not handle well, or the mod tries to call back to a web site/page which isn't available and an error is generated. Many mods have broken or missing mcmod.info files and Forge will complain about that as well.

[The Wadapan]

I didn't have much time to come back and wrap up this thread, but it was a problem with the .jar. I've changed it now and it's working great, the server's running fine. Thanks for the help!

Edited December 9, 2014 by The Wadapan