Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Minecraft Forge Server MacOS Problem

R3VOLVR

By R3VOLVR
in Support & Bug Reports

 Share

Recommended Posts

R3VOLVR Tree Puncher

R3VOLVR

Posted
Posted

Hi,

I am trying to create a modded Minecraft Forge server so I could play with my friends. I watched every video on how to make a modded Minecraft server using Forge on a Mac and they do not seem to have any problems at all, but unfortunately the terminal can not run the forge jar and is giving me error messages which will be provided below. The reason why I prefer using the terminal instead of the provided Minecraft server jar provided by the official Minecraft website is because the SpongeForge mod disables the GUI as far as I know. But anyways, here are the information:

I am currently using a 2018 Macbook Pro 15.

Specs:

  • CPU

    • 2.2 GHz Intel Core i7

  • RAM

    • 16GB 2400mHz DDR4

  • GPU

    • Radeon Pro 555X 4GB
    • Intel UHD Graphics 630 1536 MB

 

I also installed the recommended Java version - Java 8 Update 221.

 

Here's what's inside my start.command 

#!/bin/bash
cd "$(dirname "$0")"
exec java -Xms1G -Xmx1G -jar forge-1.12.2-14.23.5.2838-universal.jar nogui

 

and Here's the log on my terminal when i try to run the start.command: 

Last login: Thu Jul 18 00:22:03 on ttys000
Keiths-MacBook-Pro:~ keithphilippe$ /Users/keithphilippe/Desktop/Modded/Server/start.command ; exit;
A problem occurred running the Server launcher.java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:567)
	at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.run(ServerLaunchWrapper.java:70)
	at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.main(ServerLaunchWrapper.java:34)
Caused by: java.lang.ClassCastException: class jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class java.net.URLClassLoader (jdk.internal.loader.ClassLoaders$AppClassLoader and java.net.URLClassLoader are in module java.base of loader 'bootstrap')
	at net.minecraft.launchwrapper.Launch.<init>(Launch.java:34)
	at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
	... 6 more
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

 

 

I hope someone can help me fix this problem. Thanks in advance.

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted
2 hours ago, uiytt said:

okay so can you show us what you have in your server folder ?

This is irrelevant.

 

You need to use Java 8 to launch any pre-1.13 Forge version.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

R3VOLVR Tree Puncher

R3VOLVR

Posted
  • Author
Posted
8 hours ago, DaemonUmbra said:

This is irrelevant.

 

You need to use Java 8 to launch any pre-1.13 Forge version.

I already have said above that I recently installed Java 8. Problem still occurs.

R3VOLVR Tree Puncher

R3VOLVR

Posted
  • Author
Posted (edited)
6 minutes ago, diesieben07 said:

The log shows you are using Java 9 or above.

I do not currently have my laptop with me right now, but yesterday I just checked the Java version on my Mac via the System Preferences and it said that I was using Java 8u221. But if the log said that I am still using Java 9, I'll try to uninstall that version once I can have access to my laptop ASAP and send another update from you guys.

Hopefully this will fix the problem.

Edited by R3VOLVR
Spelling
R3VOLVR Tree Puncher

R3VOLVR

Posted
  • Author
Posted
4 hours ago, R3VOLVR said:

I do not currently have my laptop with me right now, but yesterday I just checked the Java version on my Mac via the System Preferences and it said that I was using Java 8u221. But if the log said that I am still using Java 9, I'll try to uninstall that version once I can have access to my laptop ASAP and send another update from you guys.

Hopefully this will fix the problem.

Unfortunately, I do not know how to uninstall Java 9 at the moment, but here's a screenshot of my current version of Java:

36094558_ScreenShot2019-07-18at4_23_39PM.thumb.png.f0119099742f7a8e3c3d310522e35cd3.png

R3VOLVR Tree Puncher

R3VOLVR

Posted
  • Author
Posted
8 minutes ago, diesieben07 said:

What matters is that java on the command line is somehow bound to Java 9 (or above).

You can specify the full path to the java executable instead to force Java 8.

So I reinstalled Java 8 again and the problem still persists. Is there a way you can help me do what's needed to be done? Do I need to change what's written in the start.command?

  • 1 month later...
  • 10 months later...
MisterBrums Tree Puncher

MisterBrums

Posted
Posted

Had the same problem. Running macOS Catalina 10.15.6. Installed Java 8 from Oracle's website, as suggested in this post. However, it's true that even after installing java 8, the "java" command still links to the built-in installed java.

 

This can be checked by typing  

java -version

Which outputs : java version "14.0.2" 2020-07-14

 

You can also see where the binary is by typing  

whereis java

Result: /usr/bin/java

 

After a bit of searching, the Java 8 binary, on the Mac, when installed from Oracle, is at: 

/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java

 

This is the correct binary, as shown by checking the version: 

"/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/./java" -version

Result: java version "1.8.0_261"

 

Here is my working startup script: 

#!/bin/bash
cd "$(dirname "$0")"
"/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/./java" -Xms4G -Xmx4G -jar forge-1.12.2-14.23.5.2854.jar

Note that you need to either quote the path or escape the space.

 

Hope it helps

 

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

1.12 is no longer supported on this forum.

Please update to a modern version of Minecraft to receive support.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

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

  I accept