Added logic to reset Random.state in ColorSettings to avoid polutting… #404
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.
ColorSettings has logic that resets the global rng state with a seed of 0. This results in RNG behaving deterministically the same when in the editor.
Fixed by caching the current state of Random and then setting it back after filling the outlines2D array.
Considering the logic as is will always fill outlines2D array with the same values. If this is the intended behavior then it could be refactored to just have a static definition of what should be in outlines2D.