Search results

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
  1. F

    Problem Server Bat not starting my project Ozone 2 server

    Yes I do, I have JRE 1.8.0_111 64x, i do still have a couple old versions of java for other servers to use, is that any issue?
  2. F

    Problem Server Bat not starting my project Ozone 2 server

    java -Xms2G -Xmx6G -jar forge.jar pause That's my new code line, but the window still doesn't stay open long enough for me to see what the server is doing... sorry if I'm being dumb here but I haven't run into this issue before.
  3. F

    Problem Server Bat not starting my project Ozone 2 server

    So, i have a project ozone server. I have started it from the forge.jar file, let it load all its files, then tried creating a batch file. I've tried making a very complex one, and it failed. I currenty am trying to run a batch file with the following code line. java -Xms2G -Xmx6G -jar...
  4. F

    Problem Internal Server Error on Direwolf20 1.7.10

    someone else thats on the server doesnt have an issue, are you sure it wouldn't be client side?
  5. F

    Problem Internal Server Error on Direwolf20 1.7.10

    im just using a normal iron pickaxe, its happened on most ores I've tried, as well
  6. F

    Problem Internal Server Error on Direwolf20 1.7.10

    i looked through the direwolf20 mod list, and its not on it, so that would be a no
  7. F

    Problem Internal Server Error on Direwolf20 1.7.10

    i have two codes here, ones a link that i copied and pasted from my search bar, which is this: http://pastebin.com/Hj9wer28 and this is the embed code <script src="http://pastebin.com/embed_js.php?i=Hj9wer28"></script>
  8. F

    Problem Internal Server Error on Direwolf20 1.7.10

    I'm using McProHosting to host my server, my only issue is when i break a block these errors pop up: Server thread/ERROR [FML]: Exception caught during firing event net.minecraftforge.event.world.BlockEvent$BreakEvent@5e1e6332: and then a little farther down the line, this: Server thread/WARN...