Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Reputation Activity

  1. Upvote
    plowmanplow got a reaction from wyatttt7 in What Am I Doing Wrong?   
    Your /bin/modpack.jar file is incorrect. The modpack.jar file is the Forge universal binary JAR file renamed to modpack.jar. You have a number of mods with (1), (2), etc. in the file names. This is caused by downloading a file with an existing name to a folder. All the file names need to be fixed by removing the extra space, parenthesis and numbers. Failing to do so can cause issues with mods. You should update to the latest AE2rv2. You have an "installer" for the MC Heli mod in your /mods/ folder. The mod is not distributed this way implying that you obtained that from an illegitimate source. You have duplicate mods in your /mods/ folder: Resonant Engine, Thermal Expansion You have no mods which require Resonant Engine and all 4 of those files should be removed.
  2. Upvote
    plowmanplow got a reaction from MrJayDay in Issues with launching my ModPack   
    You would use the LiteLoader installer to extract the LiteLoader mod JAR. Just run it form the command line: java -jar liteloader-installer.jar (or whatever the file name is) The other Voxel stuff would need to be copied from their modpack. They don't distribute it directly. Thaumic Tinkerer: http://jenkins.nekokittygames.com:8080/job/Thaumic Tinkerer/
  3. Upvote
    plowmanplow got a reaction from MrJayDay in Issues with launching my ModPack   
    bspkrsCore belongs in /mods/1.7.10/ You have AM2 for an older version of Forge/MC. 1.4.0.008 is the current 1.7.10 version. You should be using the latest version of the AE2rv2 Beta. You only have one of the three mods that make up Galacticraft. You need GalacticraftCore, GalacticraftPlanets and MicdoodleCore. You should remove any "(1)" strings from your file names (or parenthesis with any other numerical digits in them). They can cause issues with some mods. You have the LiteLoader installer in your /mods/ folder. The actual LiteLoader mod JAR (not the installer) belongs in the /mods/1.7.10/ folder. Your TeamCoFH mods don't match. Get the latest version of all your chosen TeamCoFH mods from their website. Your Not Enough Items mod is from an illegitimate source. Get the latest version from the author's website. This applies to any of your mods named in the format of "ModName-Mod-1.7.10.jar". You have the Thaumic Exploration for 1.7.2 instead of the required 1.7.10 version. Your Thaumic Tinkerer mod is ancient and not compatible with the current version of Thaumcraft. It should be updated. You have a 1.7.2 version of Twilight Forest. You need the latest 1.7.10 version. This is all simply from browsing the contents of the modpack archive. I made no attempt to start the pack since there are so many fatal issues. Address these and come back here if you have more difficulties.
  4. Upvote
    plowmanplow got a reaction from The_Doctors_Life in Custom Modpack Mac issues   
    The pack seems well constructed and appears to work fine. We would need one of the crash reports from a client that is crashing on world creation in order to proceed.
  5. Upvote
    plowmanplow got a reaction from HenrikoMagnifico in My custom modpack won't open in the Technic Launcher.   
    This thread belongs in Platform Pagoda. Hopefully a forum mod/admin will move it.
    The contents of your modpack archive are in a subfolder. The required folders (bin, config, Flan, mods, shaderpacks) must be at the top level of the folder structure inside the modpack archive. The ZIP library used by the technic launcher does not like the character "§". You will need to remove that character from any file names (in the shaderpacks folder). The shaderpacks folder contains another folder named shaderpacks under which the actual shader ZIP files exist. The ZIP files need to be moved up one folder. Resource packs should not be included in the modpack archive and should always remain zipped (not extracted). The legacyjavafixer mod is not required and should be removed. The NEI mod should be updated to the latest 1.7.10 version available.
  6. Upvote
    plowmanplow got a reaction from CharZinta in COFH Core and Cauldron 1.7.10   
    The current RC versions of CoFH mods have no problems running in Cauldron builds >= #1272. And to answer your next question, no we shall not discuss how or where to obtain them.
  7. Upvote
    plowmanplow got a reaction from Duffa13 in Chunk Loader Issues   
    Looks to be more of an issue related to Ender Storage (another ChickenBones mod):
    java.lang.NullPointerException at codechicken.enderstorage.storage.item.TileEnderChest.reloadStorage(TileEnderChest.java:98) at codechicken.enderstorage.common.TileFrequencyOwner.func_70312_q(TileFrequencyOwner.java:33) The crash report does list a specific location for the ender chest. Possibly something intended to receive the output of a quarry (which loads its own chunks)? You might try removing the quarry and/or chest using MCEdit if the server crashes anytime the chunk is loaded.
  8. Upvote
    plowmanplow got a reaction from EvilOwl in Server pack works on linux, fails on PC   
    I applaud your efforts to provide a consistent, uninterrupted game play experience to your users. That desire will serve you well over time.
     
    As for the updates, as long as you stay within the same version of MC (1.7.10) you'll almost never have an issue. All of the mods I mentioned will update without any impact on world saves which players have created. For things like Thaumcraft and ThaumicTinkerer not matching, this WILL cause your world to crash eventually. The version of TT you have has implemented features that don't work with the version of Thaum you have. If someone attempts to make certain TT items and gets them into their inventory, the client will crash. Same issue with any mods with provide Waila integration. There was a significant API change in Waila after the version you are using which most other mods have included. This will cause issues if you don't update.
  9. Upvote
    plowmanplow got a reaction from The_Doctors_Life in The pack is vanilla instead of forge 1.6.4   
    Your modpack.jar is named "modpack.jar.jar". Google "windows explorer always show file extensions". Your Big Reactors is very out of date (should be 0.3.4A2). Your ComputerCraft is out of date. OptiFine is out of date. Tinker's Construct is out of date. Your CoFH mods are out of date. You have no config files in your pack. This will likely prove fatal.
  10. Upvote
    plowmanplow got a reaction from AetherPirate in [Modpack Help] White textures instead of vanilla textures   
    Well, I did stay at a Holiday Inn Express last night.
  11. Upvote
    plowmanplow got a reaction from Optimus111 in HELP PLEASE!!! MY MODPACK STARTS UP BUT THE MODS DONT LOAD   
    No, you should change your Windows Explorer settings to always show file extensions. Google for "windows explorer always show file extensions".
     
    As for the modpack, nearly all your mods have been downloaded from illegitimate sources. Most of the time if your mod has a name in the format of "mod-name-1.7.10.jar" it is being downloaded from somewhere other than where the author provides. This is always bad. In your case most of your mods are out of date because of that.
  12. Upvote
    plowmanplow got a reaction from LightningZBolt in My own take on a 'Hexxit 2'   
    This post on creating a server from an existing custom modpack may help you:
     
    Client only mods in this pack (as of 20150308 17:15:00EST): (tested with both Forge and Cauldron #1307 servers)
    ArmorStatusHUD DamageIndicators StatusEffectHUD BackTools TiCTooltips WailaHarvestability Mods which should be removed (both client and server):
    LegacyJavaFixer: This mod is not needed with versions of Forge for MC >= 1.7.10 #1230. Making the above modifications allowed me to launch the client and connect to a server for the pack.
  13. Upvote
    plowmanplow got a reaction from CharZinta in Server Crash - Assistance needed   
    Sure enough, that looks like a chunk corruption. You might try using MCEdit to delete/regen the two chunks listed as being wonky. I say this with the utmost sympathy, but there is never any substitute for good backups. If step #1 is getting the server started, step #2 is implement and verify a good backup solution.
  14. Upvote
    plowmanplow got a reaction from The_Doctors_Life in How do I make a mods page?   
    You would need to use the Solder API: https://github.com/TechnicPack/TechnicSolder
  15. Upvote
    plowmanplow got a reaction from CharZinta in Launcher closes after I click play on my private modpack   
    Posting unrelated requests in a thread that is nearly a year old is considered bad form. You do not have "the same problems but with different mods". You have a different problem. In the future, please create a new thread when you require assistance.
    You have the Forge installer as your /bin/modpack.jar. The modpack.jar file should be the correct version of the Forge universal binary JAR file renamed to modpack.jar.
  16. Upvote
    plowmanplow got a reaction from CharZinta in Cache File Not Loading Correctly   
    Shall we play a guessing game for which modpack you might be referring to? I'll vote for this one: http://api.technicpack.net/modpack/journey-of-the-mage
  17. Upvote
    plowmanplow got a reaction from CharZinta in Factorization colossus   
    I can assure you that would not save any time for me.
  18. Upvote
    plowmanplow got a reaction from The_Doctors_Life in What qualifies a modpack for "Trending" page?   
    Think "rate of change". Possibly first or second order derivative. I don't know if they are making it that complex, but in the end it's largely a factor of "how fast are the numbers changing".
  19. Upvote
    plowmanplow reacted to Torezu in Help with creating modpack server for me and my friends.   
    Okay, if that's the latest error log:
    - AnimationAPI is not there, whether you believe you added it or not. 
    - Neither is CustomMobSpawner.
    - Mo' Creatures is outdated (it should be 6.1.0 for latest 1.6.4 version).  The fact that you have 6.0.1 instead when it's not available on Dr Zhark's site tells me you may not have gotten it from the official downloads.
    - EnviroMine is outdated (1.1.89 is the last 1.6.4 version).
    - The LegacyJavaFixer needs to be added, since you're using Java 8 on a 1.6.4 pack - I'm surprised that's not crashing your client, and wouldn't be shocked at all if it's the next error in line after you get the current ones out of the way.
    - The Coros downloads for 1.6.4 include a couple things I don't see: ConfigMod and ModBuild.  I don't know if you need them, to be honest, since I didn't start using Coro's stuff until 1.7.x, but you might want to keep them in mind.
     
    If you want your client to actually update when you change the modpack files, you need to change the version number on the Platform page.
  20. Upvote
    plowmanplow got a reaction from VCastro_Gamer in ERROR EXTRACTING FILE... PLEASE HELP PLIS   
    The Technic Launcher does not like the character "§" in filenames. Rename any files (specifically in the /shaderpacks/ folder) to remove that character.
  21. Upvote
    plowmanplow got a reaction from The_Doctors_Life in My modpack not launching   
    You have two different versions of Not Enough Items installed. You've got the "new" CoFH mods, but haven't updated many other mods which rely on CoFHCore. Mods which you really need to update (not just because of CoFHCore):
    AE2rv2 to beta-8 BigReactors Botania BuildCraft IC2 Nuclear Control Jabba PneumaticCraft RailCraft Tinker's Construct Thaumic Tinkerer (big time) Tinker's Mechworks Twilight Forest
  22. Upvote
    plowmanplow got a reaction from SinisterPixel in So, my pack won't load any mods whatsoever   
    Your /bin/modpack.jar is the wrong file. It should be the correct version of the Forge universal binary JAR renamed to modpack.jar. HEE is not installed correctly. Open the ZIP file and follow the instructions.
  23. Upvote
    plowmanplow got a reaction from AlexPyro in Help Modpack Won't Open   
    You haven't fixed your download URL. You haven't incremented your pack version even though you changed the modpack archive. You are now including too much stuff in your pack archive. It should only contain the folders: bin, config, Flan, mods. The /bin/ folder should only contain the file modpack.jar. You haven't moved the contents of /coremods/ over to /mods. You have a 1.6.4 version of CoFHCore in the /coremods/ folder. CoFHLib is for mod developers only and shouldn't be in a pack. You haven't updated AE2. Your Forestry mod is out of date. You have MFFS but none of the dependency mods which Calclavia requires. You have Numina but not Modular Powersuits, the only mod which uses it. Please address all the points I have made in both posts before continuing.
  24. Upvote
    plowmanplow got a reaction from AlexPyro in Help Modpack Won't Open   
    The only real way is to keep abreast of the change log so you notice when they switch to a new version. That being said, the current version is for 1.7.10. The page I linked is the build server for the developers so always current and up to date.
  25. Upvote
    plowmanplow got a reaction from AlexPyro in Help Modpack Won't Open   
    Copy.com links need to have "?download=1" (without quotes) appended to them in order to function properly. Your pack version is 1.0. Make sure you are incrementing this when you update your modpack archive. Forge for MC 1.7.10 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder. You have only one of the three required mods files for Galacticraft. You need GalacticraftCore, GalacticraftPlanets, and MicdoodleCore You need to get your IC2 build from the developers: http://ic2api.player.to:8080/job/IC2_experimental/ You need to get your ChickenBones mods from the author: http://chickenbones.net/Pages/links.html Your ProjectRed is woefully out of date. REI Minimap crashes with some mods. I recommend a combination of LiteLoader and VoxelMap. You should update to AE2rv2 Fix these issues and come back if you are still having troubles.
×
×
  • Create New...