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

Suggestion: Usually Stick with One Unity Version for Updates #87

Open
CG-Tespy opened this issue Sep 27, 2023 · 0 comments
Open

Suggestion: Usually Stick with One Unity Version for Updates #87

CG-Tespy opened this issue Sep 27, 2023 · 0 comments

Comments

@CG-Tespy
Copy link

CG-Tespy commented Sep 27, 2023

The Problem

Each new release requiring users to install a newer version of Unity. Like how going from v0.15 to v0.16 requires you to go from 2021.3.17f1 to 2021.3.28f1.

Why It's a Problem

Simply put, it shows a lack of respect for users' time. People usually don't like going through the hassle of installing a newer Unity just for the sake of one asset package, especially if the improvements don't seem to really need whatever the newer engine ver offers. And if said newer Unity has a bug that breaks functionality in your game...

The Solution/Suggestion

Unless an update really needs whatever's in the newer ver, stick to an older one. For maximum accessibility, go with the oldest version of the relevant year necessary. For example, if everything in v0.17 is perfectly doable in 2021.1.1, have that be the minimum version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant