Jump to content

Recommended Posts

  • Discord Moderator
Posted
  • The contents of your modpack archive are inside a subfolder. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive.
  • Your modpack is set to be MC 1.7.10, but your Forge version and mods are for 1.6.4.
  • You have an ancient version of Forge as your modpack.jar. Get the latest 1.6.4 version of Forge (#965).
  • You have two .class files in your mods folder. These should be removed.
  • You have mods in the coremods folder. Starting with Forge for MC 1.6+ the coremods folder is unused. All mod go in or below the mods folder.
  • Your modpack has no config files. This is always bad. Since your pack has few mods which add blocks/items you can get away without config files, but a full compliment of config files is a requirement in all cases.
Posted (edited)
  • Moved all the mods in /coremods/ into /mods/ and deleted the previous folder
  • Moved it down to 1.6.4
  • Downloaded the latest version of forge for 1.6.4
  • deleted them class files
  • Haven't yet done the config, but would this still make it run in vanilla? i would like to get the thing actually running before messing around with the configs XD

Thankyou

 

Also here is a new link for it, created it as new

 

http://www.technicpack.net/api/modpack/brightspark-164

Edited by BrightSpark

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...