All Mod packs I add are Vanilla

[zenoaegis]

For some reason, any modpack I try to add to my Technic Launcher just ends up becoming Vanilla. Is there any quick fix someone could recommend?

EDIT: The modpacks I have tried to add are the ones already available on the technic site, such as "Feed the Beast" and "Science & Magic." But the modpacks that are already available when you download the Technic Launcher work just fine. When I try to install the modpack after adding it, I get a really weird decompression

Anyone know how to fix this?

[Spongeman131]

If it's a pack you made yourself there's 4 things you should check for:

-make sure that the modpack.jar you made was originally created as a .zip and then renamed to a .jar, .rar EXTENSIONS WILL NOT WORK

-make sure that the pack you're adding (the entirety of the pack which is the file that you download from the platform url and contains the config, mods and coremods folders) was compiled and archived originally as a .zip. It can THEN be renamed also to a .jar however this is unnecessary, .rar EXTRNSIONS WILL NOT WORK

-make sure that any mods eg forge, optifine etc.. etc.. were installed correctly into the modpack.jar file

-make sure that the direct-download link you provided in the Modpack info (the download link provided if you click on the "Edit" button when looking at the pack on the Technic website) actually is a direct download. The url checker isn't perfect and if you use Dropbox as your hosting service when you get the "share link" url from Dropbox, you must replace the "www." with "dl." in the beginning of the url ie:

"https://www.dropbox.com/s/_____________" -> https://dl.dropbox.com/s/____________

If all of these check out a-ok then when you launch the pack from the Launcher for the first time and it does what it needs to do to get you playing Minecraft, check the directory of the pack itself and make sure everything's there (the four things I listed above are all common issues that can cause improper extraction). If there's things missing then try deleting the pack from the launcher (making sure that the actual folder of the pack is removed in the launcher directory) and redownloading it again, it may just be an error. I've had it happen before.

[Zeeman1]

If it's a pack you made yourself there's 4 things you should check for:

-make sure that the modpack.jar you made was originally created as a .zip and then renamed to a .jar, .rar EXTENSIONS WILL NOT WORK

-make sure that the pack you're adding (the entirety of the pack which is the file that you download from the platform url and contains the config, mods and coremods folders) was compiled and archived originally as a .zip. It can THEN be renamed also to a .jar however this is unnecessary, .rar EXTRNSIONS WILL NOT WORK

-make sure that any mods eg forge, optifine etc.. etc.. were installed correctly into the modpack.jar file

-make sure that the direct-download link you provided in the Modpack info (the download link provided if you click on the "Edit" button when looking at the pack on the Technic website) actually is a direct download. The url checker isn't perfect and if you use Dropbox as your hosting service when you get the "share link" url from Dropbox, you must replace the "www." with "dl." in the beginning of the url ie:

"https://www.dropbox.com/s/_____________" -> https://dl.dropbox.com/s/____________

If all of these check out a-ok then when you launch the pack from the Launcher for the first time and it does what it needs to do to get you playing Minecraft, check the directory of the pack itself and make sure everything's there (the four things I listed above are all common issues that can cause improper extraction). If there's things missing then try deleting the pack from the launcher (making sure that the actual folder of the pack is removed in the launcher directory) and redownloading it again, it may just be an error. I've had it happen before.

Thank you soooo much. It works for me.