Add colour of Resource nodes (A, B) to minimap #89
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
Scony
reviewed
Dec 11, 2023
| @@ -8,12 +8,11 @@ const MATERIAL_ALBEDO_TO_REPLACE_EPSILON = 0.05 | |||
| resource_a = max(0, value) | |||
| if resource_a == 0: | |||
| queue_free() | |||
|
|
|||
| @export var color = Constants.Match.Resources.A.COLOR | |||
There was a problem hiding this comment.
IMO we can drop @export in the case of both resource files - that variable should be as read-only as possible to avoid situations where the color is being changed in runtime
|
Actually, I'll fix it, thanks for contributing! |
|
Thank you! 👍 |
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 is a small change so that Resource nodes show up as their own colour on the minimap.
Any questions just let me know!
Resolves #88