Jump to content

Recommended Posts

Posted

How? my folders are:

bin

modpack.jar

Does this mean that your modpack.jar is in the root directory, if so then that is your problem, it needs to be in the bin dir

hence "/bin/modpack.jar"

Posted

Well here are a list of problems with your pack

  1. You need a direct download link (dl.dropbox.com) for the client
  2. This is a rar file, the launcher can only unpack zip files
  3. It's suppose to be config, not configs
  4. It's suppose to be coremods, not coremod
  5. You have packed the minecraft.jar which is piracy - The launcher will download minecraft.jar
  6. You have packed Plasmacraft-0.3.3.zip twice
  7. You have packed the matmos download and the matmos mod, this may cause issues with FML
  8. You have not generated any of the config files, there may be unresolved ID conflicts

WARNING: Dropbox will shutdown your direct links if your traffic exceeds their limits

Posted

Well here are a list of problems with your pack

  1. You need a direct download link (dl.dropbox.com) for the client
  2. This is a rar file, the launcher can only unpack zip files
  3. It's suppose to be config, not configs
  4. It's suppose to be coremods, not coremod
  5. You have packed the minecraft.jar which is piracy - The launcher will download minecraft.jar
  6. You have packed Plasmacraft-0.3.3.zip twice
  7. You have packed the matmos download and the matmos mod, this may cause issues with FML
  8. You have not generated any of the config files, there may be unresolved ID conflicts

WARNING: Dropbox will shutdown your direct links if your traffic exceeds their limits

thanks for your help! also how do you make it the 'dl.dropbox.com' like you were saying

Posted

how do you generate config files

Run the pack, it will generate the config files as each mod is loaded, if it does not load (gray screen or crash) then check the log files of the launcher and your pack for an error stack, if you encounter an ID conflict the stack will tell you which mod caused the error and which item in that mod, change the ID via the newly generated config files and try again

Some mods have not received the 4096 patch so if you set the ID over 4096 you may receive an out of bounds error, just use an ID below 4096 if this happens

Posted

Run the pack, it will generate the config files as each mod is loaded, if it does not load (gray screen or crash) then check the log files of the launcher and your pack for an error stack, if you encounter an ID conflict the stack will tell you which mod caused the error and which item in that mod, change the ID via the newly generated config files and try again

Some mods have not received the 4096 patch so if you set the ID over 4096 you may receive an out of bounds error, just use an ID below 4096 if this happens

Errrrm......

Posted

Run the pack, if forge loads successfully then it will generate configs, just launch your pack then check the logs for errors, then fix them

repeat until all errors are gone

  • 1 month later...

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