Since VPM is convenient package distribution, some Generic Unity tools are also distributed as VPM package.
For such a packages, specifying unity field to 2021.3 is very reasonable since Unity 2021.3 is (legacy) LTS
VCC allows installing Package Requires Unity 2021.3 to the project without any warning.
Expected behavior
VCC should
Warn Package Requires Unity 2021.3 is not compatible with 2019 and ask migrate to 2022
Warn Package Requires Unity 2021.3 is not compatible with 2019 and refuse installing the package
Screenshots
No response
Related Product
VCC (VRChat Creator Companion)
Product Version
2.2.2
OS
Windows 11
Additional context
Related issues
367
311
There already is one real-world example of packages requires unity 2021.3.
That is TexTransTool v0.5.0-beta by Reina Sakiria.
In addition, my AvatarOptimizer is planned to require unity 2021.3 if it's still LTS when I drop Unity 2019.
orels1
commented
4 months ago
Describe the bug
VCC allows installing packages requires Unity 2021.3 to Unity 2019 projects.
Since VPM is convenient package distribution, some Generic Unity tools are also distributed as VPM package. For such a packages, specifying
unityfield to2021.3is very reasonable since Unity 2021.3 is (legacy) LTSTo Reproduce
Package Requires Unity 2021.3to the projectPackage Requires Unity 2021.3to the project without any warning.Expected behavior
VCC should
Package Requires Unity 2021.3is not compatible with 2019 and ask migrate to 2022Package Requires Unity 2021.3is not compatible with 2019 and refuse installing the packageScreenshots
No response
Related Product
VCC (VRChat Creator Companion)
Product Version
2.2.2
OS
Windows 11
Additional context
Related issues
367
311
There already is one real-world example of packages requires unity 2021.3. That is TexTransTool v0.5.0-beta by Reina Sakiria. In addition, my AvatarOptimizer is planned to require unity 2021.3 if it's still LTS when I drop Unity 2019.