Users of macOS, consider yourselves warned! Read this troubleshooting section should thine cursor falter in haste, and foolishly the native distribution click ye! But, you should just use the JAR instead, if you can run JARs!

This mighty release should sate the ravenous throngs beseeching, nay, demanding updates to their precious versions!

First, some Mac support from updating NFD to NFDe, now at 3.3.4, to help the file selection dialogs. In addition, this updates Construo to 1.4.1 , which helps the native Mac distribution here a little (you should still probably prefer the .jar if that works for you).

The language defaults for Kotlin and Scala are now at their current latest stable versions (2.0.20 for Kotlin, 3.5.0 for Scala). If anyone wants Scala 2.x support still, please post an issue here on GitHub; Scala 3 uses different... everything from Scala 2, and this means Liftoff can generate dependencies for one but not the other.

MOE is enabled again, thanks to @Berstanio 's PR! This is another option for targeting iOS that allows using newer Java language levels and APIs than RoboVM, but isn't official and hasn't been tested as thoroughly. If you like features, I'm sure this is enticing, though!

Gradle is now up-to-date at 8.10.1, but this release has a bad known issue that, as of today, has a known workaround that Liftoff uses starting in this release. The issue is, generally, an unexpected build failure related to Gradle's "daemon" service it runs, and disabling the daemon avoids risking the failures at all. The 8.10.2 release is expected to issue a better fix that permits using the daemon if you want, but 8.10.1 without the daemon seems to perform fine so far, actually better than 8.10 with the daemon, potentially.

The OpenJDK versions downloaded by Construo have been updated; I'm not sure if they're the most recent right now, but they are newer.

Various bugs were fixed:

• projectVersion won't appear where an actual version was expected.
• Graal Native Image should behave with Gradle 8.10 (and 8.10.1) now; it needed some dependency changes moved around.
• If preferences can't be written for whatever reason (typically Windows-related), the app won't crash, since they aren't critical.
• Asset changes should be detected more reliably now, and not just when source code has changed.

Of the releases here, you should prefer the .jar file if you know you can run .jar files how you normally do, such as by double-clicking them. If you aren't confident a .jar file will run for you, you can either try the appropriate native distribution, or install a free/libre JDK that will let you run .jar files. As ye hast once been warned, macOS users should really use the .jar if at all possible, and if you do need to use the native distribution on macOS, there are extra steps it requires.

OK, get jamming, and good luck!