LiteCommands
LiteCommands copied to clipboard
Drop java 8 support. Bump to java 17
This is fatal for lower versions of Minecraft
Higher versions of Java have many pleasant features, but this is devastating to lower version games (minigames and PVP servers that still exist in large numbers).
I think Lite Commands should update to atleast Java 17 following ViaVersion. Most Minigame/PvP servers already run a fork of the notchian server that can be updated or already support J17. Also if it is required lite commands can include a version that uses https://github.com/unimined/JvmDowngrader. I would love to see J21 support to utilize virtual threads, but its not a requirement.
I think Lite Commands should update to atleast Java 17 following ViaVersion. Most Minigame/PvP servers already run a fork of the notchian server that can be updated or already support J17. Also if it is required lite commands can include a version that uses https://github.com/unimined/JvmDowngrader. I would love to see J21 support to utilize virtual threads, but its not a requirement.
Maybe you are right. But ProtocolLib says NO.
I think Lite Commands should update to atleast Java 17 following ViaVersion. Most Minigame/PvP servers already run a fork of the notchian server that can be updated or already support J17. Also if it is required lite commands can include a version that uses https://github.com/unimined/JvmDowngrader. I would love to see J21 support to utilize virtual threads, but its not a requirement.
Maybe you are right. But ProtocolLib says NO.
What do you mean?
Owner Author
ProtocolLib for 1.8.8~1.12 alwasy drop errors if not using Java8 even using "Downgrader"
I think Lite Commands should update to atleast Java 17 following ViaVersion. Most Minigame/PvP servers already run a fork of the notchian server that can be updated or already support J17. Also if it is required lite commands can include a version that uses https://github.com/unimined/JvmDowngrader. I would love to see J21 support to utilize virtual threads, but its not a requirement.
Maybe you are right. But ProtocolLib says NO.
What do you mean?
Of course, no matter what, I also strongly support LiteCommands upgrading to at least j17.
The new version of Java brings many syntax and performance advantages.