You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of users are confused on why they cannot use newly added Minecraft Add-On syntax within their bridge. projects.
Summary
We propose to allow the strings "latestStable" and "latestPreview" as valid target versions within the project config.
The config parser can replace these two strings with the respective versions before handing over the parsed config to other parts of the program making this a non-breaking change.
/** * The Minecraft version this project targets * * Use "latestStable" or "latestPreview" to always use the latest Minecraft or Minecraft Preview * version as your project target version * * @example "1.17.0" / "1.16.220" / "latestStable" */
targetVersion: string
The text was updated successfully, but these errors were encountered:
Motivation
A lot of users are confused on why they cannot use newly added Minecraft Add-On syntax within their bridge. projects.
Summary
We propose to allow the strings
"latestStable"
and"latestPreview"
as valid target versions within the project config.The config parser can replace these two strings with the respective versions before handing over the parsed config to other parts of the program making this a non-breaking change.
The text was updated successfully, but these errors were encountered: