After convincing my Mac that I did in fact want to open the thing I tried to open (unverified developer thing, scary download off the interwebs!) the launcher splash screen briefly blipped (hard to even notice) then nothing happened.
When I tried from a terminal so I could get some sort of logging it directed me to a log file wherein I found the following - which does at least seem to have a pretty clear error:
Rasmuss-MacBook-Pro:MacOS cervator$ pwd
/Users/cervator/dev/terasology/TerasologyLauncher-mac-4.7.0/TerasologyLauncher.app/Contents/MacOS
...
Rasmuss-MacBook-Pro:MacOS cervator$ ./TerasologyLauncher
Using log file /var/folders/j9/9d141hz563x0qdq1098_92100000gp/T/TerasologyLauncher_5431132856693820465.log
TerasologyLauncher is starting
The TerasologyLauncher could not be started!
...
Rasmuss-MacBook-Pro:MacOS cervator$ cat /var/folders/j9/9d141hz563x0qdq1098_92100000gp/T/TerasologyLauncher_5431132856693820465.log
16:17:59.008 [JavaFX Application Thread] INFO o.t.launcher.TerasologyLauncher - TerasologyLauncher is starting
16:17:59.012 [JavaFX Application Thread] DEBUG o.t.launcher.TerasologyLauncher - Java: 11.0.16.1 BellSoft /Users/cervator/dev/terasology/TerasologyLauncher-mac-4.7.0/TerasologyLauncher.app/Contents/jre
16:17:59.013 [JavaFX Application Thread] DEBUG o.t.launcher.TerasologyLauncher - Java VM: OpenJDK 64-Bit Server VM BellSoft 11.0.16.1+1-LTS
16:17:59.013 [JavaFX Application Thread] DEBUG o.t.launcher.TerasologyLauncher - Java classpath: /Users/cervator/dev/terasology/TerasologyLauncher-mac-
...
-1.6.20.jar:/Users/cervator/dev/terasology/TerasologyLauncher-mac-4.7.0/TerasologyLauncher.app/Contents/lib/icu4j-59.1.jar
16:17:59.013 [JavaFX Application Thread] DEBUG o.t.launcher.TerasologyLauncher - OS: Mac OS X x86_64 11.7.7
16:17:59.013 [JavaFX Application Thread] DEBUG o.t.launcher.TerasologyLauncher - Max. Memory: 4294967296 bytes
16:17:59.022 [JavaFX Application Thread] DEBUG o.t.launcher.TerasologyLauncher - Launcher version: 4.7.0
16:17:59.350 [Launcher init thread] DEBUG o.t.launcher.LauncherInitTask - Platform: OS 'mac', arch '64'
16:17:59.357 [Launcher init thread] DEBUG o.t.launcher.LauncherInitTask - TerasologyLauncher directory: /Users/cervator/Library/Application Support/TerasologyLauncher
16:17:59.359 [Launcher init thread] DEBUG o.t.launcher.LauncherInitTask - download directory: /Users/cervator/Library/Application Support/TerasologyLauncher/download
16:17:59.363 [Launcher init thread] DEBUG o.t.launcher.LauncherInitTask - temp directory: /Users/cervator/Library/Application Support/TerasologyLauncher/temp
16:17:59.364 [Launcher init thread] DEBUG o.t.launcher.LauncherInitTask - cache directory: /Users/cervator/Library/Application Support/TerasologyLauncher/cache
16:17:59.399 [Launcher init thread] DEBUG o.t.launcher.settings.Settings - Loading launcher settings from '/Users/cervator/Library/Application Support/TerasologyLauncher/TerasologyLauncherSettings.properties'.
16:17:59.530 [JavaFX Application Thread] ERROR o.t.launcher.TerasologyLauncher - The TerasologyLauncher could not be started!
java.lang.IllegalArgumentException: No enum constant org.slf4j.event.Level.DEFAULT
at java.base/java.lang.Enum.valueOf(Unknown Source)
at org.slf4j.event.Level.valueOf(Level.java:16)
at org.terasology.launcher.settings.LauncherSettings.getLogLevel(LauncherSettings.java:286)
at org.terasology.launcher.settings.Settings.fromLegacy(Settings.java:94)
at org.terasology.launcher.settings.Settings.load(Settings.java:161)
at org.terasology.launcher.LauncherInitTask.getLauncherSettings(LauncherInitTask.java:171)
at org.terasology.launcher.LauncherInitTask.call(LauncherInitTask.java:76)
at org.terasology.launcher.LauncherInitTask.call(LauncherInitTask.java:41)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
After convincing my Mac that I did in fact want to open the thing I tried to open (unverified developer thing, scary download off the interwebs!) the launcher splash screen briefly blipped (hard to even notice) then nothing happened.
When I tried from a terminal so I could get some sort of logging it directed me to a log file wherein I found the following - which does at least seem to have a pretty clear error: