Jump to content

plowmanplow

Discord Moderator
 View Profile  See their activity

  • Posts

    4594

  • Joined

  • Last visited

  • Days Won

    74

 Content Type 

Everything posted by plowmanplow

  1. plowmanplow
    From the front page: http://www.technicpack.net/article/view/concurrentmodificationexception-in-java-18020.89
  2. plowmanplow
    You should probably be using Forge 1.7.10 #1240. You should not be including binminecraft.jar in your modpack archive. Not including config files is always bad, and especially so when you have so many mods. This applies even to 1.7.10 modpacks. You should not be including CoFHLib in your mods folder. It does not belong in a client modpack. Most people who include Mekanism also include MekanismGenerators. Just a suggestion. You have a number of ChickenBones' mods, but not the dependency mod CodeChickenCore. One of your mods seems to be including the old BuildCraft API and causing a conflict with the latest BuildCraft: [15:26:29] [Client thread/ERROR]: Caught exception from BuildCraft|Energy java.lang.NoSuchMethodError: buildcraft.api.recipes.IRefineryRecipeManager.addRecipe(Ljava/lang/String;Lnet/minecraftforge/fluids/FluidStack;Lnet/minecraftforge/fluids/FluidStack;II)V I stopped messing with it at this point. After disabled a number of mods it was still complaining about the BC pipe API. You need to assemble this pack in the traditional fashion. Build it methodically, adding in a few/related mods at once until it fails and you'll know where the problem is coming from.
  3. plowmanplow
    It is generally considered bad form to post in a thread that is 16 months dead. This is termed "necroposting", from the term necromancy relating to the reanimation of the dead. The reason for it is that the issues are usually so old that positions have changed and the dialog is now different. In this case, MANY more mod devs are much more open about the use of their mods than they were back when this thread was active, and there is little contention between the Technic group and the FTB group. Necroposting just dredges up old news that is no longer relevant.
  4. plowmanplow
    You are missing the top level "Chocolate" folder in your server. This must be on both the server and the client.
  5. plowmanplow
    Tekkit Lite (like all modpacks) use a specific version of Forge/MC for mods, each of which requires that specific version of Forge/MC. Tekkit Lite is built for Forge/MC 1.4.7. This cannot be changed and must be the same on both client and server. This is why the Technic group provides both the client and the server for Tekkit Lite. In order to use the Tekkit Lite client, you must download and run the "Tekkit Lite" server, not the "Tekkit" server, which is built for Forge/MC 1.6.4.
  6. plowmanplow
    Once a chunk is loaded and changed (which the vanilla server JAR will do to chunks with mod items/blocks) there is no way to restore it except by using a backup of the world. Without good backups you are 100% out of luck.
  7. plowmanplow
    Yes, that's exactly it. I'm here to persecute you by calling you names, belittling your contributions... oh, wait. I didn't do that at all. I simply provided information which enhances that which you had previously provided. In all seriousness, I in no way intended for this to be received negatively. I do a ton of custom modpack support here and having the most accurate information possible is of the utmost importance. This thread should now show up with that information in an easily consumed format if someone searches for dropbox information, and for that I thank you.
  8. plowmanplow
    Always use a pastebin service ( http://pastebin.com or http://paste.ubuntu.com/ ) for long files like this. Always provide the API URL (the URL you paste into the launcher to add the pack) when requesting help for a custom modpack.
  9. plowmanplow
    I am quite willing to continue debugging things here. Are you able to update the pack settings with the new/updated modpack archive/URL? If not you may need to make another modpack altogether and we can start from there.
  10. plowmanplow
    Maybe try using MCEdit?
  11. plowmanplow
    The reason it worked (kinda, sorta) in Windows is that Windows is not case sensative in its filenames. The "Modpack.jar" file (with the upper case M) will break the pack on anything but Windows. Of course, all the other problems still need attention regardless of platform.
  12. plowmanplow
    Cauldron builds are no longer available to to DMCA claims.
  13. plowmanplow
    Your pack works fine when added to my Launcher. However, I noticed in your pack settings that the version number is still 1.0. Every time you update your modpack archive you must also increment the version number or the client will never know about the update. I suspect you have not done this. Try updating the version number to 1.1 (or 2.0 or whatever).
  14. plowmanplow
    There has likely been no response to the OP since this likely belongs in the Tracker and it often becomes tiring to continually repeat this.
  15. plowmanplow
    I should have said this in my first post (wish I didn't have to say it at all), but you must provide the API URL for your custom modpack when requesting help. This is the URL you paste into the Launcher when adding the pack. Please provide this URL. Since the pack works in my test environment, I'm going to assume that some local configuration is causing the issue. What version of Java (version and bit length) are you using? What specific version of Windows (Vista 32bit, Windows 7 64bit, Windows 8.1 64bit, etc.)? How much RAM does your PC have?
  16. plowmanplow
    Better Dungeons is not installed correctly. Open the ZIP file and follow the mod author's instructions. You have included (again, improperly installed) Millenaire v0.6.4 which is for Minecraft Beta 1.6.4. Millenaire v5.1.11 is for Minecraft Release 1.6.4. You must make sure to re-add the updated config folder (which includes configs for the new mods) in your new modpack archive. All that being said, I've re-built the pack with the changes. Millenaire is a PITA to deal with because of the way the author publishes the mod. For whatever reason, the files in the mod's folders often cause problems for the ZIP library embedded in the Technic Launcher which causes pack extraction to fail if not done just right. https://copy.com/VWRPUA8xlPLaYA2I?download=1
  17. plowmanplow
    03.12 16:41:15 [Server] INFO java.lang.NoClassDefFoundError: net/minecraft/client/renderer/entity/Render You have a client-only mod in your server mods folder, or a mod which "should" work in SMP but does not due to lousy coding. I'm assuming this is a custom modpack server of some sort? Please provide the API URL for your custom modpack if so.
  18. plowmanplow
    Your pack settings are configured to be MC 1.6.4, but your Forge (modpack.jar) and mods seem to be for Forge/MC 1.2.5... well, mostly. Your bin folder should only contain the modpack.jar file. It looks like you have dropped a 1.6.4 version of denLib and QuarryPlus into a 1.2.5 modpack. This will never work. There are modern 1.7.10 versions for just about everything in that pack. Someone else has already made a 1.6.4 (or maybe 1.7.10) version of the original Tekkit Classic (which you seem to be starting from) which you could modify to your needs. Making a 1.2.5 modpack at this point is an exercise in frustration.
  19. plowmanplow
    A challenge is that GP was taken over by a new dev (group?) for a while but is now back under the original management. I'm using the GriefPrevention Build #277 on my 1.6.4 servers and it is working just fine (as expected). I am fairly sure this is one of the "interim group" builds. If you are having trouble finding that version I can send you a link. Grief Prevention #277: https://copy.com/DusdR1wVHiqWencb?download=1
  20. plowmanplow
    Don't use Java 8. Use the latest Java 7 for your platform.
  21. plowmanplow
    Your modpack archive should contain three top level folders (unless you've added a mod which requires its own top level folder): bin - Contains ONLY the modpack.jar file config - Contains all the config files mods - Contains the mods for the pack Any time you are requesting help for a custom modpack you should provide the API URL. This will allow us to diagnose problems with the pack settings. In your case it seems like you might have the incorrect MC version selected in your pack settings. This is just a guess without having the API URL.
  22. plowmanplow
    The pack needs significant work: All folders other than bin, config and mods should not be in the pack, as well as the megabytes of logs from a previous version of Forge/MC. The modpack.jar file in the bin folder is actually named "Modpack.jar". This is bad and should be fixed (needs to be all lower case). Forge/MC for 1.7.10 does not use a coremods folder in any way. All mods go in or below the mods folder. I believe there are mismatched mods in the pack. For instance, I think the AE2 and ExtraCells mods are not correctly matched. The EE3 mod has an odd name with no version number. The implication here is that the mod was not obtained from the mod author. This is always bad. There are many other included mods with the same problem. The Flan's mod installer is in the mods folder instead of the actual mod. Many of the mods are painfully out of date (such as Mekanism), as well as Forge itself (the modpack.jar file). There are no config files included in the pack. This is always bad. I'm surprised the pack even starts for anyone. It needs some serious work. The problems listed above do not address integration issues between mods. It is messed up enough that I did not try to start it.
  23. plowmanplow
    It looks like you have not incremented the version number in your pack settings page. This must be incremented in order for the client to recognize that a new version is available. You probably want at least the Mekanism Generators mod to go along with Mekanism (same download location). Your Carpenter's Blocks mod is oddly named and woefully out of date. The implication is that you didn't get it from the author. His site is here: http://www.carpentersblocks.com/downloads.html Minechem mod is incorrectly including the CoFH API which is causing an incompatibility with Mekanism. If you add the most recent CoFHCore mod this will fix your most significant crash.
  24. plowmanplow
    Since the Cauldron installers (in theory) no longer properly retrieve their libraries, this might all be a moot point.
  25. plowmanplow
    Note: this likely belongs in Platform Pagoda Your bin folder contains everything you dont need and not the file you actually need. The bin folder should only contain the modpack.jar file. This file is simply the correct version of the Forge universal binary JAR renamed to "modpack.jar". You should not be including "PlayerAPI-src-1.7.10-1.0.zip" in your mods folder.
×
×
  • Create New...