Respect tiled properties as an array #682
Merged
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
Tiled objects have properties as an array of objects like:
{ name: ..., type: ..., value: ...}
Update the parser to load these using the name/value properties instead
of just treating it as an array and loading properties named '0', '1',
etc.
the difference is, that sprite.setData does not exist in PhaserCE. therefore the property is set directly on the sprite.
samme
added a commit
that referenced
this pull request
Feb 18, 2021
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.
This PR
Please include a summary in Change Log: Unreleased and thank yourself.
Describe the changes below:
Adaptation of:
phaserjs/phaser@fea6598
Tiled objects have properties as an array of objects like:
{ name: ..., type: ..., value: ...}
Update the parser to load these using the name/value properties instead
of just treating it as an array and loading properties named '0', '1',
etc.
sprite.setData does not exist in PhaserCE. therefore the property is set directly on the sprite.