SapphireTerraria Posted November 15, 2015 Share Posted November 15, 2015 (edited) Hello, I have been having a couple of issues with my modpack, Magology, which are now fixed. All but 1. I can't seem to figure out how to make it run forge and not 1.7.10 (the vanilla version that is)? I've looked through the modpack versions, no forge. I've looked through the forums and ways to do it, and tried some, but again - no forge. Thanks in advance. Edited November 15, 2015 by SapphireTerraria Link to comment Share on other sites More sharing options...
Moderators AetherPirate Posted November 15, 2015 Moderators Share Posted November 15, 2015 post a link to your modpack Link to comment Share on other sites More sharing options...
SapphireTerraria Posted November 15, 2015 Author Share Posted November 15, 2015 post a link to your modpack http://www.technicpack.net/modpack/magology.763015 Link to comment Share on other sites More sharing options...
Moderators AetherPirate Posted November 15, 2015 Moderators Share Posted November 15, 2015 The Bin folder should have the forge universal .jar, renamed to modpack.jar. Your bin folder only has the vanilla minecraft .jar Your mods folder is empty. Instead, you put them in \magology\mods. Move them in the mods folder at the root, and get rid of the magology folder. The directory structure should look like this: Bin folder has renamed forge universal for 1.7.10 (modpack.jar) Config has all the config files that are generated once the pack is successfully launched once. Mods has all the .jar files for your mods. Don't put mods in subfolders. Forge won't see them. Zip it all up, Name your zip file modpack.zip, and upload it to dropbox. Increment your modpack version number in your Technic profile. Report back if you get new errors or issues that you are stuck on. Link to comment Share on other sites More sharing options...
SapphireTerraria Posted November 16, 2015 Author Share Posted November 16, 2015 The Bin folder should have the forge universal .jar, renamed to modpack.jar. Your bin folder only has the vanilla minecraft .jar Your mods folder is empty. Instead, you put them in \magology\mods. Move them in the mods folder at the root, and get rid of the magology folder. The directory structure should look like this: Bin folder has renamed forge universal for 1.7.10 (modpack.jar) Config has all the config files that are generated once the pack is successfully launched once. Mods has all the .jar files for your mods. Don't put mods in subfolders. Forge won't see them. Zip it all up, Name your zip file modpack.zip, and upload it to dropbox. Increment your modpack version number in your Technic profile. Report back if you get new errors or issues that you are stuck on. I have already done the bin folder with the modpack.jar forge, but I had to create the bin folder because it didn't exist (I had run the modpack before) For me, the config files are in there...? Most mods are Jar files, some not but they're not in sub-folders. Zipped, dropbox(ed?) already. Link to comment Share on other sites More sharing options...
Moderators AetherPirate Posted November 16, 2015 Moderators Share Posted November 16, 2015 There should be no folder called magology. Move everything in there out and put them in the appropriate top level folders, and delete that magology folder. Bin Config Mods No magology folder. I'll post pics of the correct directory structure if you need it. Link to comment Share on other sites More sharing options...
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