Jump to content

JaariAtmc

Ascended
  • Posts

    3052
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by JaariAtmc

  1. I was not able to locate that modpack, you got a page like this?
  2. Give the name of the modpack, we can look for it ourselves then.
  3. I'll need a link to the modpack on the launcher then (as in the API url), so I can check the issue myself.
  4. 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.
  5. Change dl=0 to dl=1 and try again.
  6. 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.
  7. Hint: Google for "Dimension ID conflict resolving"
  8. JAMI was never updated to 1.7.10. If you saw it somewhere advertised as 1.7.10, that is likely false advertising on such sites to get more clicks. Edit: After removing JAMI, the ID conflicts start. You have Biome ID conflicts, Enchantment ID conflicts and Potion ID conflicts. Good luck.
  9. Well, it's really quite easy, your game is running out of available RAM while starting, and that is fixed by allocating more RAM. In case you cannot allocate more RAM, you would need to install Java8 64-bit, which can be downloaded here. Restart your launcher after installing, and allocate 2-3 GB.
  10. Send the one with from yesterday (as in June 5th), as the one you sent was from May 30th.
  11. Are you sure it is a good idea to combine BetterFPS and Fastcraft?
  12. This log shows that you were able to succesfully launch the modpack, but that it either kicked you, or you left, while trying to join a server.
  13. And then you upgraded to Windows 10. Welcome to Windows 10. Downgrade your java to java8u25.
  14. The mod "ThaumcraftGates" requires Buildcraft|transport, but Buildcraft|transport requires Buildcraft|core. So if you were not planning on using Buildcraft in your pack, just drop ThaumcraftGates. Also, a few more legit mods to spruce up your pack: Thaumcarpentry Pam's Desertcraft Pam's Bonecraft Dragon Mounts MrCrayfish Furniture Also, ran the pack without ThaumcraftGates, your pack requires DummyCore.
  15. No logs provided. No help to be given, as we don't know what is causing your issue. Log can be found in %appdata%\roaming\.technic\logs\ Open the log file, copy the contents and paste it here, then give us the link.
  16. Yes. Very easy fix. Like incredibly easy. If you would post it under Tekkit Bug Reports that is. And even then a quick google would get you all the answers you need on that.
  17. A quick lookaround on the net shows that this is a BigReactors related error. Did you do anything "weird" to your reactor? Like using multiple fluids as coolant?
  18. Multiple cases of said error, just use the TileEntity removing now.
  19. Corrupted TileEntity which is located at: Block type: ID #701 (tile.thermalfoundation.fluid.glowstone // cofh.thermalfoundation.fluid.BlockFluidGlowstone) Block data value: 0 / 0x0 / 0b0000 Block location: World: (-956,145,-1023) You could try removing it with MCEdit. You could also go to the config folder, look for the "forge" config, and turn "# Set this to true to remove any TileEntity that throws an error in its update method instead of closing the server and reporting a crash log. BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES. B:removeErroringTileEntities=false" " to true. This will remove the Erroring fluid glowstone on startup. Mind to make a backup of your savefile, in case something else corrupts, as this is a very hacky way to resolve your issue. Remind yourself to turn it back to false after removing the above issue.
  20. Intel HD Graphics? Java version (don't you dare say latest, I want a "java#u##)?
  21. I do not have said mudpack unzipping issue, but I do see a small error, your modpack.jar is actually called modpack.jar.jar now. Remove the .jar from the name, and it should load Forge just fine.
  22. First, why are you using optifine if you have such a good computer? Second, why are you allocating so much RAM? That garbage collecting is going to cause quite a bit of lag. You should not need more than 3-4 GB of RAM allocated to your game, and more actually hurts your performance.
  23. Go into the config folder, look for SuperHeroesUnlimited, open said txt file, look for biomes, change Mars Biome ID to 153 and you should be good to go.
  24. Because Intel HD graphics drivers, especially the older ones, are not supported on Win10. Which results in an OpenGL crash, barring you from playing minecraft. Minecraft itself uses Java8u25, so we tell people to use that instead. This allows for playing in 99.5% of the cases.
  25. First, to start off, what is the name of your modpack? If it is Forsaken Borders, please confirm. If it is, you also have a few minor other issues. Like mod jars being empty.
×
×
  • Create New...