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
    My recommendation is to NEVER let java update itself. It seldom picks the correct platforms/versions/whatever. If you are notified of an available update simply uninstall Java and then install the latest/best version for your platform.
  2. plowmanplow
    Why did you make a new post about this after I had already answered you in your previously created thread? '?do=embed' frameborder='0' data-embedContent>> Don't create multiple threads for the same problem.
  3. plowmanplow
    Your bin folder should ONLY contain the folders: bin, config, mods. One does not typically include a resource pack in the archive as it considerably increases the size and some people can't use them. The bin folder should only contain the modpack.jar file. All other files should be removed. Your modpack is set to be a 1.7.2 pack, but you have Forge 1.6.4 as your modpack.jar file. Your Forge Multipart jar has "(1)" in the filename. That should be fixed/removed.
  4. plowmanplow
    You seem to have an extremely high number of actively ticking entities. What command line are you using to start the server? How much memory does the system have? Is there anything else on the system which would be consuming CPU or RAM resources?
  5. plowmanplow
    java.lang.OutOfMemoryError This error says you are running out of memory in the client. Your current allocation is set to 1G or RAM and you are running 32bit Java. For large packs like this you need to make sure you are running 64bit Java (Java 7 64bit JRE u60 as of this post) on your 64bit OS and allocate more RAM in the launcher. If you only have a 32bit OS then you are out of luck. Also, don't start multiple threads for the same issue.
  6. plowmanplow
    Your modpack.jar file is actually named "modpack.jar.jar". Do a Google search for "windows always show file extensions" to help prevent this in the future. You have no config files in your pack. This is always bad and often fatal, especially with a pack of this size.
  7. plowmanplow
    There are no circumstances I can imagine where you would need to allocate 16G in the launcher. Most packs works perfectly with 2G and large, complicated packs with full HD texture packs will not require more than 4G. Allocating more RAM in the launcher than is required will hinder the performance of your client and your OS.
  8. plowmanplow
    Requests related to the Launcher belong in its tracker: http://forums.technicpack.net/tracker/project-1-technic-launcher/ In this case I suspect you are trying to log into the Launcher with your Technic account credentials. You log into the Launcher with your premium Minecraft/Mojang account credentials.
  9. plowmanplow
    Your modpack.jar file should be in a subfolder named "bin".
  10. plowmanplow
    Change what you want in a modpack while testing it locally until you are satisfied with the results. Package up modpack using the proper format and structure. Upload modpack archive to file hosting service which provides direct download URLs. Change Technic pack settings to point at the new URL and increment your pack version number.
  11. plowmanplow
    Check your forge logs (in the logs folder) around where the crash happened. That log will often provide more relevant information about the cause of the crash or what was going on when it happened.
  12. plowmanplow
    I just updated the file downloaded with that link (same URL) to include the newer required libraries for Cauldron. You really should be using Cauldron instead of MCPC+ in almost all circumstances.
  13. plowmanplow
    You mentioned that you intended to try Java 7. Your most recent log shows that you are still using Java 8.
  14. plowmanplow
    In this case it would be sufficient to simply delete that file as it will get recreated when you start the pack.
  15. plowmanplow
    When requesting assistance for a custom modpack one should always include a link to the Technic pack page or API URL. In the absence of that, and without any logs/errors/crash-reports/etc., we will be unable to help you.
  16. plowmanplow
    Your modpack contents are in a subfolder. All of the required folders (bin, config, mods) must be in the top level of the folder structure inside your modpack archive. You have zipped up the entire contents of your client folder as your modpack archive. Your archive should ONLY contain these folders: bin, config, Flan, mods. Plese note that the Flan folder should have a capital "F" at the beginning, not lower case. Your bin folder should only contain "modpack.jar" which is the Forge universal binary JAR file renamed to be "modpack.jar". Your Forge version is out of date. You should upate to Forge for 1.6.4 #965. (see previous bullet point) As you have it packaged, your modpack is over 360 megabytes in size. Packaged correctly, the modpack is less than 20 megabytes.
  17. plowmanplow
    Your modpack settings for your pack have your Minecraft version set to 1.7.9 instead of 1.6.4. As for the pack, why would you fix the first and second points, but not the final one about item IDs. You have enough of them that large portions of your pack will be unusable unless they are resolved.
  18. plowmanplow
    It sounds like you may be having some odd Java problems possibly. That's the only explanation I can think of that fits all the symptoms. You could try removing all Java related entries in your Control Panel -> Programs/Uninstall and reinstalling the latest Java 7 64bit JRE or JDK.
  19. plowmanplow
    I'll just put the installation process here because it is quite involved: Install B-Team server to a folder. We will refer to that folder as SERVER. Install Cauldron to SERVER. Hmm, guess we are done after only two steps. A couple items of note: You are using Java 8. This may or may not cause issues. You are using ClearLagg with Cauldron. This may or may not cause issues. If you think the problem is coming from Cauldron (and not a plugin) then you may have better luck following up with the Cauldron author(s).
  20. plowmanplow
    Your bin folder has the correct file, but it is named incorrectly. The "forge-1.6.4-9.11.1.965-universal (1).jar" file should be named "modpack.jar". You have a LiteLoader map mod for 1.7.10. Since you have neither of those you will need to remove that mod. You have NetherOres but not the dependency mod PowerCrystalsCore. Your Optifine is out of date. Get the latest 1.6.4 version. You have many mods which are for Forge/MC 1.7.2 and 1.7.10. You need to make sure you are getting the correct 1.6.4 versions. You might benefit from this:
  21. plowmanplow
    @crisapsi: Did you not read the thread. You have asked the same question as the OP and I answered it directly in the second post.
  22. plowmanplow
    @NarutoSasukeRasen: Please don't suggest that folks use mediafire. That host is not a viable direct-download host.
  23. plowmanplow
    You need Cauldron (former known as MCPC+): http://cauldron.minecraftforge.net/
  24. plowmanplow
    Once you use the installer once you can update the server jar by itself (although there shouldn't be any more 1.6.4 builds after the current one). Cauldron (I believe) requires an additional library or two over the base Forge.
  25. plowmanplow
    Your folder names are wrong. You have the first letter of each of the required folders capitalized. They need to be all lower case. You need to update to Forge #965. You have item ID conflicts between: aodb & AdvancedGenetics, aodb & TwilightForest, TwilightForest & AdvancedGenetics, MineFactoryReloaded & Tinker's Mechworks, Fossil & Forestry Fix these and come back if there are more problems.
×
×
  • Create New...