RC12's requirement on Java 24 conflicts with ProtocolLib

[RobotHanzo]

Stacktrace

exception encountered in com.velocitypowered.proxy.connection.backend.LoginSessionHandler
io.netty.channel.unix.Errors$NativeIoException: recv(..) failed: Connection reset by peer

(This happens upon joining a server with ProtocolLib installed)

Actions to reproduce

1. Install Java 24, CloudNet 4.0.0RC12 alongside with ProtocolLib
2. Join any server with ProtocolLib installed
3. The player gets kicked with the above exception from proxy, and no logs from the server.

CloudNet version

[26.05 16:12:08.731] INFO :
[26.05 16:12:08.732] INFO : CloudNet Blizzard 4.0.0-RC12 4895431e
[26.05 16:12:08.732] INFO : Discord: <https://discord.cloudnetservice.eu/>
[26.05 16:12:08.732] INFO :
[26.05 16:12:08.732] INFO : ClusterId: c6b7bcad-****-401c-****-069f7903704c
[26.05 16:12:08.732] INFO : NodeId: Node-1
[26.05 16:12:08.732] INFO : Head-NodeId: Node-1
[26.05 16:12:08.732] INFO : CPU usage: (P/S) 13.94/17.53/100%
[26.05 16:12:08.732] INFO : Node services memory allocation (U/R/M): 14848/14848/60000 MB
[26.05 16:12:08.733] INFO : Threads: 86
[26.05 16:12:08.733] INFO : Heap usage: 214/256MB
[26.05 16:12:08.733] INFO : JVM: Eclipse Adoptium 24 (OpenJDK 64-Bit Server VM 24.0.1+9)
[26.05 16:12:08.733] INFO : Update Repo: CloudNetService/launchermeta, Update Branch: beta
[26.05 16:12:08.733] INFO :

Other

After digging through related issue requests, I have found a relevant post on PaperMC's discord explaining a solution to this issue: https://canary.discord.com/channels/289587909051416579/908507866183372801/1373576291944763452
However, this solution requires advanced configuration of an environment variable JDK_JAVA_OPTIONS=--add-opens java.base/java.lang=ALL-UNNAMED in the global template group, which may be difficult for starters.
Thus, it is advised to include this env var by default in the setup, as well as in the release notes, until this issue is patched by ProtocolLib, or CloudNet stops depending on it.

Issue uniqueness

• Yes, this issue is unique. There are no similar issues.

[derklaro]

This should be resolved by updating your ProtocolLib version, at least it worked for me without additional jvm flags after dmulloy2/ProtocolLib#3425

[RobotHanzo]

This should be resolved by updating your ProtocolLib version, at least it worked for me without additional jvm flags after dmulloy2/ProtocolLib#3425

This indeed fixed the issue, thank you
Though it'd be great if there were a notice to update ProtocolLib in the release notes