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:"
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_