Jump to content

JaariAtmc

Ascended
  • Posts

    3052
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by JaariAtmc

  1. Probably ran out of RAM because you are allocating TOO MUCH RAM.
  2. org.lwjgl.LWJGLException: Pixel format not accelerated Location's fine, this IS getting lame.
  3. Server file works the same as the client modpack, just leave out any clientside-only mods. Look over at Apex if Forge is required to run (probably not).
  4. Serverside Chunkloader mod related.
  5. Yes, do not use Java 9.
  6. I keep on wondering why we bother with these: " [B#353] org.lwjgl.LWJGLException: Pixel format not accelerated"
  7. Probably Java Options. Best head to the Discord server for that. Read the #rules then go to #tech-help.
  8. Oh, they do, but the loss of the conductive pipes is too great for the output of redstone engines.
  9. Yes, there are multiple mods conflicting. Especially the ones that are Modname-Mod-MCversion. Because those are from bad sites. Just download the mods from sources like Curseforge, minecraftforum.net (not minecraft-forum, that's an imposter) or the modmakers. own site, like http://www.bibliocraftmod.com/ How about changing those mods (Bibliocraft, BigReactors, Carpenterblocks, Custommobspawners, Dimstorage, Draconic Evolution, Ender Compass, IC2). Also, why do you have IChunUtil for MC 1.12 and Optifine running on your server?
  10. "ATM3"
  11. Link is broken?
  12. Please add the following file: C:\Users\Fernandez-Greene\AppData\Roaming\.technic\modpacks\attack-of-the-bteam\hs_err_pid5128.log
  13. Search for " org.lwjgl.LWJGLException: Pixel format not accelerated" on this forum.
  14. Yup, this is the reason that villages were disabled. Just delete the village.dat in the world folder. You'll have to either disable new village generation, or something not really tested: add a z to the biomesoplenty mod name (biomesoplenty-universal-1.6.4-1.2.1.434 to zbiomesoplenty-universal-1.6.4-1.2.1.434)
  15. Hmm, turned on villages per chance?
  16. Are you certain that it is the whole log? There's nothing about a crash in there. Please add the techniclauncher_2017-(recent date here) found in .technic/logs. If too big for pastebin, try paste.ubuntu.com instead.
  17. That's because you did not try hard enough, nor told us what you did, nor gave us a log to see for ourselves what you did.
  18. The person that made this modpack did not include legacyjavafixer. Therefore, it will crash. Get the mod from a modpack like Attack of the Bteam (just copypaste it from the mods folder) and add it to the mods folder of magicraft 2.
  19. Care to upload the fml-client-latest log instead of the latest.log? latest.log doesn't give enough information for this issue.
  20. Like uh, zip it and use WeTransfer for example?
  21. This particular error is usually a disguised Out.of.Memory error. Considering you are running 64-bit java, please look if it still crashes with, say, 2 GB of RAM, instead of your current 1 GB.
  22. [main/INFO] [FML/]: Forge Mod Loader version 7.10.114.1388 for Minecraft 1.7.10 loading [FML/]: The mod aobd (Another One Bites The Dust) requires mod versions [Forge@[10.13.4.1448,)] to be available
  23. Hoo boy, that's going to be an issue. Easiest way to fix this should just be using NBTexploror on your player.dat file and then changing the coordinates.
  24. Because he is on a cracked version, we won't even bother to look into the issue. Either he gets a real account, or he (and you in extension) can sod off.
×
×
  • Create New...