Jump to content

SinQ882

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by SinQ882

  1. No worry's, i'm glad i can start the server. Such a small think to overlook when you're not into commands. Thanks again!
  2. Thank you so much! Using cd in the terminal I've managed to start the server. Is there a way to quickly set the terminal to the same folder so I don't have to use 'cd' every time I'm starting the server? Anyway, thanks a lot!
  3. Hi guys! I have a question: I can’t seem to start a 1.18.1 forge server on MacOS Big Sur, version 11.6.3. I can’t figure out what the problem is and been struggling for days now. I’ve installed Java JDK 17. I’ve tried with Java 8 update 321 and downgraded to Java 8 update 312. I’ve disabled my anti-virus software and I’ve tried giving the file permission through the “chmod 755 /path/to/script” command in the terminal. After running the run.sh file, I keep get the following error. It seems like a permission error, but I’m not sure how. ------------------------------------------- /Users/macbook/Minecraft\ server/Wecraft\ 1.18.1\ FORGE/run.sh ; exit; macbook@MacBook-Pro-2 ~ % /Users/macbook/Minecraft\ server/Wecraft\ 1.18.1\ FORGE/run.sh ; exit; Error: could not open `user_jvm_args.txt' Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. Deleting expired sessions...none found. [Process completed] ------------------------------------------- Changing the run.sh file so that it doesn’t need the ‘user_jvm_args.txt’ file and inserting the amount of RAM straight into the .sh file I get the following error: ------------------------------------------- /Users/macbook/Minecraft\ server/Wecraft\ 1.18.1\ FORGE/run.sh ; exit; macbook@MacBook-Pro-2 ~ % /Users/macbook/Minecraft\ server/Wecraft\ 1.18.1\ FORGE/run.sh ; exit; Error: could not open `libraries/net/minecraftforge/forge/1.18.1-39.0.63/unix_args.txt' Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. [Process completed] ------------------------------------------- It seems like the run.sh file has no permission to access anything in the folder, which is weird because it should be able to (I think?) I’m at a loss. Is anyone having the same problem? Is there a solution?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.