Resource Tree Generator: Add missing built-in file types #169
Conversation
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
1 participant
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.
I have no idea how I could miss some of these, especially .gdshader! :D
Most of these are seemingly undocumented binary formats offered as alternatives for some resource types (which could just as well be saved in .tres or .res).
I don't think there's a list of these anywhere, so I just clicked my way through the resource creation wizard, so I cannot claim that the included ones are exhaustive, but they probably more than cover common types.
I had an issue adding a case for .translation because it would generate duplicate entries for the
OptimizedTranslationfiles already being tested.I don't think this is relevant enough to be investigated, since "regular" .translation files clearly work already.