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
    Ahh, I see what is going on. You have the FOLDER that contains the Modpack.zip file as your download URL. When you do that Dropbox is zipping everything up into another archive. You need to get the direct URL for the FILE that is Modpack.zip and use that.
  2. plowmanplow
    Bumping is bad form. Other than re-doing the texture from scratch or talking to the people who made it I couldn't suggest anything else.
  3. plowmanplow
    What are you trying to add to the minecraft.jar file? Keep in mind that the whole point of the Technic Launcher is focused around providing a platform for Forge modpacks. It is possible to do a pack that only modifies the vanilla MC, but you aren't supposed to be distributing the base minecraft.jar file.
  4. plowmanplow
    Use launch.bat.
  5. plowmanplow
    When trying to connect to a server and getting that error in the client, always check Mojang's Status Page. They are currently experiencing issues.
  6. plowmanplow
    Can you be more specific? Tekkit Classic (Forge/MC 1.2.5) is available through the launcher. Do you mean an older version?
  7. plowmanplow
    You have not clearly stated your request. Are you asking someone to make the pack for you or are you asking someone to help debugging the pack you have been working on? When requesting help for a modpack always provide a link to the Technic pack page or API URL along with specific details providing context for the issue like how/when it happens, how reproducible it is, crash reports, FML logs, etc.
  8. plowmanplow
    Keep in mind that development of mods on Forge/MC 1.4.7 ended a long time ago. Maintenance updates for that version ended not too long after that. I'm pretty sure that the TekkitLite pack has been frozen for over a year at this point.
  9. plowmanplow
    Are you using the batch file which came with the server download? The launch.bat file which comes with the server has max/starting values of 3G/2G.
  10. plowmanplow
    There is no range limitation or check. As long as both ends/chunks are loaded it will work.
  11. plowmanplow
    Yep.
  12. plowmanplow
    You should only have added the first one for IC2. The "deobf" and "api" should not be included. You are zipping things up twice. Stop doing that. You have a modpack inside of a ZIP file which is in itself inside of another ZIP file. I already explained this once. You have to remove the old version of IC2 when adding the new one.
  13. plowmanplow
    @Munaus: Too true. Might have been a bit trigger happy there. @carlsoncalvin: Can you be more specific? I am able to launch vanilla MC 1.7.10 as well as a Forge 1.7.10 modpack through the technic launcher without difficulty.
  14. plowmanplow
    The contents of your modpack archive "Public.zip" is just another zip file named "Modpack.zip". The contents of your modpack archive must be the required folders (bin, config, mods) at the top of the folder structure. The contents of the nested Modpack.zip file is mostly correct. Just use that one. If you intend on including IC2 for 1.6.4 you should read this: You have included the Backpacks mod for 1.7.x. You need to get the 1.6.4 version.
  15. plowmanplow
    Problems with the Launcher belong in the Tracker for the Launcher.
  16. plowmanplow
    Not quite sure what you are after. The modpack.jar file is ONLY the Forge universal binary JAR file renamed to modpack.jar. Nothing more, nothing less. If that file exists the Launcher tries to do some very specific things with it. Since your file is broken/malformed/invalid the Launcher/client will blow up. If you want a vanilla client do not include a modpack.jar file at all.
  17. plowmanplow
    @senne010: You do not have the "exact same problem". It is likely quite different in fact. Don't hijack someone else's thread with a new problem. Start a new thread with pertinent details. Provide: Link to Technic pack page or API URL, crash-report, FML client log, etc.
  18. plowmanplow
    Google search for "windows ? always show file extension" where the "?" is your version of windows (i.e. 7, 8, Vista, etc.).
  19. plowmanplow
    You could copy the %APPDATA%.technic folder to your new laptop in the same location.
  20. plowmanplow
    For the block ID conflicts, just go through the list that is created in IDConflicts.txt and change one of the IDs in one of the conflicting mods for each line item in the list. Reference the open list of IDs at the bottom of the file.
  21. plowmanplow
    Dropbox works fine. You just have to share the individual files and append "?dl=1" (without quotes) to the URL provided. copy.com works fine as well. Append "?download=1" to any share URL.
  22. plowmanplow
    In this case, yes, the pack is fundamentally broken. It is fairly easy to fix, but it's not a 1-step process.
  23. plowmanplow
    This likely belongs in the Tracker for the Launcher.
  24. plowmanplow
    Don't include minecraft.jar in your bin folder. It is unnecessary and violates Mojang's TOS. I would strongly recommend updating to Forge 1.6.4_965. You have OpenBlocks mod but not the dependency mod OpenModsLib. You have two copies of Damage Indicators mod in your mods folder. Remove one. You do not have Weather Mod installed properly and is out of date. Download the latest version for 1.6.4 from the author's web site and install it per his instructions. The default generated config files have over 40 block ID conflicts. These must all be resolved. I would normally continue on from this point. However, I don't feel like fixing over 40 block ID conflicts. Fix the pack up to this point and if you have more difficulties just holler.
  25. plowmanplow
    @Olivier: Don't hijack someone else's thread and don't multi-post. I'll respond to you in the thread you started.
×
×
  • Create New...