Jump to content

Recommended Posts

Posted (edited)

I was wondering If someone could help me?
For some reason my custom pack works but when it loads up theres no mods loaded.

If anyone can help it'd be much appreciated.. Im still a bit new to tekkit but im very computerminecraft savvy. Its most likely something very simple.

 

Im not seeing anything standing out really in console either. They just dont load.
http://www.technicpa...ands-of-paroria
http://www.technicpack.net/modpack/details/lands-of-paroria.345932
https://www.dropbox.com/s/h3jnli4ya2i1tf4/ParoriaModPack.zip

Edited by tommygoesha
  • Discord Moderator
Posted
  • You bin folder should only contain the Forge universal binary (965) renamed to "modpack.jar".
  • The coremod folder is unneeded and can be safely removed.
  • Your mods1.6.4 folder has the forge universal binary in it. This should be moved to your bin folder and renamed (see bullet 1)
  • Your mods1.6.4 folder has the liteloader installer jar. Installing Liteloader in Forge/MC 1.6.4 takes a bit of jumping through hoops. I have a modpack.jar with the required changes already installed you can use. Remove your current installer jar and use this: https://copy.com/y2HRNF4mr3Zb?download=1
  • On a related note, it seems you wanted to install LiteLoader but I don't see any LiteLoader mods. Was that on purpose?
  • You have a version of InventoryTweaks for 1.7.2. Get the 1.6.4 version (will say 1.6.2 or 1.6.2+).
  • You have two different copies of RenderPlayerAPI installed. Use the correct/current version.
  • Your PlayerAPI and SmartMoving mods are named "oddly" (not the author's file names). Remove them and get the most recent 1.6.4 version from the author.
  • Your included version of GraveStone mod is for 1.7.2. Get the 1.6.4 version.
  • You haven't included any config files (mildly understandable since you have never successfully started the pack). Once you make these changes and get the pack to start properly you need to include the config folder and all its contents in your pack archive ZIP file.
Posted (edited)

First off thank you.

Bullet 5 - There was a mod (Ill edit this and recheck, although i mightve removed it unknowngly) that required liteloader and said forge may work but there were some reports of bugs so I wanted to be safe then sorry.
Bullet 6 - I got from another Modpack that ran on 1.6.4 so i thought it'd work but ill go ahead and switch.

Bullet 8 - At first when I downloaded they were named just MC Player 1.6.4 Player API forge 1.2.zip but when I opened the zip there was a .jar so I just moved it out. (any zip I found a .jar in I just took out and put it in the main file)

Bullet 9 - Didnt know there was a 1.6.4 Thank you

Bullet 10 - I dont know where the config files would be? Dont they come up when it runs? Or do you mean when It runs I need to copy the config and put it in the .zip (thats in the dropbox?) so that it loads the same for everyone?

 

Question by the way as just a side note: How is it that players cant edit the config files and help themselves to shit?

Edited by tommygoesha
Posted

 

  • You bin folder should only contain the Forge universal binary (965) renamed to "modpack.jar".

Im not fully understanding this? do I rename the folder "bin" > "modpack.jar"? or when I download whatever forge unversal binary (965) I should rename that?

  • Discord Moderator
Posted
  • As for the SmartMoving mod and it's dependencies, you had the original "download" for Render Player that needed to be extracted and it looked like they might have been mismatched versions. I could be mistaken, but it wouldn't hurt to just download them all again from the author's preferred distribution channels and re-extract them.
  • Always get your mods from the author's preferred distribution channels. This will ensure that you have the correct version and that you have the proper installation procedures.
  • Yes, the config files get created when the mods get injected into Forge/MC. Once you have the pack working this whole config folder needs to be included in your pack archive. This ensures that everyone has the same, predictable configs and gives you an opportunity to fix/prevent ID conflicts and to balance mods against each other.

About "modpack.jar":

 

Normally the only thing that should be in your bin folder is modpack.jar. Also, modpack.jar is usually just the Forge universal binary jar renamed to "modpack.jar". However, in your case, since it seemed like you wanted to have LiteLoader, there needs to be some changes made to this (specifically to the version.json file inside the jar). I went ahead and published a link to the modpack.jar I maintain with the proper changes to include LiteLoader already injected. You can just download the file I linked and use that as your modpack.jar.

Posted

 

  • As for the SmartMoving mod and it's dependencies, you had the original "download" for Render Player that needed to be extracted and it looked like they might have been mismatched versions. I could be mistaken, but it wouldn't hurt to just download them all again from the author's preferred distribution channels and re-extract them.
  • Always get your mods from the author's preferred distribution channels. This will ensure that you have the correct version and that you have the proper installation procedures.
  • Yes, the config files get created when the mods get injected into Forge/MC. Once you have the pack working this whole config folder needs to be included in your pack archive. This ensures that everyone has the same, predictable configs and gives you an opportunity to fix/prevent ID conflicts and to balance mods against each other.

About "modpack.jar":

 

Normally the only thing that should be in your bin folder is modpack.jar. Also, modpack.jar is usually just the Forge universal binary jar renamed to "modpack.jar". However, in your case, since it seemed like you wanted to have LiteLoader, there needs to be some changes made to this (specifically to the version.json file inside the jar). I went ahead and published a link to the modpack.jar I maintain with the proper changes to include LiteLoader already injected. You can just download the file I linked and use that as your modpack.jar.

 

Alright Cool, Well as for the part about getting the mods from the authors channel, I did from what I believe (see above post)

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