Add option to fetch Minecraft protocol versions from remote API #215
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently released https://github.com/hugmanrique/mc-versions, a project which reports Minecraft version data and is updated daily. It's not a real API per-se since the URL points to a static GitHub asset, but this guarantees the API will be online for long. This PR adds an option to specify the type of version provider (
local
ormc-versions
) and an update interval for fetching versions (both local and remote).(one of the reasons I made it was to stop needing someone to PR an update for each new MC version 😛)
The data fetching and normalization is already done. The versions take a while to be displayed on the client since the API reports so many protocol numbers, and Minetrack needs to ping servers with these versions. However, I've modified
getNextProtocolVersion
to skip versions with the same protocol number. The plan is to include aisRelease
flag to skip loading (and therefore pinging with) snapshot/pre-release protocol numbers.