Expose server API version along with helper methods

[Toffikk]

Is your feature request related to a problem?

Currently when trying to gate logic behind MC versions in plugins you need to implement some sort of a version matcher for MC versions or use protocol versions.

Describe the solution you'd like.

I would like to see the server’s latest supported API version exposed in the API along with an isCompatible() method to make version dependent plugin code cleaner.

A possible implementation could look similar to to ServerBuildInfo with the latest plugin API version supported by the server being exposed along with something like ApiVersionInfo#isCompatible(String version)

Describe alternatives you've considered.

mentioned above

Other

Tbh just the isCompatible method would be enough for most use cases

[Toffikk]

This could also land under UnsafeValues

[lynxplay]

Like https://jd.papermc.io/paper/26.2/io/papermc/paper/ServerBuildInfo.html?

[Toffikk]

Like https://jd.papermc.io/paper/26.2/io/papermc/paper/ServerBuildInfo.html?

Yes

[lynxplay]

I am a bit confused what "isCompatible" would look like in your mind.
Is what compatible? your plugin with the server version? The answer is generally gonna be yes if you use non experimental API and "depends" if you use experimental API.

idk how you'd scope that to a single method?

[masmc05]

If I remember correctly the reason why #10253's isAtLeast was dropped from the final ServerBuildInfo was complexity of checking that for snapshots, but with the new Minecraft versioning I think that wouldn't be a problem anymore

[Toffikk]

I meant as if the API version is equal to or lower than the latest supported by the server

like the methods in org.bukkit.craftbukkit.util.ApiVersion which i would love to see exposed to the API

edit: i might have worded the issue a bit not clearly, but i just meant an easy way to check and compare api versions

[lynxplay]

Yea I mean, their new version scheme should make this a good bit easier and we wouldn't be porting something like this back so, no need to handle old snapshot builds as no plugin was developing against those anyway 💀