-
Notifications
You must be signed in to change notification settings - Fork 0
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
Retrieve vanilla data packs [$25] #5
Comments
Implementation notesGlowstone would only be interested in server-side data packs and registry reports. Those can be generated by downloading the Vanilla server JAR, and running:
Which produces the directory structure:
AutomatingMy thoughts on implementation:
If the second option is used by the end-user, it should be possible to configure which URL to download the JAR from, defaulting to Mojang's servers. |
Do we actually need to automate this? Now that vanilla's gone through 1.13, 1.14, 1.15, and soon 1.16, and at most this file would change once per version. We could just hand edit it based off the changelogs for each version. |
Yes, because we don't want to redistribute the file. |
Plus a bounty's a bounty :P |
This is now being handled by redstone-transformer. |
This issue is part of the 1.13.x compatibility Epic.
All contributions are subject to the Glowstone CLA. In short, contributions must not contain any content (code or otherwise) copied from,
inspired by or based upon content from Mojang or third-party projects that are based on such content (CraftBukkit, Spigot, Forge, ...).
Description:
Have a way to automatically get vanilla data packs and reports without redistribution. This will likely involve downloading the Minecraft server automatically and running it for generating data reports. We need to also add a flag to prevent downloading the Minecraft server if people choose to opt out of using Mojang data.
Reference Documentation:
https://wiki.vg/Data_Generators
Related to:
#4
There is a $25 open bounty on this issue. Add to the bounty at Bountysource.
The text was updated successfully, but these errors were encountered: