You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, the script does NOT like Java 17, but I was able to get around that issue by disabling the Java check.
Now, every time I launch the script, it asks if I want to reinstall. Whether I say yes or no, it starts installing Forge (which looks like it's successful: the log file shows it's completed at the end, but no Forge or Minecraft server Jars are generated) and will repeatedly loop on this until finally failing. I did seem to get slightly further after correcting the error in the script noted in #93 but it does not resolve the issue.
Also, your discord link expired, or I'd ask someone there :D
The text was updated successfully, but these errors were encountered:
snaiperskaya
changed the title
Linux - Server keeps re-installing Forge and never actually starts
Linux - ServerStart.sh keeps re-installing Forge and never actually starts
Mar 25, 2023
My workaround is using ServerStart.sh -i to install forge (or use the installer that comes with the server pack if there is one), then I use the following script:
I use /usr/lib/jvm/java-8-openjdk/jre/bin/java instead of java because some forge versions require java8.
Replace forge-1.12.2-14.23.5.2860.jar with your forge jar.
Firstly, the script does NOT like Java 17, but I was able to get around that issue by disabling the Java check.
Now, every time I launch the script, it asks if I want to reinstall. Whether I say yes or no, it starts installing Forge (which looks like it's successful: the log file shows it's completed at the end, but no Forge or Minecraft server Jars are generated) and will repeatedly loop on this until finally failing. I did seem to get slightly further after correcting the error in the script noted in #93 but it does not resolve the issue.
Also, your discord link expired, or I'd ask someone there :D
The text was updated successfully, but these errors were encountered: