Jump to content

Bocaj1000

Members
  • Posts

    3
  • Joined

  • Last visited

About Bocaj1000

  • Birthday 10/02/1999

Bocaj1000's Achievements

Dirt

Dirt (1/9)

0

Reputation

  1. Use Drop Box and upload your pack. Then hit the share link button and copy that address then do this: Replace the www with dl so it says https://dl.dropbox... Then at the end after (Your modpack name).zip add ?dl=1. The final web address should say- https://dl.dropbox.com/....../(Your modpack).zip?dl=1 Put that address in the modpack location on the Technic website.
  2. 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!
×
×
  • Create New...