Tuor56 Posted August 12, 2015 Posted August 12, 2015 If anyone could offer help, I'm relatively new to the modding community and have been up all night trying to this. I've followed tutorial after tutorial and ended up with this as my final outcome. The modpack is below. http://www.technicpack.net/modpack/thisisamodpackthatdoesathing.713478#
Poseidon5001 Posted August 12, 2015 Posted August 12, 2015 (edited) Ill try to take a look at it!Stay tuned! EDIT: Allright, so right from the bat, i tried swapping out the modpack.jar, for a forge universal, but that didnt work, so Im assuming you had done that.I see you are using a coremods folder. Minecraft forge doesnt use coremods anymore. Everything goes into the mods folder.As for why it starts in vanillla, Im still looking. EDIT 2: I may have found a solution, Im testing it now. In the modpack edit page, on the Technic website, you might have set game version to the wrong integer.EDIT 3: Yep, that was probably it. I took your jar file, put the mods you had in coremods in mods, and told technic launcher it was a 1.7 pack and it worked. It was probably downloading the libraries for another minecraft version, thus not launching up in forge.So basically, heres what you have to do:Put mods you have in coremods in modsDelete everything you have in the bin folder for the download, except the modpack.jar (which should be a 1.7 forge universal)Change the game version to 1.7.10 in modpack settings, then go to versions tab, and make an update, click update modpack.Then, reboot your technic launcher, update should be there and it should work! Edited August 12, 2015 by Poseidon5001
Tuor56 Posted August 12, 2015 Author Posted August 12, 2015 Ill try to take a look at it!Stay tuned! EDIT: Allright, so right from the bat, i tried swapping out the modpack.jar, for a forge universal, but that didnt work, so Im assuming you had done that.I see you are using a coremods folder. Minecraft forge doesnt use coremods anymore. Everything goes into the mods folder.As for why it starts in vanillla, Im still looking. EDIT 2: I may have found a solution, Im testing it now. In the modpack edit page, on the Technic website, you might have set game version to the wrong integer.EDIT 3: Yep, that was probably it. I took your jar file, put the mods you had in coremods in mods, and told technic launcher it was a 1.7 pack and it worked. It was probably downloading the libraries for another minecraft version, thus not launching up in forge.So basically, heres what you have to do:Put mods you have in coremods in modsDelete everything you have in the bin folder for the download, except the modpack.jar (which should be a 1.7 forge universal)Change the game version to 1.7.10 in modpack settings, then go to versions tab, and make an update, click update modpack.Then, reboot your technic launcher, update should be there and it should work!' We tried editing it and now it doesn't run at all. It simply reloads the technic launcher without anything working. If you're still able, please help.
Poseidon5001 Posted August 13, 2015 Posted August 13, 2015 (edited) My error, sorry. Did a stupid mistake.Ya, doesnt launch for me either, in forge that is.However, if i tried installing forge into the vanilla launcher, and put your mods in (oh, and you need to properly extract some of those from their zip files)It does launch, and then says it is missing hardlib.After installing hardlib v3.9,it said there were other missing mods, such as customoregen, outdated codechickencore, immibiscore. Then it said there were dual chocolate quests, since there was one, plus the one in the zip file in mods. So i kept the one that didnt say beta. I then updated ichun util, installed mantle.Then it launched!So, now I knew the mods were all sorted out.So what I did, is I took the config, mods folders, put them in a zip file, created a bin folder in that zip file, downloaded the latest forge universal (from files.minecraftforge.net) for 1.7.10 (v-1.7.10-10.13.4.1492), renamed it to modpack.jar, created a NEW modpack, for 1.7.10, called testerposeidon. I then put it into my dropbox public folder, as I always do to put the modpacks on the web. Once dropbox synced, I copied the public url of test.zip, and pasted that into modpack url, in the settings of testerposeidonAfter I posted an update to the pack (so it recognizes the changes), it launched just fine!If you repeat those steps and it still doesnt work for you, compare this file:https://dl.dropboxusercontent.com/u/182337284/test.zipto your zip that your pack downloads from P.S. I tried loading a world with it, and I was getting 10 frames.And i have a i7 4790k, 16gb of ram and a gtx 770, so might wanna add fastcraft or optifine in there (if the mod authors allow it, i forget)P.S.S. once the island i spawned in de-rendered, i jumped up to like 300. So, something fishy, but i guess just hope yu dont spawn on a survival island made of sand that is all falling into the ocean because of a big ae2 meteor thats forcing it to update. Edited August 13, 2015 by Poseidon5001 finished
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