Jump to content

Recommended Posts

Posted

I recently created a technic pack for a server that I help manage.  While testing it I noticed that it is just making a file in the modpack directory called what the name of the file was with everything in it instead of moving them into the bin, mods, and config folder within the pack.  This causes it to launch a unmodded version of minecraft.

 

 

Here is the pack if you would like to see this for yourself.

http://www.technicpack.net/modpack/details/lualand-modpack.509613

Posted

The one difference I had when I created my modpack was that I named the modpack file modpack.zip since that's what the tutorial I watched told me, maybe that's it? I'll try testing it and I'll let you know

  • Discord Moderator
Posted
  • The contents of your modpack archive are in a subfolder. All of the required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive.

Other than that, your pack seems to start just fine. Item of note: I used Forge 1231 instead of the 1217 that you have in your pack.

Posted (edited)

 

  • The contents of your modpack archive are in a subfolder. All of the required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive.

Other than that, your pack seems to start just fine. Item of note: I used Forge 1231 instead of the 1217 that you have in your pack.

 

 

 

They were actually in the top level of the folder structure, but after you said this i tested a different way of zipping the files and it worked.  The way I zipped it this time produced a exact copy of how I zipped it last time, but it actually worked this time.  Thank you anyway.

Edited by valithor2

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...