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
    That is not the whole crash report. You have cut off the useful portion. Don't paste log data here, use a pastebin service. Use that to provide your full crash report.
  2. plowmanplow
    The /fill command was not introduced until Vanilla MC 1.8. Tekkit is currently 1.6.4. Two ways to fill an area is with a BC filler or by using WorldEdit.
  3. plowmanplow
    Directly from the log you provided: [17:49:01] [main/INFO] [FML/]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.6.0_65, running on Mac OS X:x86_64:10.9.5, installed at /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Note that it explicitly shows JDK 1.6 (i.e. Java 6). This won't work. Must be 1.7 (i.e. Java 7) or higher, preferably Java 8.
  4. plowmanplow
    This belongs in Platform Pagoda. Always provide the API URL for the custom modpack for which you are requesting assistance.
  5. plowmanplow
    This might help: http://forums.technicpack.net/topic/103596-still-looking-for-help-building-custom-modpack/#comment-571785
  6. plowmanplow
    Mediafire is not a valid file host for modpack archives in the platform. You should use DropBox or copy.com
  7. plowmanplow
    And always include the API URL or a link to the pack details page when requesting custom modpack assistance.
  8. plowmanplow
    If the built-in Technic packs aren't working then you need to be in Bug Reports for the Launcher. Anything resolved there will likely fix your custom modpacks not working as well.
  9. plowmanplow
    If the built-in Technic packs aren't working then you need to be in Bug Reports for the Launcher. Anything resolved there will likely fix your custom modpacks not working as well.
  10. plowmanplow
    The Minechem source is the file named: Minechem-1.7.10-5.0.5.385.zip You have old versions of mods for 1.7.10. For example: OptiFine 1.7.10_HD_B5 instead of 1.7.10_HD_B7, BiblioCraft 1.7.10_1.9.2 instead of 1.7.10_1.10.4, all your ChickenBones mods (CodeChickenCore, NEI, etc), All your CoFH mods (CoFHCore, ThermalExpansion, ThermalFoundation), BuildCraft 6.4.1 instead of 6.4.18. Chisel instead of Chisel 2 ( http://coloredlightscore.us.to:8080/job/Chisel-2 v1.7.10-Dev/ ) Your crash is caused by one of your mods not being updated for the fluid registry changes that happened in Forge #1355. If you update ALL your mods to their latest versions the crash will likely be fixed.
  11. plowmanplow
    Yes, Millenaire. Years of development and they still haven't figured out how to properly package a mod. Try removing and re-extracting the Millenaire mod. I did that and was able to get your pack working by replacing the modpack archive downloaded by the Launcher. The issue is that the Launcher doesn't like one of the file name characters inside the /mods/millenaire/languages/ folder.
  12. plowmanplow
    As soon as you change one of the Technic packs you have a custom modpack and the thread belongs in the Platform Pagoda forum. Hopefully a patient admin will move this. In order to do a proper diagnosis, we will need the custom modpack API URL or a link to the pack details page. IDFixMinus is intended to be used for helping to resolve ID conflicts during the pack assembly process. It should never be in a published modpack. That requirement is MUCH more critical when the pack will be used for a server. Resolve your conflicts the proper way and eliminate IDFixMinus: http://forums.technicpack.net/topic/64178-hexxit-modification/#comment-519633
  13. plowmanplow
    The /mods/VoxelMods/ folder should not be included in your client modpack. This will overwrite local client settings when the pack updates. You have the Minechem source and API in the mods folder. Both of these should be removed. You have voxelmapNoRadar, but neither VoxelMap.litemod nor LiteLoader on which it depends. Many of your mods are very old, some fatally so (OptiFine for instance). You need to update all your mods to their latest versions.
  14. plowmanplow
    It is generally considered bad form to distribute the options.txt file in a pack because it will overwrite all client settings/options every time the pack is updated. CoFHLib is intended for use only by mod developers and does not belong in a client modpack. That being said, the pack installs and launches successfully on both of my test systems.
  15. plowmanplow
    [B#301] 2015/06/19 17:59:42 [INFO] Could not reserve enough space for 1048576KB object heap You need to increase the memory allocation in the Launcher settings. If you are unable to increase the amount beyond 1G then you need to install 64bit Java. Never allocate more than 4G of RAM or half your physical RAM, whichever is lowest.
  16. plowmanplow
    Something as discreet as particular spells would need to have a built-in mechanism from AM2 in order to restrict them. Since that doesn't exist the best you could possibly do is to restrict casting all spells, maybe using some combination of the plugins TekkitCustomizer, BanItem or the mod DimensionGuard.
  17. plowmanplow
    http://forums.technicpack.net/forum/8-technic-launcher/
  18. plowmanplow
    Yes, it is possible to get Solder running under Windows. No, it is not supported on that platform. On a lark I decided to set it up just to see what happens (some time ago). There are numerous points where things are different from the supported (Linux) platform instructions and without prior experience deploying service level applications on multiple platforms most users will not be successful.
  19. plowmanplow
    How about some context? What's not working? Which custom modpack is this in regards to? What specific behavior are you experiencing? Use a pastebin service. Attachments don't work here.
  20. plowmanplow
    If all packs fail, including the packs provided by the Technic group, you need to post in the Tracker for the Launcher.
  21. plowmanplow
    If all packs are crashing, specifically the packs provide by the Technic group, you need to be in the Tracker for the Launcher.
  22. plowmanplow
    "Forge for 1.7.10 does not use a coremods folder in any way" means that it doesn't use a coremods folder. At all. In any way. Put your mods directly in the /mods/ folder except in cases where they belong in /mods/1.7.10/. In your case, all your mods belong in /mods/. You are not using the latest versions of ChickenBones' mods. I even put "latest" in quotes to indicate you should be using the ones under the "latest" header instead of the ones under the "recommended" header (which don't work in current Forge versions). You have changed your modpack download, but havn't incremented/changed your pack version number. The Launcher is only notified that an update is available when the pack version number changes.
  23. plowmanplow
    Having 100 concurrent players on a single modded MC server is just not going to happen. As has been previously stated, Forge/MC is largely single threaded so scalability is a huge challenge. Even with a view distance of six and everyone working in pairs you would still have 6000+ active chunks. Once people started building up their bases there would be so many active tile entities the TPS would plummet. Roversword has it right with the backups. In my opinion, this is one of the most compelling reasons to use Linux as it is very simple to setup true versioned backups without consuming a ton of disk space (rsync hard links FTW). My largest pack's server, which has been running for 6+ months is nearly 8G in size. Using rsync hard link backups I have hourly backups for 24 hours that only consume just over 9G total.
  24. plowmanplow
    This is why having the API URL is so important: Your pack settings are configured to be a 1.8.3 modpack, but you have mods and Forge for 1.7.10. You need to change your pack settings to 1.7.10.
  25. plowmanplow
    The link you provided is not an API URL. It looks like you linked the same URL twice instead of a crash report and the API URL. Additionally, the log data you are providing is not the crash report. Those are generated in the modpack's crash-reports folder.
×
×
  • Create New...