Jump to content

JaariAtmc

Ascended
  • Posts

    3045
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by JaariAtmc

  1. What I think you are doing (used Attack of the Bteam for my example): You zip the folders first, after that, you put these folders in another zip, which makes it look like this inside the new zip file. What you should be doing: Select these 3 folders, then zip them into one zip folder, which looks like this on the inside.
  2. Please upload the contents of that crashreport to www.pastebin.com, as we cannot view attachments on here
  3. Open the big map, default key is M (this conflicts with another key, change that in your controls).
  4. The name of the world, does it have a dot in it?
  5. Remove that one, it is a clientside only mod (means the server will crash if left in).
  6. So you zipped the config/mods/bin folders seperately, then zipped the zipped folders? Just select bin/config/mods, then make one zip out of those three unzipped folders.
  7. And the URL for your technic modpack page? Like, what is your modpack's name? Also, kick out LegacyJavaFixer, unless you are using a version of Forge before 1291 (which also means you should consider upgrading to a much later version of Forge...).
  8. Check your controls for conflicting controls.
  9. Try adding this: http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2387300-say-no-to-id-conflicts-install-anti-id-conflict Also, the thing I'd need from that error is just outside the screen (Its a conflicting Enchantment ID).
  10. Mind pointing me to where you put JAS? I cannot seem to locate it in your modpack folder. Also, have you tried CMS? Its so great and stuff, that you don't want anything else, and I totally didn't read that last line there!!!
  11. Correct IP stated in server.properties?
  12. Go into the mods folder, remove the LegacyJavaFixer-1.0 mod. The person maintaining the pack has updated Forge to the version which has the fix built in, but forgot to remove the mod from the list (this results in the insane console spam).
  13. Because on other servers, you do not have said issue with the garage doors bugging out. It is not on your side, it is on the serverside.
  14. Please provide us with an API url for the launcher so we can check.
  15. That is because all your required folders are in a sub folder, and you included way too much junk. You need to zip the bin/config/mods folders, you can leave out all other folders. Don't zip the actual modpack folder, as that will put the bin/config/mods folders inside a modpack folder inside the modpack.zip (the subfolder) and makes it load without mods or forge.
  16. Garage door crash, this has likely been fixed in Carpenters blocks 3.3.8 (Legends running 3.3.7). So either request the staff of your server to remove the garage doors or wait and hope the Technic team updates Legends soon so it includes this fix.
  17. I was not able to locate that modpack, you got a page like this?
  18. Give the name of the modpack, we can look for it ourselves then.
  19. I'll need a link to the modpack on the launcher then (as in the API url), so I can check the issue myself.
  20. The Rolling Machine requires 50 RF/t to produce rails. A redstone engine should provide the machine with 10 RF/t, so you need 5 redstone engines for it to work.
  21. Change dl=0 to dl=1 and try again.
  22. No. NO. JUST NO. SERIOUSLY NO. NO NO NO NO NO NO NO. Really just NOPE. NOPE. Nope. NEVER, EVER, allocate 15 GB of RAM. NEVER. After you drop it back down to 3-4 GB, try again. You just starved your system of RAM, because if you allocate 15 GB of RAM, it will allocate all of it to the java process, not just increases if necessary. This means that if your system needs to do anything else, like you opening a browser, or a folder, you will be presented with said error.
×
×
  • Create New...