Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Community Answers

  1. plowmanplow's post in Mods not Loading in Custom ModPack was marked as the answer   
    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.
  2. plowmanplow's post in Custom Modpack Server Crashes was marked as the answer   
    At first glance it looks like you are missing the MCPC+ libraries. Some time recently MCPC+ stopped properly retrieving its library files. Download this file and extract it into your server folder:
     
    https://copy.com/qLsTvZfUUkkb
     
    Also, if you are using IC2 Experimental you probably want the recipe fix mod someone cooked up to fix some of the in-game recipes display. You can get that here:
  3. plowmanplow's post in Server crash help was marked as the answer   
    Comments on your client pack:
    You have Forge build #953. Build #965 is the latest. You should update that. You have HardcoreEnderExpansion (HEE) installed improperly. Open your HEE.zip for details. You have old versions of a number of mods. I recommend updating them. Comments (guesses since you did not provide a server archive/pack link) from the crash report:
    You seem to have a number of client only mods showing up in that crash report: ArmorStatusHUD, DirectionHUD, StatusEffectHUD, DamageIndicators, ZanMinimap. All client only mods must be removed in a server install.
  4. plowmanplow's post in Help with server crash please was marked as the answer   
    It seems that either through a mistake or intent MCPC+ is not currently retrieving its libraries properly. Supposedly this link has them: http://www.mediafire.com/download/n28pp7r4kt0e1bd/MCPCPlus_Libraries.zip
  5. plowmanplow's post in Custom Modpack won't launch. was marked as the answer   
    You are including extraneous/unneeded/unwanted files in your "bin" folder. That folder should only contain "modpack.jar". In the top level of your pack (because you have Flan's mod) you should only see folders for: bin, config, Flan, mods and resourcepacks (since you are including one) You are including ICBM API. Remove it. You have NEI installed but have not included CodeChickenCore which is required for that mod. You have included NEI but none of the addons for NEI. You probably want to add them. You have old versions of mods. For instance. Your version of NEI won't work with the latest version of CodeChickenCore. Your Calclavia mods (UE, CalclaviaCore, ICBM) don't worth with each other. Check Calclavia's info to figure out which ones do. Couldn't finish debugging, but that's a good start. Gotta roll!
  6. plowmanplow's post in 1.2.8d Tekkit server crash was marked as the answer   
    Check the top pinned post in the platform pagoda forum. Basically, you need to update to MCPC+ Build #251.
  7. plowmanplow's post in I am not understanding Why isint it working? (Custom Modpack)i was marked as the answer   
    7Zip is a program capable of working with multiple different archive formats. It is important that you always select ZIP format (not 7z, rar, etc.) when making archives intended for use by the platform.
     
    Also, glad it's working for you!
  8. plowmanplow's post in My modpack for 1.6.4 doesn't work was marked as the answer   
    The only thing that belongs in bin is Forge as modpack.jar. Any more debugging will require your pack link.
  9. plowmanplow's post in Tekkit Server Crash was marked as the answer   
    Not necessarily. Your world may be fine, but your DimDoors/PocketDims do seem corrupted.
     
    Make a backup of your world data as it currently stands. Then try removing the DimDoor/PocketDIm data and see if you can get started. Just delete (or rename) the DimensionalDoors folder in your world folder an try starting the server again. You will of course lose anything in any pocket dims, but that might be better than nothing.
  10. plowmanplow's post in My Modpack is Broken! was marked as the answer   
    Your modpack.jar file is a RAR archive format file. All files intended for use by the launcher/platform must be in ZIP archive format. Your modpack.jar file is HUGE. Unless you really need to add mods directly into the file (almost never) you just need to get the correct Forge universal file and rename it to "modpack.jar". You have no config files in your pack. Always, always include config files. It is nearly impossible to guarantee you won't have item conflicts, that you won't have mod interaction problems, and that configs are consistent between players in SMP and SSP without including configs.
  11. plowmanplow's post in Failed to download modpack was marked as the answer   
    Your modpack.zip is actually a RAR format archive even though it has a .ZIP extension. All archives you wish to have Forge/MC/Java use must be in ZIP format. Your modpack.jar file is not the size I would expect. If it work, then great. Just something I noticed. You have some item ID conflicts. Specifically between Factorization's battery and something from CalclaviaCore. Other than that it seems to start and run.
  12. plowmanplow's post in Client Crash was marked as the answer   
    You should have exactly one file in your "bin" directory: modpack.jar You have a ton of other stuff in the top level of your archive that doesn't need to be there: cache, customnpcs, hats, jarmods, log files, IDConflicts.txt You are using an amazingly old version of Galacticraft with known bugs and crashing problems. Your problem with Resonant Induction is actually that you are using a number of Calclavia mods of widly varying versions. This won't work. They all rely on CalclaviaCore so you need to make sure you are using the correct version of the mods for the correct version of the core. Getting the latest versions of the mods worked, but you may need to resolve an ID conflict inside ICBM after upgrading that mod. Atomic Science is also very old. Mekanism is old. The newer version fixes many lag/crash bugs from the version you currently have. If you are including NEI and plugins while also including Mystcraft it would probably make sense to also include the Mystcraft NEI plugin. Fixing the things I mentioned above allowed the pack to start properly.
  13. plowmanplow's post in Failed to download my custom pack was marked as the answer   
    Your modpack link in your pack is not a "direct" download. It must be so in order for the launcher to recognize it. You have mods in the "coremods" folder. Forge/MC 1.6.4 does not use a coremods folder. Everything goes in "mods". Many (very many) of your mods seem like they are out of date. Might load into 1.6.4, but definitely newer versions exist. You aren't including any config files in your pack. In a pack with this many mods, that is most likely fatal.
  14. plowmanplow's post in Modpack crashes immediately was marked as the answer   
    This line in the error log:
    java.lang.NoClassDefFoundError: clashsoft/cslib/minecraft/CustomPotion implies that you are missing Clashsoft's Brewing API library. Is this it? http://www.minecraftforum.net/topic/1895107-164sspsmpapiforge-brewing-api/
  15. plowmanplow's post in How can I test my pack before uploading? was marked as the answer   
    1) Add this modpack to your launcher: http://www.technicpack.net/modpack/details/barebonespack.271497
    2) Change settings of the pack and select your Forge/MC version
    3) Start the pack
    4) Stop the client.
     
    You now have a "bare" forge install where you can add your own mods and configs. When you are done, just copy out the "config", "mods" and "bin" folders but MAKE SURE you delete everything from your copied "bin" folder except "modpack.jar".
     
    You are now ready to zip up your pack.
×
×
  • Create New...