Open
Conversation
Mirrors the existing TMX custom importer pattern for TSX and World asset types, enabling project-specific import extensions via [AutoCustomTsxImporter] and [AutoCustomWorldImporter] attributes.
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.
It's sometimes useful for projects to cusalso tomize the tileset and worlds exports to include additional autogenerated assets.
For tilesets, this might be to generate embedded animation SOs in a format more native to the project
For worlds, this might be to include a top level behavior for managing the "level" state or other metadata.
This PR adds [AutoCustomTsxImporter] and [AutoCustomWorldImporter] attributes, to allow unity projects to augment and customize the .tsx and .world assets at import time.