Jump to content

Recommended Posts

Posted

Hello everyone! I have just found out how to fix the problem where a custom modpack would open in Vanilla Minecraft instead of Forge. I don't know if there are other tutorials on this, but I haven't seen one and have seen this problem a lot with no answer. Here I go.

First, this is if your modpack works and can be opened up by the launcher.

When the launcher installs your modpack, it does not include the modpack.jar with your pack. Here is how to fix this. Just go to /%appdata% (Or wherever Technic is installed)/.techic/(Your modpack name)/bin

If you look in that bin you see the modpack.jar isn't there. If it IS there, this isn't your fix. Just put your modpack.jar as you have it in your pack in the bin folder.

It should now work and be loaded up in Forge.

But there is another problem. The mods aren't loading up either. There is a folder in your modpack folder if you leave the bin that says your modpack name. Open it up, and all your mods and stuff should be in there. Just do what you did there in

/%appdata%/.technic/(Your modpack name)

and it should work.

I'm sorry if someone else posted this, or this bug only happened to me, but if it helped you please tell me below. Thank you!

Posted

After locating my technic pack folder in my /technic/ section, i found that the modpack had not been there. Upon placing it in there and starting up the pack via the launcher, it seems it just skips over downloading it and acts as if it does not exist even though it is in the folder and it still remains vanilla..

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...