Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to fetch Minecraft protocol versions from remote API #215

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

hugmanrique
Copy link
Contributor

@hugmanrique hugmanrique commented Nov 16, 2020

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 or mc-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 a isRelease flag to skip loading (and therefore pinging with) snapshot/pre-release protocol numbers.

@babel/preset-env now contains @babel/plugin-proposal-class-properties
with the default config (which is what parcel uses by default). This
removes the redundant .babelrc, which caused a double-declaration error.
@Cryptkeeper
Copy link
Owner

Cryptkeeper commented Nov 27, 2020

Would you like me to start reviewing this now or wait until the draft status is removed?

@hugmanrique
Copy link
Contributor Author

I would wait until I remove the WIP status. As it stands, this is more of a PoC. I'm pretty busy right now, so I don't have much time to work on this 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants