So if I read "Important things #2" from the blog correctly, the Steam Early Access version (when it's released) will be auto-installing a Java Runtime on my system ? If that's the case, I'm sorry to say you definately won't win me as a customer after all that waiting. I have no problem with Java in itself, as long as it's not installed system-wide, for all virus and trojans free to use. Just distribute your EXE launcher and tested JRE binaries referenced by the EXE on Steam and everyone is happy, no ? The game would work just as good, without causing a huge security concern. Help me try to understand the reason for Java having to be installed system-wide otherwise, because it doesn't make any sense at all when it's perfectly possible to just start up the game by referencing the JRE binaries from a BAT file without having Java installed. Also, when the user is updating his Java runtime or modifying global JRE settings, because him being a developer, tester, whatever, then you'd have to deal with unnecessary, unrelated problem reports which too could be avoided by simply distributing your tested JRE binaries with the game and referencing them by the EXE launcher in the games install folder instead of installing Java on users PCs %programfiles%. By distributing tested JRE binaries in the install folder you also immediately get around the problem of x64 users having to explicitly install x86 JRE. I don't get it, is it a Java licensing issue to simply do that or ..? I want to buy your game as soon as it's finally available on Steam Early Access, but as I said, sadly not under these conditions. Should you insist on requiring Java installation in %programfiles%, I'll continue to wait for the GoG version if it's ever released there and play it on a separate offline PC or a virtual machine, but that's just nuts.