sonusmc

Java 7 allows that, too. http://docs.oracle.com/javase/7/docs/technotes/guides/language/strings-switch.html I am also thinking of writing my mods in Scala. However, I want my mods to be compatible with older minecraft versions (1.4.7+). Did forge support scala back then?

ok, I got it now. had to add -Djava.library.path= pointing to native lwjgl folder to vm arguments.

I am totally new to minecraft and game modding in general and starting the client via eclipse with the built in examplemod gives me the following exception: [20:09:18] [main/ERROR] [LaunchWrapper]: Unable to launch java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_45] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_45] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_45] at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_45] at net.minecraft.launchwrapper.Launch.launch(Launch.java:134) [launchwrapper-1.9.jar:?] at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.9.jar:?] Caused by: java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown Source) ~[?:1.7.0_45] at java.lang.Runtime.loadLibrary0(Unknown Source) ~[?:1.7.0_45] at java.lang.System.loadLibrary(Unknown Source) ~[?:1.7.0_45] at org.lwjgl.Sys$1.run(Sys.java:73) ~[lwjgl-2.9.0.jar:?] at java.security.AccessController.doPrivileged(Native Method) ~[?:1.7.0_45] at org.lwjgl.Sys.doLoadLibrary(Sys.java:66) ~[lwjgl-2.9.0.jar:?] at org.lwjgl.Sys.loadLibrary(Sys.java:95) ~[lwjgl-2.9.0.jar:?] at org.lwjgl.Sys.<clinit>(Sys.java:112) ~[lwjgl-2.9.0.jar:?] at net.minecraft.client.Minecraft.getSystemTime(Minecraft.java:2720) ~[Minecraft.class:?] at net.minecraft.client.main.Main.main(Main.java:40) ~[Main.class:?] ... 6 more I can run the server without any problems from eclipse and 'gradlew build' also works fine with the sample mod. I know lwjgl is the java gl library. do I have to install it manually? shouldn't gradle also resolve this dependency?