--headless displays splash screen when running from console/terminal.

[lodici]

A long time since I looked at the splash screen mechanism but I think MagicMain is linked to the mechanism for preloading the splash image via a setting in build.xml. The workaround is to add -splash:.

[melvinzhang]

splash screen and --headless are separate things, they are not related. Splash screen is the image shown when the JVM loads the jar, it is a setting in the jar. It is loaded and shown without any code as long as the SplashScreen-Image is set in the jar file. --headless means run using a particular game controller that output on the command line instead of in the GUI.

[melvinzhang]

@lodici is the issue starting many --headless instances and seeing multiple splash screen show up?

[melvinzhang]

If so, it seems that the only way around that is to use our own splashscreen instead of the default one. The default one is loaded and shown even before any code gets loaded, so it is not possible to disable it except with VM flags like the -splash:. or -Djava.awt.headless=true. See MovingBlocks/Terasology#1571 for a similar issue

[melvinzhang]

Using our own SplashScreen seems to be a bit of an overkill, instead of requiring both -Djava.awt.headless=true and --headless what about removing --headless and automatically execute "headless" mode when -Djava.awt.headless=true is set. This can be detected in code via GraphicsEnvironment.isHeadless() method.