feat: rename shader config file on version change#5636
Open
Artezon wants to merge 1 commit into
Open
Conversation
|
@aecsocket can you review pls |
Artezon
force-pushed
the
update-shader-companion-files
branch
from
32e6207 to
49550ab
Compare
Artezon
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Shaderpacks with changed settings have companion files named
<shader_file>.txt. Different shader versions usually have different file names. This PR adds a feature that automatically renames companion files when shaders are updated (or downgraded), so the config is transferred to a new version.Closes #5483