You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an open discussion on the below points. Feel free to drop a reply with your thoughts.
Is anyone having issues with the current approach to compatibility with this library?
Is anyone still using this plugin with Minecraft server versions below 1.13 (i.e., with legacy support)?
Only the server version matters, e.g., if you're using ViaVersion/ViaBackwards for additional client support, dealing with other client versions would be done by that plugin.
How should version compatibility be handled?
Assuming 1.12 and below are not needed, support for those versions can be dropped and api-version can be used instead.
Alternatively, does anyone have suggestions on how backwards compatibility should be achieved?
The text was updated successfully, but these errors were encountered:
I personally tend to use 1.18 - 1.12 , however i agree with the person above that legacy support should be keeped if possible , considering servers nowdays support 1.8 till 1.19 versions.
This is an open discussion on the below points. Feel free to drop a reply with your thoughts.
The text was updated successfully, but these errors were encountered: