Initial 1.17 Support

**wild1145** · June 19, 2021 at 2:56 PM

We are now able to support 1.17 throughout the network with the use of ViaVersions.

For the time being we are still recommending that where practical users still connect on 1.16.5 for the best possible experience, however do appreciate that might not always be practical / desirable.

The development team are working hard to bring support for 1.17, though it is a significant amount of work even compared to previous updates, and a lot of stuff is breaking due to Mojang's decision to bump up the minimum Java version to play their game to a non-standard / LTS release.

We hope in the coming weeks to move fully on to 1.17, but for now this should at least bridge the gap and allow everyone who has been playing / may want to join us to be able to play on the network.

Thanks everyone.

Windows · June 19, 2021 at 4:16 PM

Good luck, you'll probably need it. Murphy's law + Java 16 = yikes.

Telesphoreo · June 19, 2021 at 4:38 PM

A lot of stuff broke after Java 11. Technically you aren't required to compile for Java 16. I still compile in Java 8 because it supports older versions than 1.15 and some versions like 1.12 flat out don't work on Java 16 for me

Windows · June 19, 2021 at 4:52 PM

↩ Telesphoreo
You can use different Java versions for different MC profiles thankfully.

**wild1145** · June 19, 2021 at 5:21 PM

↩ Windows Yeah we're doing the Java 16 upgrade at the moment, and then the 1.17 update in the aims of making it simpler, but because a lot of plugin dev's ignored the deprecation warnings in Java 11 and Java 16 is not LTS it's come as a bit of a shock to most dev's and is causing a lot of issues just getting base plugins working on Java 16...

Telesphoreo · June 19, 2021 at 6:10 PM

↩ Windows True but a lot of average 11 year old Minecrafters won't even know how to do this. I'm pretty sure the Minecraft launcher bundles Java now though

Telesphoreo · June 19, 2021 at 6:44 PM

I was able to get TFM to compile under Java 16 in about 10 minutes lol

**wild1145** · June 19, 2021 at 6:47 PM

↩ Telesphoreo TFM is not the main problem... It's every other plugin as I already said.

We've been able to get TFM to build Java 16 (With some minor tweaks) but it doesn't mean TF itself runs well on Java 16 with 2/3 of the plugins broken.

Telesphoreo · June 19, 2021 at 7:14 PM

↩ @'Ryan' Every plugin except LibsDisguises works fine on StevenNL2000Freedom. Thats probably because the one on AMG is outdated and I haven't been bothered to update it on my own. I was able to get BlocksHub working on Java 16, I just had to compile it on my own (LibsDisguises gives errors on Java 11 also which is weird)

Windows · June 19, 2021 at 7:21 PM

↩ Telesphoreo

I honestly expect there will be a lot of less obvious bugs popping up once it gets onto the server. It is impossible to test every possible interaction with plugins on your own.

Telesphoreo · June 19, 2021 at 7:36 PM

↩ Windows Fair, but getting it to turn on is the first step. I just got TF-LibsDisguises working on Java 16. I've been playing for a while now and it seems as if everything is working fine. No plugins are visibly broken and all the functionality of TFM appears to be working fine for me

Fleek · June 20, 2021 at 1:11 AM

↩ Telesphoreo TF-LibsDisguises have been updated for since a couple days ago.

Telesphoreo · June 20, 2021 at 1:13 AM

↩ Fleek didn't compile, I had to merge the latest commit from the main repo

**wild1145** · July 8, 2021 at 7:54 PM

We've now updated the bungee and ViaVersion to support 1.17.1 as well as it doesn't look like it is backward compatible natively for some reason or another.

wild1145 July 16, 2022 at 11:09 PM