Resource and Data packs should use version ranges from .mcmeta files
Both resource packs and data packs have .mcmeta files that declare a version inside of them. It would be nice if instead of a single version or a version range, you get to pick predefined version ranges that match the possible numbers in those .mcmeta files.
An existing ticket on resource packs only (see here) does make a valid point that neither packs get a version number update if there are no breaking changes (like additions). That means that a pack made in for example 1.15, won't use the shiny features in 1.16 (assuming they are in the same version range), which is most notable in resource packs. The poster's proposed solution is allowing an "optimal" version (single version) besides the version range.
set status to Accepted, assigned Cyprezz, Paril. Having Data Packs and Resource Packs have their own version list that matches the protocol #s is probably the best in terms of quickly finding a compatible version.
We'd also have to think about Bedrock versions, though.
1
Join Planet Minecraft!
Since 2010, 5.8 million Minecraft fans have joined PMC to create, share, and grow together. Whether you're here to browse, show your support or level up your skills, you're invited to be part of our community.
Resource and Data packs should use version ranges from .mcmeta files
These are the current version tables for resource packs and data packs.
An existing ticket on resource packs only (see here) does make a valid point that neither packs get a version number update if there are no breaking changes (like additions). That means that a pack made in for example 1.15, won't use the shiny features in 1.16 (assuming they are in the same version range), which is most notable in resource packs. The poster's proposed solution is allowing an "optimal" version (single version) besides the version range.