Add force set value #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Updated Unity project to 2021.3.22f1 * Updated all packages in project, removed several uneeded packages.
* Added editor-only method for forcing variable value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an editor-only way to force the value of
Variables, even if the variable is set as read-only or clamped. This enables us to potentially script changes for variables as part of build scripts (for example turning IAP on or off for a given build via aBoolVariable.As a part of this update I updated the project to the latest 2021 LTS version and removed a bunch of redundant packages we did not need in this project.
Nothing to test here, code-review only.