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
    In my experience (the servers I run), I seem to be seeing better memory management in general when using Java 8. This is anecdotal in nature so I wouldn't take a strong stance just for that, but there are so many compelling reasons to switch to Java 8, and so few not to, that it just makes good sense at this point. There is always a decent amount of HD I/O going on ranging from "some" to "a crapton" (technical term). The system will run MUCH better on an SSD, especially when lots of folks are generating a lot of chunk churn, and when backups hit.
  2. plowmanplow
    I use my BareBonesPack as the base for building and testing modpacks. You may find it useful. Here is a detailed explanation of how one may build a modpack using BareBonesPack:
  3. plowmanplow
    This is not a corrupted chunk. This is a tile-entity doing bad things here: Block location: World: (-9049,86,-1572) Log into the server, switch to creative mode and break the block/portal at that location.
  4. plowmanplow
    What now? As previously mentioned, you go through every mod in your pack and make sure that: each mod is the latest compatible version each mod is downloaded directly from the mod author's preferred distribution channels For mods that aren't cornerstone, "big name" mods make sure that you take a look at what folks are saying or complaining about. If a mod has a ton of folks complaining about instability or incompatibility with other mods you might want to steer clear. At this point I would normally bring the pack up in my test environment, but there are so many outdated mods with known critical issues in your pack that it's not reasonable to do that at this time.
  5. plowmanplow
    That covers a large part of the low hanging fruit for optimizations. There are more complex options, but since you are currently just admining it might not be helpful. Things like VisualVM, system level performance monitoring, that type deal.
  6. plowmanplow
    I use the VoxelMap minimap for LiteLoader.
  7. plowmanplow
    Use Java 8. Use FastCraft. Make sure you are running off an SSD. Keep your view distance to 6. Play with command line Java options. Google for additional information (not getting into that here). Make sure you are using Opis to keep tabs on what is actually using the most server resources.
  8. plowmanplow
    From my log: This server is running CraftBukkit version git-MCPC-Plus-jenkins-MCPC-Legacy-147-70 (MC: 1.4.7) (Implementing API version 1.4.7-R1.1-SNAPSHOT) Me asking "does TekkitCustomizer work by itself" is another way of me saying "please start the server with TekkitCustomizer the only Bukkit plugin installed and return with your results".
  9. plowmanplow
    @CharZinta: If you create a modpack archive with Forge for 1.7.10 and select MC 1.7.2 in your pack settings the Launcher will get the libraries and minecraft.jar for Forge/MC 1.7.2 and then try patching that with Forge 1.7.10. This results in unexpected classes and structures and throws that exact error. Now, this may not be what OP did, but it is highly likely. We won't know until he either admits that he corrected the version number and the pack works fine, or he posts his API URL and we can examine it ourselves.
  10. plowmanplow
    Many of your mods are woefully out of date. Update all of the mods for which new versions are available. OptiFine often causes issues. Try removing that if the updated version doesn't help. Crash reports are required in order to anything other than guess at the root cause of the issue.
  11. plowmanplow
    This probably belongs in Platform Pagoda. Always provide the API URL or link to the custom modpack page when requesting assistance. Without that there is always a lot of guessing going on, which helps no one. This error is often caused by having the wrong MC version selected in your pack settings.
  12. plowmanplow
    You are going to have a challenging time finding combinations of each mod which will work in the older versions of Forge. Trying to set up a current 1.7.10 pack on Forge #1217 is going to be an exercise in frustration.
  13. plowmanplow
    Please use a pastebin service (like pastebin.com) for log outputs instead of pasting them here in the forums. This post on getting mods may help you: Your TeamCoFH (CoFHCore, Thermal Expansion, etc) are woefully out of date.
  14. plowmanplow
    Your download URL for the modpack archive needs to have "?download=1" (without quotes) appended. The "world holes" could be due to poor PC performance. JourneyMap is known to be very resource intensive. You might try swapping out to a different, lighter minimap mod. For whatever reason, the world generation in your modpack seems to be exceptionally CPU intensive. This could also be causing issue for folks with less powerful computers.
  15. plowmanplow
    Update TiCToolTips to version 1.2.3. (just came out today) Reika (wrongfully, IMHO) includes the Waila API files in his DragonAPI JAR. These are outdated and causing the crash. You can fix this by opening the DragonAPI JAR file and removing the "mcp" folder and its contents.
  16. plowmanplow
    Just because things like this are always caught in search indexes, I wanted to tack on a bit more information. The "correct" way to install LiteLoader for Forge/MC 1.7.10 in a custom modpack implemented through the Technic Launcher is to: Download the LiteLoader installer from the author. Run the JAR and extract the mod to a folder of your choice. Place the extracted jar in your modpack's /mods/1.7.10/ folder. Can you get it working other ways? Yes. However, it is always advisable to deliver everything that your modpack needs inside the modpack archive.
  17. plowmanplow
    You have OpenBlocks mod but not the dependency mod OpenModsLib. You have very outdated versions of: Biomes O' Plenty, Mantle, Chisel, Tinker's Construct. You have Thermal Expansion mod but not the dependency mods CoFHCore and Thermal Foundation.
  18. plowmanplow
    The implication from that error report is that your video card or drivers is not properly supported. I'm able to start a SSP world with your pack, which seems to work find on my system. Make sure your video drivers are as up to date as possible.
  19. plowmanplow
    Your top level folders are not named correctly. They should be all lower case names. Your /bin/modpack.jar is not the correct file/contents. The modpack.jar file is simply the correct version of the Forge universal binary JAR file renamed to modpack.jar. On another note, why are you making a new pack for Forge/MC 1.7.2? Pretty much everything in your pack has a version for 1.7.10 which would be a much better choice.
  20. plowmanplow
    Yes. I would recommend using at least Forge #1240 and preferrably #1272.
  21. plowmanplow
    Correct. You need the Legacy Fixer on Forge for 1.6.4, and 1.7.2 (and maybe 1.6.2, I forget, but who would use that anyway). It's the same version of the JAR for both versions of Forge.
  22. plowmanplow
    Your /bin/ folder should only contain the modpack.jar file. Other than that, the pack starts just fine.
  23. plowmanplow
    You have ChickenBones' mods (CodeChickenCore and NEI) for Forge/MC 1.8. You need to get the latest 1.7.10 versions. You have a 1.6.4 version of MicdoodleCore for Forge/MC 1.6.4 which must be removed. Advanced Machines requires Immibis Core mod. You have IronChests mod for Forge/MC 1.6.4. You need to get the latest version for 1.7.10. It is normally frowned upon to distribute resource packs, especially large ones, with your modpack archive. Those are something that seldom changes and can seriously bloat a pack. For instance, your pack archive is nearly 250M in size. Without all the bloat, it's only 75M, which is much more manageable. Fix these issues and come back if you are still having troubles.
  24. plowmanplow
    It may be the other way around. I'm pretty sure that Reika's mods are not compatible with BuildCraft 6.3.x at the moment. Additionally, Forestry may not be either.
  25. plowmanplow
    @SXScarecrow For versions of LiteLoader past Forge/MC 1.6.4 the LiteLoader JAR file just goes in the /mods/1.7.10/ or /mods/1.7.2/ folder. There is no extra editing or configuration needed.
×
×
  • Create New...