Closed japtar10101 closed 3 years ago
For my part, I think the current ScritpableObjects method is actually fine, and if anything, poses some significant advantages over the Project Settings method. For example, it allows creating multiple sets of builds settings and easy duplication of said settings. They can be divided into platforms, etc.
Honestly don't see a good reason to do this, when the current options provide advantages over this suggestion.
Is your feature request related to a problem? Please describe.
Build Settings
Describe the solution you'd like
It seems Unity is opening up the API to add windows under Project Settings and Preferences. In build settings' case, having a single Project Settings would be perfect, rather than awkwardly splitting it into ScriptableObjects.
Tasklist
Describe alternatives you've considered
The current method, where all the settings are held within individual ScriptableObjects.
Additional context
Carry-over from the old Bitbucket Mercurial project: https://bitbucket.org/OmiyaGames/hg-template-unity-project/issues/63/migrate-build-settings-to-a-project