Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by plowmanplow

  1. No need for anyone to get salty here. My apologies for not getting back earlier.

    While building the pack, I highly recommend using something like the BareBonesPack in the TechnicLauncher ( https://www.technicpack.net/modpack/barebonespack.271497 ). This will let you start with the base Forge and add/update mods until you get everything the way you want it. Once that is done you can package it up and update/create a full pack in the platform... or you could just play it within BBP.

  2. Was the link to the modpack always in the original post? Wow. I must be slipping.

    Onto your pack:

    • You are using mods from sources other than where the authors distribute them. Don't do that: https://stopmodreposts.org/
    • Most of your mods are out of date, some incredibly so. Why are you making a pack now with a mod that was released nearly a year ago when the latest version is 3 days old?
    • One of your mods is incompatible with OptiFine. That's why I suggested you temporarily remove/disable it. I did that and the pack started right up.

    Update your mods. Use versions from legitimate sources. See if that works. If it does, add OptiFine back in and see if that works. Come back here with more questions.

  3. Hmm.
     

    Quote

    12:18:35] [main/INFO] [Config]: [OptiFine] (Reflector) Class not present: mods.betterfoliage.client.BetterFoliageClien

     

    Maybe something wonky going on with OptiFine. Again, try pulling it. Might be something going on with PotionHelper.

    That being said, I can't do any more testing without the pack details.

  4. Lots of options there:

    • Limiting people to one /home
    • Limiting use of /back to only after death (or similar)
    • ThermalFoundation is awesome for being able to discretely control ore spawning from all mods.
    • So many more :)
  5. Or, you could just play vanilla hardcore SSP. :)

    Joking of course, heh. On a more serious note, some of the "this is hard as hell" stuff like limited ores, no item teleporting, etc. can be quite cool. Removing all flight, /tp, /back, homes, etc.? Not going to get a lot of traction with that. Way too tedious.

  6. Assuming you can upload the modpack archive to a location served by your web server (i.e. in the same place as your static HTML files) you should be able to put a link to that file into the modpack location field in your pack settings.

    For example: If your website is http://www.13madman.com/ , and you put the modpack archive named mymodpack-1.0.zip (just an example) in the same folder on the server where that page is served from, the URL you would use in the pack settings page is http://www.13madman.com/mymodpack-1.0.zip

  7. Orespawn is notorious for not working well when there are a ton of entities from other mods in a pack:

    at net.minecraft.network.packet.Packet24MobSpawn.func_73279_a(SourceFile:87)

    The Orespawn authors also aren't very responsive to bug reports of this nature. Good luck, but this is likely not solvable.

    • Your Bibliocraft and CustomNPCs mods are not from legitimate sources.
    • Why have you included CustomNPCs? None of your other mods require it.
    • Your MicdoodleCore mod has a " (1)" in the filename. This happens when you download a file to a folder that already contains a file with the same name. Fix this file name.
    • Your Mekanism mods are absolutely ancient and have odd file names. Your version is 1.7.10-7.1.1.127 and the current version is 1.7.10-8.1.9.267.
    • You have no config files in your pack.
  8. The pack loads fine for me with all the expected mods. Try removing the pack from your launcher and re-adding it.

    EDIT: The pack crashes when I try to start a SSP world. Looking into that now.

    Edit 2: Removing BetterFps allowed me to start the pack successfully. With so few mods you probably don't need an FPS booster, but if you still want one try ONE of these:

×
×
  • Create New...