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

And Argument for pack_format #28

Open
Stevertus opened this issue Jul 23, 2020 · 0 comments
Open

And Argument for pack_format #28

Stevertus opened this issue Jul 23, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@Stevertus
Copy link
Owner

That is the minor bug. If this bug is fixed, the datapacks generated will be compatible up to minecraft 1.16.1 and onwards. But I have a small suggestion on something you can add to the "mcscript new" command regarding pack.mcmeta. Currently, every datapack is generated with a pack.mcmeta file with the "pack_format" key set to 1. The "pack_format" key tells minecraft what version the datapack was made for. Minecraft can and will load datapacks for older versions, but never newer versions.

The "pack_format" ids according to the wiki are as follows:

1 for minecraft 1.6 - 1.8
2 for 1.9 and 1.10
3 for 1.11 and 1.12
4 for 1.13 and 1.14
5 for 1.15 and 1.16

My suggestion is that you can add an optional argument to mcscript new. The syntax could be something like this:
"mcscript new -version:"

Original: Hectoris919
#4922

@Stevertus Stevertus added the enhancement New feature or request label Sep 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant