Big Problem with Modpack

[Ludrum]

Hey Guys!

 

First: This is my first Post. so if I do something wrong, please tell me

 

Now to my "Big" Problem: I just made a custom Modpack (Old Link: https://www.dropbox.com/s/vl78mjik43mzd2n/Test%20Modpack.zip?dl=1 New Link: https://www.dropbox.com/s/ib1eoq5ikxe864g/Ludrum%20Modpack.zip?dl=1) with a few mods. If I press the Play button, it opens Vanilla Minecraft. I've got all Configs and renamed the Universal Version of Forge, to "modpack.jar" (with the extensions enabled!)

I already tried:

• Just ComputerCraft and no other mods.
• Adding the "servers.dat" File. It didnt worked and I couldn't see it in the modpack Folder.
• I looked into the minecraft (& modpack) jar. And I didn't found any files from Forge. I tried to add them manually, but that didnt worked.

I googled and searched on this Forum, but didn't found anything. I think its just something simple, but I cant figure it out...

 

P.S.: My first language is German, so if I said something wrong. I'm sorry.

Edited August 28, 2014 by Ludrum

[plowmanplow]

A well crafted post. My only suggestion would be to include the API URL (the URL you add to the launcher) in your post.

• Your modpack.jar file is a RAR format archive. All archive files intended for use in the platform must be in ZIP format only. That being said, the modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. Don't extract it or alter it in any way (unless you REALLY know what you are doing).

Fix that and come back if you are still having troubles.

[Ludrum]

Okay, thanks for the reply ! So, the link that I posted was a test with the archive. I created a "modpack.jar" and drag & dropped the files from the Forge Universal Version in the created "modpack.jar". With the new download Link (https://www.dropbox.com/s/ib1eoq5ikxe864g/Ludrum%20Modpack.zip?dl=1) that's "fixed". So I just downloaded the newest Forge Version for 1.6.4 (9.11.1.965) and renamed it to "modpack.jar", its 100% not "modpack.jar.zip" (I also tried it with 9.11.1.953, which is the Version I used with the Vanilla Launcher). I didn't modified it in any way. But it still doesn't work :/ Btw, my API URL is this: http://www.technicpack.net/api/modpack/test-von-ludrum.

Edited August 28, 2014 by Ludrum

[plowmanplow]

The reason I always ask for the API URL is because I use this page: http://www.circlecraft.info/platform/ . It allows me to see the pack details and link to the download URL in a similar fashion as the Launcher and makes it easier to track down problems.

• You have a couple item ID conflicts that need fixed. Search your ForgeModLoader-client-0.log file for the word CONFLICT. Not all of them can/should be addressed, but the ones that list a conflict between two different mods (like ThermalExpansion and AlchemicalWizardry) must be fixed.
• When I copy your config and mods folders to my BareBonesPack setup for 1.6.4 the client starts just fine (other than the aforementioned conflicts).

[Ludrum]

First: I looked into my config folder and found two JARs. But if it works with your BareBonesPack all is right, so that can't be the Problem. But, I can't find the log from Forge. I don't know if I'm too dumb or something is really going wrong...I think for normal they're in the modpack directory (.technicmodpacksmodpackname). But there, I can just find "options.txt", "output-client.log" & "output-serer.log". I searched in all Folders (bin, cache, config, coremods, etc.) but I couldn't find that log file...

Edited August 28, 2014 by Ludrum

[plowmanplow]

For 1.6.4 packs, the logs are in the modpacks's folder.

[Ludrum]

 

For 1.6.4 packs, the logs are in the modpack's folder.

I don't know if you mean the ".technic/modpacks"-Folder or the ".technic/modpacks/test-von-ludrum"-Folder. But I can't find any Forge-Log. And if I look in a folder from another Pack, e. g. Hexxit. I can see the "ForgeModLoader-client-0.log". But in the Folder from my Modpack is nothing, except the "standart" logs/txt files...

Edited August 29, 2014 by Ludrum

[plowmanplow]

The challenge for me is that your updated download you provided works. The modpack itself does not because you haven't updated the version number and download URL in the pack settings. Until the latter happens your client modpack won't change and you won't get a Forge log.

[Ludrum]

Ohhhhh, I didn't knew that I have to increase the Version Number that the Technic Launcher updates it. *facepalm* A big thanks to you for the help!

 

P.S.: The Download URL wasn't the Problem. That was just to test something with the Config.

Edited August 29, 2014 by Ludrum