Dromoka Posted June 8, 2020 Posted June 8, 2020 Hey guys, So I made a modpack with some mods in it and uploaded it to Technic, and it worked just fine. I then wanted to make a new modpack which was the same as the previous one, minus a few mods (as they weren't compatible with a server I wanted to make). Except this new modpack doesn't work, as each time I play with it Technic just launches Vanilla Minecraft 1.12.2. I've tried and re-tried making the modpack from scratch, as well as copying the previous modpack and just deleting the mods I didn't want anymore. But I still get the same issue. To run you through exactly what I did with the copying: I took my old modpack files (the one that works), copied the whole folder on my desktop, went into the 'mods' folder, deleted the mod files I didn't want anymore, selected the modpack folder, added to archive (using WinRAR), made it a ZIP, uploaded the file into Dropbox, copied the Share link to the modpack file location in Technic (changing the last part to dl=1), update the modpack, then open the Technic Launcher, find and install my new modpack, then click Play, which opens Vanilla Minecraft... My guess is that this problem could be due to Forge not being properly installed in the new modpack as it has a new location, but normally all the files in the old modpack are also present in the new one. Another possibility is that the mods in the new folder aren't properly installed on a 'clean client'. Or it could be something else; I'm not very tech-savvy. Either way I hope someone is able to tell me what the problem might be and how exactly I can fix it. Any help is greatly appreciated! Thanks in advance! (PS: both my modpacks are hidden as I haven't yet asked for permission from the mod creators to add their mods to a modpack. I will of course get their permission before making the modpacks public)
Forum Administrators Lord Ptolemy Posted June 8, 2020 Forum Administrators Posted June 8, 2020 Not a launcher issue. Moved to Platform Pagoda. For newer 1.12.2 Forge versions:
Dromoka Posted June 8, 2020 Author Posted June 8, 2020 6 hours ago, Lord Ptolemy said: Not a launcher issue. Moved to Platform Pagoda.Not a launcher issue. Moved to Platform Pagoda. For newer 1.12.2 Forge versions: Thanks for moving it to the right forum. However I'm using Minecraft 1.12.2, for both modpacks. And Forge works fine in the first one, and as I just copy-pasted, it should be the same Forge file that's present in the second pack too.
TerdyTheTerd Posted June 8, 2020 Posted June 8, 2020 Very rarely files can become corrupt when copy/pasting. Did you verify that the modpack.jar is still valid? Otherwise please provide the Technic log file after attempting to launch the modpack. Dromoka 1
Dromoka Posted June 9, 2020 Author Posted June 9, 2020 20 hours ago, TerdyTheTerd said: Very rarely files can become corrupt when copy/pasting. Did you verify that the modpack.jar is still valid? Otherwise please provide the Technic log file after attempting to launch the modpack. Ah I didn't know, thanks for the info. That could very well be the cause of the problem. How would I check the validity of the jar file? Or provide the log file? (Sorry for my lack of knowledge, technology is not my strong point)
TerdyTheTerd Posted June 9, 2020 Posted June 9, 2020 You can try opening the file with winrar, otherwise you can try manually re-creating it (there are plenty of guides on this). Providing the log would be easiest, to get to the log file you can open "Launcher Options" then "Open Logs". Find the most recent log, open it, copy the content and use something like pastebin.com or hastebin.com to paste the contents into, then link that here (this is so nobody has to download a file, which is a potential security threat). Dromoka 1
Dromoka Posted June 9, 2020 Author Posted June 9, 2020 10 minutes ago, TerdyTheTerd said: You can try opening the file with winrar, otherwise you can try manually re-creating it (there are plenty of guides on this). Providing the log would be easiest, to get to the log file you can open "Launcher Options" then "Open Logs". Find the most recent log, open it, copy the content and use something like pastebin.com or hastebin.com to paste the contents into, then link that here (this is so nobody has to download a file, which is a potential security threat). Ok thanks! Here is a log file of today: https://pastebin.com/FGegfwC0 I just opened Technic, played my modpack, saw that Vanilla had opened, and closed Minecraft.
JaariAtmc Posted June 9, 2020 Posted June 9, 2020 2 minutes ago, Dromoka said: Ok thanks! Here is a log file of today: https://pastebin.com/FGegfwC0 I just opened Technic, played my modpack, saw that Vanilla had opened, and closed Minecraft. That modpack is not correctly zipped. When I opened the zip, I saw a modpack folder. I should be seeing the bin/mods (and also config) folders.
Dromoka Posted June 9, 2020 Author Posted June 9, 2020 25 minutes ago, JaariAtmc said: That modpack is not correctly zipped. When I opened the zip, I saw a modpack folder. I should be seeing the bin/mods (and also config) folders. I just reuploaded the 'correctly zipped' file to Technic, relaunched the launcher, reinstalled the pack and clicked Play, only to run back into the same problem. I've already tried zipping the file both ways already, neither work, so I don't think that was the issue at hand here (unless I'm being completely stupid; which is not impossible). https://pastebin.com/V8WaDgKs
TerdyTheTerd Posted June 9, 2020 Posted June 9, 2020 Your modpack.jar is misnamed, its currently called "modpack.jar.jar". This is from the modpack download file You may have misnamed this on accident, windows will by default hide some extension names, you can show them by pressing "View" tab and then "File Name extensions" Just remove the extra .jar and you should be good to go
Dromoka Posted June 10, 2020 Author Posted June 10, 2020 (edited) 13 hours ago, TerdyTheTerd said: Your modpack.jar is misnamed, its currently called "modpack.jar.jar". This is from the modpack download file You may have misnamed this on accident, windows will by default hide some extension names, you can show them by pressing "View" tab and then "File Name extensions" Just remove the extra .jar and you should be good to go I'm afraid that this didn't fix the problem... https://pastebin.com/CH93U9eF I have however now enabled the file name extensions showing so I don't make silly mistakes like that in the future Edited June 10, 2020 by Dromoka
Forum Administrators Lord Ptolemy Posted June 10, 2020 Forum Administrators Posted June 10, 2020 2 hours ago, Dromoka said: I'm afraid that this didn't fix the problem... https://pastebin.com/CH93U9eF I have however now enabled the file name extensions showing so I don't make silly mistakes like that in the future On 6/8/2020 at 9:45 AM, Lord Ptolemy said: Not a launcher issue. Moved to Platform Pagoda. For newer 1.12.2 Forge versions:
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now