🥓🐣 ↝ Different models are loaded in based on their respective anomaly… #58
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.
…'s temperature
Essentially, as of right now we just have one model being shown. I want to customise more things like the colours, biome textures, etc via the API, but for now I’m just going to be affecting the trees based on the API, and the other values & models will be rendered in randomly. Some of the models won’t have trees so we’ll have to choose something else to modify with the value returned from the current iteration of the flask api in signal-k/sytizen but for now we’ll just leave that blank as well.
In short → a method to render different Unity builds. Let’s add it as an additional field in the Supabase table, rather than doing any real interactions with unity for now.
This method should suffice for now.