Custom Modpack opening in Vanilla

[saamoz812]

I have recently tried to make a custom modpack. At first, it didn't download from Dropbox properly, and I had absolutely no idea what was wrong. The next day i tried to show one of my friends the problem... and it worked. I don't know why, but I'm not complaining, but now I have a different problem my pack opens in vanilla. When I checked the .technic file, all the mods, coremods, and everything else had downloaded properly. On a closer examination, it seemed that the modpack.jar did not go into the minecraft.jar properly. There it was, sitting 2 cemtimetres away from success, and I could have moved it manually, but I wanted everyone who downloaded this pack to be able to have it plug and play, and no one else seems to have this issue, so why do I? I'm probably making some silly mistake somewhere along the line, and if anyone knows what I have done incorrectly, it would be much appreciated.

Here is a picture of my bin folder:

https://www.dropbox.com/s/elfyo4kk0mxczkk/Bin%20Folder.PNG

[freakachu]

modpack.jar is supposed to be a separate file. it is merged into minecraft.jar by the launcher using black java magic when you load the pack.

[saamoz812]

modpack.jar is supposed to be a separate file. it is merged into minecraft.jar by the launcher using black java magic when you load the pack.

But that's the thing! I think I have some outdated magic because the files are not merging.

[saamoz812]

modpack.jar is supposed to be a separate file. it is merged into minecraft.jar by the launcher using black java magic when you load the pack.

But that's the thing! I think I have some outdated magic because the files are not merging.

EDIT: Oops, I pressed the post button twice.

[saamoz812]

But that's the thing! I think I may have some outdated magic because the files are not merging.

What?!!! I need to learn how to post.... :P

[freakachu]

then you are not setting up your modpack.jar correctly or there is some other issue. you seem to think they will literally merge and you will be left with a single, merged minecraft.jar. this isn't the case. you will always have both files, they are merged by the launcher in memory and not actually turned into one file at any point.

that's why it's black magic.

(it's not actually magic)

[saamoz812]

But I've looked in both files as they've downloaded and the Vanilla Minecraft .jar is missing the folders and files from the modpack.jar AKA forge. Even in the META-INF folder, which both copies have, one contains files named MOJANG.whatever, and the modpack.jar contains FORGE.whatever. None of the files from modpack.jar are merging, copying, transferring, or caring in any way.

[dwwojcik]

They never become one file. Both Forge's and Vanilla's files will NEVER appear to combine in windows explorer, because, in fact, they never will. They are loaded together on the fly by the launcher each time you start Minecraft. The way it is in that image you posted is the way it's supposed to be.

[freakachu]

But I've looked in both files as they've downloaded and the Vanilla Minecraft .jar is missing the folders and files from the modpack.jar AKA forge. Even in the META-INF folder, which both copies have, one contains files named MOJANG.whatever, and the modpack.jar contains FORGE.whatever. None of the files from modpack.jar are merging, copying, transferring, or caring in any way.

ok stay with me here

you ready?

paused your youtube and muted the TV? good.

THEY AREN'T SUPPOSED TO DO THAT. you won't see it happen, it doesn't happen on the disk at all ever. I'm trying not to bury you in jargon here but you are not getting it so here you go. the modpack.jar file is essentially superimposed on top of minecraft.jar via reflection by the launcher. no files are altered, the class replacement happens in memory (that's RAM, not your HDD) and is not permanent or written to disk in any way. that is what is happening. the merging is not an actual but a virtual one. is that clear enough now?

[saamoz812]

Ok, so I understand that bit, but that still doesn't explain why my modpack opens in Vanilla. According to what you said, the files and everything were correct, but when I open the pack, the bottom left of the screen only says Minecraft 1.5.2, there is no mods folder, and no mods are actually seen in game, not even on the creative tabs. I know this is not supposed to happen, so does anyone know why?

[freakachu]

well you have a modpack.jar, but chances are that you did not create it correctly. usually people balls it up by including extra folders in it or other things like that. the file structure inside the .jar file is very important.

[saamoz812]

The way I did it, is that I downloaded Minecraft Forge Recommended for 1.5.2 version 7.8.1.737, then I put it in a zip and made that zip a jar. I know it's in a jar because the icon is different, the type is executable jar file, and I have to select open with and choose WinRAR to open it.

[freakachu]

give me a link to your modpack file and I'll tell you what's wrong with it

[saamoz812]

Here's the link: http://www.technicpack.net/api/modpack/saamozcraft

Excuse the bad artwork, after I get the pack to work, that's next on the to-do list.

[freakachu]

ava.util.zip.ZipException: error in opening zip file

	at java.util.zip.ZipFile.open(Native Method)

	at java.util.zip.ZipFile.<init>(Unknown Source)

	at java.util.zip.ZipFile.<init>(Unknown Source)

	at java.util.jar.JarFile.<init>(Unknown Source)

	at java.util.jar.JarFile.<init>(Unknown Source)

	at org.spoutcraft.launcher.launch.MinecraftClassLoader.index(MinecraftClassLoader.java:90)

	at org.spoutcraft.launcher.launch.MinecraftClassLoader.<init>(MinecraftClassLoader.java:68)

	at org.spoutcraft.launcher.launch.MinecraftLauncher.getClassLoader(MinecraftLauncher.java:60)

	at org.spoutcraft.launcher.UpdateThread.runTasks(UpdateThread.java:147)

	at org.spoutcraft.launcher.UpdateThread.run(UpdateThread.java:95)

java.util.zip.ZipException: error in opening zip file

	at java.util.zip.ZipFile.open(Native Method)

	at java.util.zip.ZipFile.<init>(Unknown Source)

	at java.util.zip.ZipFile.<init>(Unknown Source)

	at java.util.jar.JarFile.<init>(Unknown Source)

	at java.util.jar.JarFile.<init>(Unknown Source)

	at org.spoutcraft.launcher.launch.MinecraftClassLoader.index(MinecraftClassLoader.java:90)

	at org.spoutcraft.launcher.launch.MinecraftClassLoader.<init>(MinecraftClassLoader.java:78)

	at org.spoutcraft.launcher.launch.MinecraftLauncher.getClassLoader(MinecraftLauncher.java:60)

	at org.spoutcraft.launcher.UpdateThread.runTasks(UpdateThread.java:147)

	at org.spoutcraft.launcher.UpdateThread.run(UpdateThread.java:95)

this is your problem. it can't open modpack.jar for whatever reason. I extracted the files, put them into a zip file using windows and then renamed it to modpack.jar and it worked. give that a shot.

and by "worked" I mean it didn't load vanilla. it doesn't actually load at all currently and just hangs when it gets to NEI it seems. but at least the tries to load some mods, which is more than it was doing before.

[saamoz812]

Thanks, I'll try and do the same thing on the original file, and add the mods one by one to see if I can find the problem. :)