AliasXNeo Posted November 1, 2013 Share Posted November 1, 2013 Greetings, I have put together a custom pack as follows: pack folder / - config / - mods / - modpack.jar The modpack.jar is the latest Forge 1.6.2 universal JAR filed renamed accordingly. After uploading this ZIP file and pointing the launcher to it, it seems to download everything okay but when it goes to launch Minecraft it just launches it vanilla style (Forge doesn't load). One of the big differences I noted from my existing installation and the Technic version is the version file looks rather different. Does the Technic Launcher know which appropriate version.json to download for Forge? Any suggestions are much appreciated. Cheers. Link to comment Share on other sites More sharing options...
TwoTails Posted November 1, 2013 Share Posted November 1, 2013 you have it like this: pack.zip /pack folder /config /mods /bin right? well, all modpacks have to be like: pack.zip /config /mods /bin Link to comment Share on other sites More sharing options...
AliasXNeo Posted November 2, 2013 Author Share Posted November 2, 2013 you have it like this: pack.zip /pack folder /config /mods /bin right? well, all modpacks have to be like: pack.zip /config /mods /bin What goes in the bin folder? Link to comment Share on other sites More sharing options...
TwoTails Posted November 2, 2013 Share Posted November 2, 2013 What goes in the bin folder? The version.JSON for the version of minecraft the pack is and the uinversal download of the lateist version of MinecraftForge for your modpack's minecraft version. rember to rename the forgeversion.zip to modpack.jar 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